GitHub/MotorolaMobilityLLC/kernel-slsi.git
5 years ago[RAMEN9610-20768][9610] s2mu106_usbpd delete deadcode
Jinsu Park [Mon, 28 Oct 2019 04:25:01 +0000 (13:25 +0900)]
[RAMEN9610-20768][9610] s2mu106_usbpd delete deadcode

Change-Id: I2bac68122656f6f5276ff9dc4fb995eda15d4be3
Signed-off-by: Jinsu Park <js00.park@samsung.com>
5 years ago[RAMEN9610-20768][9610] s2mu106_muic move break
Jinsu Park [Mon, 28 Oct 2019 04:28:15 +0000 (13:28 +0900)]
[RAMEN9610-20768][9610] s2mu106_muic move break

Change-Id: Id0d99453289b85aabf12dbb5b04a057198c527d5
Signed-off-by: Jinsu Park <js00.park@samsung.com>
5 years ago[RAMEN9610-20759]wlbt: Changes to set key type as IGTK for BIP_GMAC ciphers
Sushant B Butta [Wed, 16 Oct 2019 14:53:44 +0000 (20:23 +0530)]
[RAMEN9610-20759]wlbt: Changes to set key type as IGTK for BIP_GMAC ciphers

Currently driver sets the key type as IGTK for cipher suite :
(0x000FAC, 6 :WLAN_CIPHER_SUITE_AES_CMAC).
Driver should set the key type to IGTK for cipher suites
WLAN_CIPHER_SUITE_BIP_GMAC_128, WLAN_CIPHER_SUITE_BIP_GMAC_256 also.

Change-Id: Idfeb67fe9c170a12ebba89d59c2235a1b37f36e5
SCSC-Bug-Id: HOST-11211
Signed-off-by: Sushant B Butta <b.sushant@samsung.com>
5 years ago[RAMEN9610-20756][COMMON] scsi: ufs: Change SSU timeout from 5s to 23s.
JaeHun Jung [Tue, 27 Aug 2019 05:10:58 +0000 (14:10 +0900)]
[RAMEN9610-20756][COMMON] scsi: ufs: Change SSU timeout from 5s to 23s.

Micron UFS SSU is spend 20s when disk full status.

Change-Id: Ic01638f71e82a9498d5f29ea595aeba298347f81
Signed-off-by: JaeHun Jung <jh0801.jung@samsung.com>
5 years ago[RAMEN9610-20756][RAMEN9610-18380][COMMON] scsi: scsi_sysfs: Remove async_suspend.
JaeHun Jung [Thu, 25 Jul 2019 04:05:09 +0000 (13:05 +0900)]
[RAMEN9610-20756][RAMEN9610-18380][COMMON] scsi: scsi_sysfs: Remove async_suspend.

async_suspend sometimes make watchdog reset when suspend.
So, Disable async_suspend.

Change-Id: Ifb9286003ef25aee9f89599c32e4ea6f370806de
Signed-off-by: JaeHun Jung <jh0801.jung@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-20756][RAMEN9610-18204][COMMON] scsi: ufs: Change timeout for start_stop...
JaeHun Jung [Fri, 19 Jul 2019 08:07:59 +0000 (17:07 +0900)]
[RAMEN9610-20756][RAMEN9610-18204][COMMON] scsi: ufs: Change timeout for start_stop from 60s to 5s

Watchdog is 26s.
60s is too long in mobile device.
So, Change it.

Change-Id: Ic874ce9dca62649e9d33d25ee6251cc123e2001d
Signed-off-by: JaeHun Jung <jh0801.jung@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-20756][COMMON] scsi: sd: Change scsi timeout form 30s to 5s.
JaeHun Jung [Mon, 18 Mar 2019 06:01:12 +0000 (15:01 +0900)]
[RAMEN9610-20756][COMMON] scsi: sd: Change scsi timeout form 30s to 5s.

UFS has very fast response device. So, We decrease timeout for recovery.

Change-Id: I4c0a6375413839a8495045a771ab50ff23edc614
Signed-off-by: JaeHun Jung <jh0801.jung@samsung.com>
5 years ago[RAMEN9610-20754][9610] ASoC: abox: requested cpu gear to hold the usage count of PM
ShinHyung [Tue, 10 Sep 2019 09:43:35 +0000 (18:43 +0900)]
[RAMEN9610-20754][9610] ASoC: abox: requested cpu gear to hold the usage count of PM

Change-Id: I71181515f075308319156c5964298cec18b71750
Signed-off-by: ShinHyung <s47.kang@samsung.com>
5 years ago[RAMEN9610-20751]ext4: zero out the unused memory region in the extent tree block
Sriram Rajagopalan [Fri, 10 May 2019 23:28:06 +0000 (19:28 -0400)]
[RAMEN9610-20751]ext4: zero out the unused memory region in the extent tree block

commit 592acbf16821288ecdc4192c47e3774a4c48bb64 upstream.

This commit zeroes out the unused memory region in the buffer_head
corresponding to the extent metablock after writing the extent header
and the corresponding extent node entries.

This is done to prevent random uninitialized data from getting into
the filesystem when the extent block is synced.

This fixes CVE-2019-11833.

Change-Id: I3dcc0bd0e41a601134041953158d73506110a88a
Signed-off-by: Sriram Rajagopalan <sriramr@arista.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cc: stable@kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
5 years ago[RAMEN9610-20751]BACKPORT: binder: Set end of SG buffer area properly.
Martijn Coenen [Tue, 9 Jul 2019 11:09:23 +0000 (13:09 +0200)]
[RAMEN9610-20751]BACKPORT: binder: Set end of SG buffer area properly.

In case the target node requests a security context, the
extra_buffers_size is increased with the size of the security context.
But, that size is not available for use by regular scatter-gather
buffers; make sure the ending of that buffer is marked correctly.

Bug: 136210786
Acked-by: Todd Kjos <tkjos@google.com>
Fixes: ec74136ded79 ("binder: create node flag to request sender's security context")
Signed-off-by: Martijn Coenen <maco@android.com>
Cc: stable@vger.kernel.org # 5.1+
Link: https://lore.kernel.org/r/20190709110923.220736-1-maco@android.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
(cherry picked from commit a56587065094fd96eb4c2b5ad65571daad32156d)

Change-Id: I415785c0e210c51a5ae1c90e6783f2beb7bdd86c

5 years ago[RAMEN9610-20751]binder: fix possible UAF when freeing buffer
Todd Kjos [Wed, 12 Jun 2019 20:29:27 +0000 (13:29 -0700)]
[RAMEN9610-20751]binder: fix possible UAF when freeing buffer

commit a370003cc301d4361bae20c9ef615f89bf8d1e8a upstream.

There is a race between the binder driver cleaning
up a completed transaction via binder_free_transaction()
and a user calling binder_ioctl(BC_FREE_BUFFER) to
release a buffer. It doesn't matter which is first but
they need to be protected against running concurrently
which can result in a UAF.

Change-Id: I6b9b6a0b9e85b0953d5b53f62fb2ad35f62e1a23
Signed-off-by: Todd Kjos <tkjos@google.com>
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
5 years ago[ERD][RAMEN9610-20750][RAMEN9610-18757] fbdev: dpu: lcd status notifier is added
hwangjae lee [Tue, 30 Jul 2019 05:10:50 +0000 (14:10 +0900)]
[ERD][RAMEN9610-20750][RAMEN9610-18757] fbdev: dpu: lcd status notifier is added

Change-Id: I283f452e6ae88ddff4a7229d1e2b71c90c2d53ff
Signed-off-by: hwangjae lee <hj-yo.lee@samsung.com>
Signed-off-by: ChiHun Won <chihun.won@samsung.com>
5 years ago[RAMEN9610-20741]UPSTREAM: xfrm: Make set-mark default behavior backward compatible
Benedict Wong [Mon, 14 Jan 2019 19:24:38 +0000 (11:24 -0800)]
[RAMEN9610-20741]UPSTREAM: xfrm: Make set-mark default behavior backward compatible

Fixes 9b42c1f, which changed the default route lookup behavior for
tunnel mode SAs in the outbound direction to use the skb mark, whereas
previously mark=0 was used if the output mark was unspecified. In
mark-based routing schemes such as Android’s, this change in default
behavior causes routing loops or lookup failures.

This patch restores the default behavior of using a 0 mark while still
incorporating the skb mark if the SET_MARK (and SET_MARK_MASK) is
specified.

Tested with additions to Android's kernel unit test suite:
https://android-review.googlesource.com/c/kernel/tests/+/860150

Fixes: 9b42c1f ("xfrm: Extend the output_mark to support input direction and masking")
Signed-off-by: Benedict Wong <benedictwong@google.com>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
(cherry picked from commit e2612cd496e7b465711d219ea6118893d7253f52)
Bug: 122236988
Test: Passes kernel tests
Change-Id: I1289b5b7b1eb93c6d99a0ba7d28e24c3eb25883d
Signed-off-by: Benedict Wong <benedictwong@google.com>
5 years ago[RAMEN9610-20741]UPSTREAM: xfrm: fix ptr_ret.cocci warnings
kbuild test robot [Thu, 26 Jul 2018 07:09:52 +0000 (15:09 +0800)]
[RAMEN9610-20741]UPSTREAM: xfrm: fix ptr_ret.cocci warnings

net/xfrm/xfrm_interface.c:692:1-3: WARNING: PTR_ERR_OR_ZERO can be used

 Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR

Generated by: scripts/coccinelle/api/ptr_ret.cocci

Fixes: 44e2b838c24d ("xfrm: Return detailed errors from xfrmi_newlink")
CC: Benedict Wong <benedictwong@google.com>
Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
(cherry picked from commit c6f5e017df9dfa9f6cbe70da008e7d716d726f1b)
Signed-off-by: Benedict Wong <benedictwong@google.com>
Bug: 113046120
Test: All kernel net-tests run, passing (20x repeated)
Change-Id: I4ec93c0427fded57ff5126dc7b3d97d9b5fd615b

5 years ago[RAMEN9610-20741]UPSTREAM: xfrm: Return detailed errors from xfrmi_newlink
Benedict Wong [Wed, 25 Jul 2018 20:45:29 +0000 (13:45 -0700)]
[RAMEN9610-20741]UPSTREAM: xfrm: Return detailed errors from xfrmi_newlink

Currently all failure modes of xfrm interface creation return EEXIST.
This change improves the granularity of errnos provided by also
returning ENODEV or EINVAL if failures happen in looking up the
underlying interface, or a required parameter is not provided.

This change has been tested against the Android Kernel Networking Tests,
with additional xfrmi_newlink tests here:

https://android-review.googlesource.com/c/kernel/tests/+/715755

Signed-off-by: Benedict Wong <benedictwong@google.com>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
(cherry picked from commit 44e2b838c24d883dae8496dc7b6ddac7956ba53c)
Bug: 113046120
Change-Id: Ic680bf1e4a828aaae01b289223d9396a551eefd2

5 years ago[RAMEN9610-20741]UPSTREAM: xfrm: Allow xfrmi if_id to be updated by UPDSA
Nathan Harold [Fri, 20 Jul 2018 02:07:47 +0000 (19:07 -0700)]
[RAMEN9610-20741]UPSTREAM: xfrm: Allow xfrmi if_id to be updated by UPDSA

Allow attaching an SA to an xfrm interface id after
the creation of the SA, so that tasks such as keying
which must be done as the SA is created, can remain
separate from the decision on how to route traffic
from an SA. This permits SA creation to be decomposed
in to three separate steps:
1) allocation of a SPI
2) algorithm and key negotiation
3) insertion into the data path

Signed-off-by: Nathan Harold <nharold@google.com>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
(cherry picked from commit 5baf4f9c0035f3e33bb693a1a1e87599f6e804e6)
Signed-off-by: Benedict Wong <benedictwong@google.com>
Bug: 113046120
Change-Id: I45a4bf725f3b8eaa8dae3266f9c411febb4c8720

5 years ago[RAMEN9610-20741]UPSTREAM: xfrm: Remove xfrmi interface ID from flowi
Benedict Wong [Thu, 19 Jul 2018 17:50:44 +0000 (10:50 -0700)]
[RAMEN9610-20741]UPSTREAM: xfrm: Remove xfrmi interface ID from flowi

In order to remove performance impact of having the extra u32 in every
single flowi, this change removes the flowi_xfrm struct, prefering to
take the if_id as a method parameter where needed.

In the inbound direction, if_id is only needed during the
__xfrm_check_policy() function, and the if_id can be determined at that
point based on the skb. As such, xfrmi_decode_session() is only called
with the skb in __xfrm_check_policy().

In the outbound direction, the only place where if_id is needed is the
xfrm_lookup() call in xfrmi_xmit2(). With this change, the if_id is
directly passed into the xfrm_lookup_with_ifid() call. All existing
callers can still call xfrm_lookup(), which uses a default if_id of 0.

This change does not change any behavior of XFRMIs except for improving
overall system performance via flowi size reduction.

This change has been tested against the Android Kernel Networking Tests:

https://android.googlesource.com/kernel/tests/+/master/net/test

Signed-off-by: Benedict Wong <benedictwong@google.com>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
(cherry picked from commit bc56b33404599edc412b91933d74b36873e8ea25)
Bug: 113046120
Change-Id: Icd3a1ea08427b91c54a64318d9dbb9acfb5d429a

5 years ago[RAMEN9610-20741]UPSTREAM: xfrm: Allow Set Mark to be Updated Using UPDSA
Nathan Harold [Fri, 29 Jun 2018 22:07:10 +0000 (15:07 -0700)]
[RAMEN9610-20741]UPSTREAM: xfrm: Allow Set Mark to be Updated Using UPDSA

Allow UPDSA to change "set mark" to permit
policy separation of packet routing decisions from
SA keying in systems that use mark-based routing.

The set mark, used as a routing and firewall mark
for outbound packets, is made update-able which
allows routing decisions to be handled independently
of keying/SA creation. To maintain consistency with
other optional attributes, the set mark is only
updated if sent with a non-zero value.

The per-SA lock and the xfrm_state_lock are taken in
that order to avoid a deadlock with
xfrm_timer_handler(), which also takes the locks in
that order.

Signed-off-by: Nathan Harold <nharold@google.com>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
(cherry picked from commit 6d8e85ffe17895d7bc632dfbaa9e2e33b22fe873)
Signed-off-by: Benedict Wong <benedictwong@google.com>
Bug: 113046120
Change-Id: Ie7ab34ca38aedb034cf5aa83457c552c43f4f566

5 years ago[RAMEN9610-20741]UPSTREAM: xfrm: Add virtual xfrm interfaces
Steffen Klassert [Tue, 12 Jun 2018 12:07:12 +0000 (14:07 +0200)]
[RAMEN9610-20741]UPSTREAM: xfrm: Add virtual xfrm interfaces

This patch adds support for virtual xfrm interfaces.
Packets that are routed through such an interface
are guaranteed to be IPsec transformed or dropped.
It is a generic virtual interface that ensures IPsec
transformation, no need to know what happens behind
the interface. This means that we can tunnel IPv4 and
IPv6 through the same interface and support all xfrm
modes (tunnel, transport and beet) on it.

Co-developed-by: Lorenzo Colitti <lorenzo@google.com>
Co-developed-by: Benedict Wong <benedictwong@google.com>
Signed-off-by: Lorenzo Colitti <lorenzo@google.com>
Signed-off-by: Benedict Wong <benedictwong@google.com>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
Acked-by: Shannon Nelson <shannon.nelson@oracle.com>
Tested-by: Benedict Wong <benedictwong@google.com>
Tested-by: Antony Antony <antony@phenome.org>
Reviewed-by: Eyal Birger <eyal.birger@gmail.com>
(cherry picked from commit f203b76d78092faf248db3f851840fbecf80b40e)
Bug: 113046120
Change-Id: I05e8fe1e8a8a4b01886504ce694ddda29e4fbec6

5 years ago[RAMEN9610-20741]UPSTREAM: xfrm: Add a new lookup key to match xfrm interfaces.
Steffen Klassert [Tue, 12 Jun 2018 12:07:07 +0000 (14:07 +0200)]
[RAMEN9610-20741]UPSTREAM: xfrm: Add a new lookup key to match xfrm interfaces.

This patch adds the xfrm interface id as a lookup key
for xfrm states and policies. With this we can assign
states and policies to virtual xfrm interfaces.

Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
Acked-by: Shannon Nelson <shannon.nelson@oracle.com>
Acked-by: Benedict Wong <benedictwong@google.com>
Tested-by: Benedict Wong <benedictwong@google.com>
Tested-by: Antony Antony <antony@phenome.org>
Reviewed-by: Eyal Birger <eyal.birger@gmail.com>
(cherry picked from commit 7e6526404adedf079279aa7aa11722deaca8fe2e)
Signed-off-by: Benedict Wong <benedictwong@google.com>
Bug: 113046120
Change-Id: I27d7757a374b0bd5f97c3e723773d6c7470a0717

5 years ago[RAMEN9610-20741]UPSTREAM: flow: Extend flow informations with xfrm interface id.
Steffen Klassert [Tue, 12 Jun 2018 12:06:57 +0000 (14:06 +0200)]
[RAMEN9610-20741]UPSTREAM: flow: Extend flow informations with xfrm interface id.

Add a new flowi_xfrm structure with informations needed to do
a xfrm lookup. At the moment it keeps the informations about
the new xfrm interface id needed to lookup xfrm interfaces
that are introduced with a followup patch. We need this new
lookup key as other possible keys, like the ifindex is
already part of the xfrm selector and used as a key to
enforce the output device after the transformation in the
policy/state lookup.

Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
Acked-by: Shannon Nelson <shannon.nelson@oracle.com>
Acked-by: Benedict Wong <benedictwong@google.com>
Tested-by: Benedict Wong <benedictwong@google.com>
Tested-by: Antony Antony <antony@phenome.org>
Reviewed-by: Eyal Birger <eyal.birger@gmail.com>
(cherry picked from commit d159ce7957eec306eacda672e5909e26675ca8ef)
Signed-off-by: Benedict Wong <benedictwong@google.com>
Bug: 113046120
Change-Id: I70b520d3cf67cd663e84868b0e7cc45ffa74d080

5 years ago[RAMEN9610-20741]UPSTREAM: xfrm: Extend the output_mark to support input direction...
Steffen Klassert [Tue, 12 Jun 2018 10:44:26 +0000 (12:44 +0200)]
[RAMEN9610-20741]UPSTREAM: xfrm: Extend the output_mark to support input direction and masking.

We already support setting an output mark at the xfrm_state,
unfortunately this does not support the input direction and
masking the marks that will be applied to the skb. This change
adds support applying a masked value in both directions.

The existing XFRMA_OUTPUT_MARK number is reused for this purpose
and as it is now bi-directional, it is renamed to XFRMA_SET_MARK.

An additional XFRMA_SET_MARK_MASK attribute is added for setting the
mask. If the attribute mask not provided, it is set to 0xffffffff,
keeping the XFRMA_OUTPUT_MARK existing 'full mask' semantics.

Co-developed-by: Tobias Brunner <tobias@strongswan.org>
Co-developed-by: Eyal Birger <eyal.birger@gmail.com>
Co-developed-by: Lorenzo Colitti <lorenzo@google.com>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
Signed-off-by: Tobias Brunner <tobias@strongswan.org>
Signed-off-by: Eyal Birger <eyal.birger@gmail.com>
Signed-off-by: Lorenzo Colitti <lorenzo@google.com>
(cherry picked from commit 9b42c1f179a614e11893ae4619f0304a38f481ae)
Signed-off-by: Benedict Wong <benedictwong@google.com>
Bug: 113046120
Change-Id: I582f0b460dc58f01e0c30afb6167725aa337d054

5 years ago[RAMEN9610-20741]UPSTREAM: xfrm: fix XFRMA_OUTPUT_MARK policy entry
Michal Kubecek [Wed, 29 Nov 2017 17:23:56 +0000 (18:23 +0100)]
[RAMEN9610-20741]UPSTREAM: xfrm: fix XFRMA_OUTPUT_MARK policy entry

This seems to be an obvious typo, NLA_U32 is type of the attribute, not its
(minimal) length.

Fixes: 077fbac405bf ("net: xfrm: support setting an output mark.")
Signed-off-by: Michal Kubecek <mkubecek@suse.cz>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
(cherry picked from commit e719135881f00c01ca400abb8a5dadaf297a24f9)
Signed-off-by: Benedict Wong <benedictwong@google.com>
Bug: 113046120
Change-Id: I4c1a8de03febfa246b99c7eb67d77f74a1e3ba93

5 years ago[RAMEN9610-20734][COMMON] lib: dss: register valid reserved memory
Donghyeok Choe [Sat, 27 Jul 2019 07:04:00 +0000 (16:04 +0900)]
[RAMEN9610-20734][COMMON] lib: dss: register valid reserved memory

for user build, debug snapshot minimize reserved area,
but both node exists in reserved mem node of device tree.
So, skip reserve invalid dss's reserved memory area.

Change-Id: I6d1c24edf61556d0a8c314cee7b2896e8c5c45a3
Signed-off-by: Donghyeok Choe <d7271.choe@samsung.com>
5 years ago[RAMEN9610-20734][COMMON] soc: samsung: clean dump_en when DEBUG_SNAPSHOT is disabled
Hosung Kim [Mon, 27 May 2019 15:38:43 +0000 (00:38 +0900)]
[RAMEN9610-20734][COMMON] soc: samsung: clean dump_en when DEBUG_SNAPSHOT is disabled

This commit supports CONFIG_DEBUG_SNAPSHOT is disabled.
If it does, dump_en bit is de-asserted, and then it prevents
into entering fastboot.

Change-Id: Ie4657ff6e4afcf93ece0e5139252aa469beec790
Signed-off-by: Hosung Kim <hosung0.kim@samsung.com>
5 years ago[RAMEN9610-20734][COMMON] lib: dss: fix to support DSS disabled
Hosung Kim [Fri, 24 May 2019 06:20:13 +0000 (15:20 +0900)]
[RAMEN9610-20734][COMMON] lib: dss: fix to support DSS disabled

This commit supports when CONFIG_DEBUG_SNAPSHOT is disabled.

Change-Id: I9706d1bb2b715fa7c4cf2a1059fa4498c9e451fc
Signed-off-by: Hosung Kim <hosung0.kim@samsung.com>
5 years ago[ERD][RAMEN9610-20672][MODAP-49764][COMMON] chub_ipc: fix spin_unlock error with...
Boojin Kim [Fri, 18 Oct 2019 05:10:28 +0000 (14:10 +0900)]
[ERD][RAMEN9610-20672][MODAP-49764][COMMON] chub_ipc: fix spin_unlock error with ipc evt full

This patch fixed spin_lock error with ipc evt full.
And then, Added the slient reset with ipc evt failure.

Change-Id: Ia5cef3f10b2b5fd1afe38ba54bbae085227872c0
Signed-off-by: Boojin Kim <boojin.kim@samsung.com>
5 years ago[ERD][RAMEN9610-20672][MODAP-49617][COMMON] chub: run nanohub_kthread after contexthu...
Boojin Kim [Fri, 18 Oct 2019 02:20:54 +0000 (11:20 +0900)]
[ERD][RAMEN9610-20672][MODAP-49617][COMMON] chub: run nanohub_kthread after contexthub_poweron

Change-Id: I3d17afb81db7606d4de4e037cb080a88d7196368
Signed-off-by: Boojin Kim <boojin.kim@samsung.com>
5 years ago[ERD][RAMEN9610-20672][COMMON] chub: add the validation of ipc index
Boojin Kim [Wed, 3 Jul 2019 02:39:19 +0000 (11:39 +0900)]
[ERD][RAMEN9610-20672][COMMON] chub: add the validation of ipc index

Change-Id: I621610545307bbc3fc1286fa2ff9efbcd55f8da7
Signed-off-by: Boojin Kim <boojin.kim@samsung.com>
5 years ago[RAMEN9610-20695][COMMON] wlbt: Add support for testPasspointCapability
Abhishek Chaudhary [Fri, 11 Oct 2019 18:13:28 +0000 (23:43 +0530)]
[RAMEN9610-20695][COMMON] wlbt: Add support for testPasspointCapability

For GTS need to add support for testPasspointCapability

Change-Id: I7b60487078297aa910bbb3546aa6e60f77d6766d
SCSC-Bug-Id: HOST-11169
Signed-off-by: Abhishek Chaudhary <ab.chaudhary@samsung.com>
5 years ago[RAMEN9610-20656]wlbt: Vts failed for configure_roaming API.
Srishti Piplani [Wed, 21 Aug 2019 12:56:43 +0000 (18:26 +0530)]
[RAMEN9610-20656]wlbt: Vts failed for configure_roaming API.

Modified set_bssid_blacklist to check proper length
for bssid attribute.

Change-Id: I0867246112f1059b2abf20ffdab171d2e733c695
SCSC-Bug-Id: HOST-10743
Signed-off-by: Himani Gupta <himani.g2@samsung.com>
5 years ago[RAMEN9610-20643][NEUS7920-6688][ERD][COMMON] chub: fix prevent error (CID:275678...
Boojin Kim [Thu, 10 Oct 2019 06:36:53 +0000 (15:36 +0900)]
[RAMEN9610-20643][NEUS7920-6688][ERD][COMMON] chub: fix prevent error (CID:275678,275715)

Change-Id: I4fef5095fe76fb8a6951f586f65e8a5bf2a39a97
Signed-off-by: Boojin Kim <boojin.kim@samsung.com>
5 years ago[RAMEN9610-20563][9610] : drivers : ccic : fix ccic rp threshold operating Source
Jinsu Park [Mon, 14 Oct 2019 06:53:02 +0000 (15:53 +0900)]
[RAMEN9610-20563][9610] : drivers : ccic : fix ccic rp threshold operating Source

Change-Id: I57e76dc68a94f1f8085b71d783f2b8145f816c99
Signed-off-by: Jinsu Park <js00.park@samsung.com>
5 years ago[ERD][RAMEN9610-20560][MODAP-47871][COMMON] chub: check ipc index and run status
Boojin Kim [Fri, 11 Oct 2019 03:43:27 +0000 (12:43 +0900)]
[ERD][RAMEN9610-20560][MODAP-47871][COMMON] chub: check ipc index and run status

This patch checks the ipc index and the run status of chub.

Change-Id: I9165b1374641520965567493317c918a245e1d8d
Signed-off-by: Boojin Kim <boojin.kim@samsung.com>
5 years ago[RAMEN9610-20555][COMMON] scsi: ufs: Add device reset when return error in query...
JaeHun Jung [Fri, 11 Oct 2019 04:54:39 +0000 (13:54 +0900)]
[RAMEN9610-20555][COMMON] scsi: ufs: Add device reset when return error in query cmd.

UFS device is not responsed when return -EAGAIN.
So, It need device reset for working.

================================================================================================
<3>[  715.766410,1] exynos-ufs 13520000.ufs: ufshcd_print_pwr_info:[RX, TX]: gear=[1, 1], lane[1, 1], pwr[SLOWAUTO_MODE, SLOWAUTO_MODE], rate = 0
<6>[  715.768915,1] exynos-ufs 13520000.ufs: UFS link established
<3>[  716.376936,3] exynos-ufs 13520000.ufs: ufshcd_query_flag: Sending flag query for idn 1 failed, err = -11
<6>[  716.578308,1] acpm_noti_mif_callback : req 1794000 KHz
<3>[  716.990135,3] exynos-ufs 13520000.ufs: ufshcd_query_flag: Sending flag query for idn 1 failed, err = -11
<6>[  717.434411,1] acpm_noti_mif_callback : req 419000 KHz
<3>[  717.603532,3] exynos-ufs 13520000.ufs: ufshcd_query_flag: Sending flag query for idn 1 failed, err = -11
<3>[  717.603555,3] exynos-ufs 13520000.ufs: ufshcd_query_flag_retry: query attribute, opcode 6, idn 1, failed with error -11 after 3 retires
<3>[  717.603567,3] exynos-ufs 13520000.ufs: ufshcd_complete_dev_init setting fDeviceInit flag failed with error -11
<3>[  717.603577,3] exynos-ufs 13520000.ufs: ufshcd_probe_hba failed with err -11, retrying:1
....
<3>[  748.447849,3] exynos-ufs 13520000.ufs: UPIU[2] - issue time 717847005 us
<3>[  748.447868,3] exynos-ufs 13520000.ufs: UPIU[2] - Transfer Request Descriptor phys@0x8fc042040
...
<3>[  748.753470,3] exynos-ufs 13520000.ufs: ufshcd_issue_tm_cmd: task management cmd 0x80 timed-out
<3>[  748.753553,3] exynos-ufs 13520000.ufs: ufshcd_abort: no response from device. tag = 2, err -110
<3>[  748.753594,3] exynos-ufs 13520000.ufs: ufshcd_abort: query task failed with err -110
<3>[  748.753636,3] exynos-ufs 13520000.ufs: ufshcd_abort: failed with err -110
<3>[  748.753718,3] exynos-ufs 13520000.ufs: ufshcd_abort: tag:1, cmd:0x2a, lba:0x00bb993c, sct:0x0001, retries 0
<3>[  748.753764,3] exynos-ufs 13520000.ufs: ufshcd_abort: Device abort task at tag 1
=================================================================================================

Change-Id: I73609250b8454d3b0dfd928cb1643992f2117672
Signed-off-by: JaeHun Jung <jh0801.jung@samsung.com>
5 years ago[RAMEN9610-20538]ion: fix wrong argument for dma_flush_area.
Hyesoo Yu [Fri, 12 Jul 2019 01:53:29 +0000 (10:53 +0900)]
[RAMEN9610-20538]ion: fix wrong argument for dma_flush_area.

Change-Id: Idb3933c35b9b53d6d7c30c03db3d6d91a9f00034
Signed-off-by: Hyesoo Yu <hyesoo.yu@samsung.com>
5 years ago[RAMEN9610-20413][lv] host update 10.6.1.1 for lenovo only
Youngsoo [Thu, 26 Sep 2019 06:30:45 +0000 (15:30 +0900)]
[RAMEN9610-20413][lv] host update 10.6.1.1 for lenovo only

add ipv4 multicast packet filter again.
add prevent issue fix : 310263

Change-Id: I3895000b184dd6c8731b7ead4343056deb9d80cc
Signed-off-by: Youngsoo <youngss.kim@samsung.com>
5 years ago[RAMEN9610-20413][9610] wlbt: SCSC Driver version 10.6.1.0
Tarun Karela [Tue, 24 Sep 2019 15:34:00 +0000 (16:34 +0100)]
[RAMEN9610-20413][9610] wlbt: SCSC Driver version 10.6.1.0

SCSC Driver version 10.6.1.0

Change-Id: Ib3cae4b7bce4b448477a1d5d0e92e4bad364282a
SCSC-Bug-Id: Rels-3171
Signed-off-by: Tarun Karela <t.karela@samsung.com>
5 years ago[RAMEN9610-20413][9610] [9630] wlbt: Delete SCSC drivers before update
Tarun Karela [Tue, 24 Sep 2019 15:33:02 +0000 (16:33 +0100)]
[RAMEN9610-20413][9610] [9630] wlbt: Delete SCSC drivers before update

Remove existing SCSC drivers before applying update

Change-Id: Ia9b0382ae916227a19498733ac362e8fdf752066
SCSC-Bug-Id: Rels-3171
Signed-off-by: Tarun Karela <t.karela@samsung.com>
5 years ago[RAMEN9610-20350][9610] drivers: muic: support bad TA
Kim Taejeong [Sun, 11 Aug 2019 06:45:49 +0000 (15:45 +0900)]
[RAMEN9610-20350][9610] drivers: muic: support bad TA

Change-Id: I605bf8bbd5df0dfeea091836bd90cdeca5dfad34
Signed-off-by: Kim Taejeong <tj.kim@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[ERD][RAMEN9610-20347]arm64: defconfig: add CPU_FREQ_TIMES
Sangkyu Kim [Fri, 27 Sep 2019 15:49:11 +0000 (00:49 +0900)]
[ERD][RAMEN9610-20347]arm64: defconfig: add CPU_FREQ_TIMES

Change-Id: I9292c790830c406e80d1b623d6946e0ba79fbe19
Signed-off-by: Sangkyu Kim <skwith.kim@samsung.com>
5 years ago[ERD][RAMEN9610-20347]ANDROID: cpufreq: times: optimize proc files
Sangkyu Kim [Fri, 27 Sep 2019 14:14:53 +0000 (23:14 +0900)]
[ERD][RAMEN9610-20347]ANDROID: cpufreq: times: optimize proc files

The majority of the time spent reading /proc/uid_time_in_state is due
to seq_printf calls. Use the faster seq_put_* variations instead.

Also skip empty hash buckets in uid_seq_next for a further performance
improvement.

Bug: 111216804
Test: Read /proc/uid_time_in_state and confirm output is sane
Test: Compare read times to confirm performance improvement
Change-Id: I9a735a591b0f1d879dba8e1d9dd05bb47e18a9c5
Signed-off-by: Connor O'Brien <connoro@google.com>
5 years ago[ERD][RAMEN9610-20347]ANDROID: cpufreq: times: add /proc/uid_concurrent_{active,polic...
Sangkyu Kim [Fri, 27 Sep 2019 14:12:34 +0000 (23:12 +0900)]
[ERD][RAMEN9610-20347]ANDROID: cpufreq: times: add /proc/uid_concurrent_{active,policy}_time

In order to model the energy used by the cpu, we need to expose cpu
time information to userspace.  We can use this information to blame
uids for the energy they are using.

This patch adds 2 files:

/proc/uid_concurrent_active_time outputs the time each uid spent
running with 1 to num_possible_cpus online and not idle.

For instance, if 4 cores are online and active for 50ms and the uid is
running on one of the cores, the uid should be blamed for 1/4 of the
base energy used by the cpu when 1 or more cores is active.

/proc/uid_concurrent_policy_time outputs the time each uid spent
running on group of cpu's with the same policy with 1 to
num_related_cpus online and not idle.

For instance, if 2 cores that are a part of the same policy are online
and active for 50ms and the uid is running on one of the cores, the
uid should be blamed for 1/2 of the energy that is used everytime one
or more cpus in the same policy is active.

This patch is based on commit c89e69136fec ("ANDROID: cpufreq:
uid_concurrent_active_time") and commit 989212536842 ("ANDROID:
cpufreq: uid_concurrent_policy_time") in the android-msm-wahoo-4.4
kernel by Marissa Wall.

Bug: 111216804
Test: cat files on hikey960 and confirm output is reasonable
Change-Id: I075fef030c261b47831ae8d4ddb286ee9d8b9347
Signed-off-by: Connor O'Brien <connoro@google.com>
5 years ago[ERD][RAMEN9610-20347]ANDROID: Fix massive cpufreq_times memory leaks
Sangkyu Kim [Fri, 27 Sep 2019 14:07:44 +0000 (23:07 +0900)]
[ERD][RAMEN9610-20347]ANDROID: Fix massive cpufreq_times memory leaks

Every time _cpu_up() is called for a CPU, idle_thread_get() is called
which then re-initializes a CPU's idle thread that was already
previously created and cached in a global variable in
smpboot.c. idle_thread_get() calls init_idle() which then calls
__sched_fork(). __sched_fork() is where cpufreq_task_times_init() is,
and cpufreq_task_times_init() allocates memory for the task struct's
time_in_state array.

Since idle_thread_get() reuses a task struct instance that was already
previously created, this means that every time it calls init_idle(),
cpufreq_task_times_init() allocates this array again and overwrites
the existing allocation that the idle thread already had.

This causes memory to be leaked every time a CPU is onlined. In order
to fix this, move allocation of time_in_state into _do_fork to avoid
allocating it at all for idle threads. The cpufreq times interface is
intended to be used for tracking userspace tasks, so we can safely
remove it from the kernel's idle threads without killing any
functionality.

But that's not all!

Task structs can be freed outside of release_task(), which creates
another memory leak because a task struct can be freed without having
its cpufreq times allocation freed. To fix this, free the cpufreq
times allocation at the same time that task struct allocations are
freed, in free_task().

Since free_task() can also be called in error paths of copy_process()
after dup_task_struct(), set time_in_state to NULL immediately after
calling dup_task_struct() to avoid possible double free.

Bug description and fix adapted from patch submitted by
Sultan Alsawaf <sultanxda@gmail.com> at
https://android-review.googlesource.com/c/kernel/msm/+/700134

Bug: 110044919
Test: Hikey960 builds, boots & reports /proc/<pid>/time_in_state
correctly
Change-Id: I12fe7611fc88eb7f6c39f8f7629ad27b6ec4722c
Signed-off-by: Connor O'Brien <connoro@google.com>
5 years ago[ERD][RAMEN9610-20347]ANDROID: cpufreq: Add time_in_state to /proc/uid directories
Sangkyu Kim [Fri, 27 Sep 2019 14:03:54 +0000 (23:03 +0900)]
[ERD][RAMEN9610-20347]ANDROID: cpufreq: Add time_in_state to /proc/uid directories

Add per-uid files that report the data in binary format rather than
text, to allow faster reading & parsing by userspace.

Signed-off-by: Connor O'Brien <connoro@google.com>
Bug: 72339335
Bug: 70951257
Test: compare values to those reported in /proc/uid_time_in_state
Change-Id: I463039ea7f17b842be4c70024fe772539fe2ce02

5 years ago[ERD][RAMEN9610-20325][COMMON] fimc-is2: Fix prevent issue
Sanghoon Lee [Mon, 15 Jul 2019 07:07:43 +0000 (16:07 +0900)]
[ERD][RAMEN9610-20325][COMMON] fimc-is2: Fix prevent issue

ISSUE JIRA ID: RAMEN9610-17294, RAMEN9610-17295, RAMEN9610-17297
PREVENT ID: 80694, 80703, 80723
PR JIRA ID: CSWPR-59, CSWPR-124

Change-Id: I77342f00f03d23618183789df309b9a222340594
Signed-off-by: Sanghoon Lee <shoon114.lee@samsung.com>
5 years ago[ERD][RAMEN9610-20325][COMMON] fimc-is2: Fix prevent issues
Sanghoon Lee [Wed, 24 Jul 2019 07:21:45 +0000 (16:21 +0900)]
[ERD][RAMEN9610-20325][COMMON] fimc-is2: Fix prevent issues

ISSUE JIRA ID: MAKA9820-6229, NEUS7920-327, RAMEN9610-16606, RAMEN9610-18289
PR JIRA ID: CSWPR-124

Change-Id: I275d7c1e2d9de196c6f42aaae065879401d95e8e
Signed-off-by: Sanghoon Lee <shoon114.lee@samsung.com>
5 years ago[ERD][RAMEN9610-20321][9610] driver: chub: exit resume when not working
Sukwon Ryoo [Fri, 27 Sep 2019 10:33:26 +0000 (19:33 +0900)]
[ERD][RAMEN9610-20321][9610] driver: chub: exit resume when not working

Especially in charger mode

Change-Id: I58f40b4ba373b3832e5d2b71add8d07055d99eaa
Signed-off-by: Sukwon Ryoo <sw.ryoo@samsung.com>
5 years ago[RAMEN9610-20318][9610] arm64: configs: add config for resolving VtsKernelNetTest...
Jiyoung Jeong [Fri, 27 Sep 2019 11:22:39 +0000 (20:22 +0900)]
[RAMEN9610-20318][9610] arm64: configs: add config for resolving VtsKernelNetTest fail

Change-Id: Ic683efe27c6c1df4396ff4a89d73b1eb295121d3
Signed-off-by: Jiyoung Jeong <ji_0.jeong@samsung.com>
5 years ago[RAMEN9610-20297][9610] vipx: fix prevent defects
Sanghwa Park [Fri, 27 Sep 2019 00:45:59 +0000 (09:45 +0900)]
[RAMEN9610-20297][9610] vipx: fix prevent defects

prevent defects (275231, 275562) is fixed

Change-Id: Ia18640d45964f8a28a1d90589cf42ebbdb04e9dc
Signed-off-by: Sanghwa Park <senius.park@samsung.com>
5 years ago[ERD][RAMEN9610-20296][COMMON] driver: chub: handle invalid logbuf index
Sukwon Ryoo [Thu, 26 Sep 2019 07:20:56 +0000 (16:20 +0900)]
[ERD][RAMEN9610-20296][COMMON] driver: chub: handle invalid logbuf index

When an invalid logbuffer index issue happened,
1. reset eq and dq to 0
2. chub dump
also resolves prevent CID 275510, 275336 and 276075

Change-Id: I6b2f9205b4b8ed31f135e1f04a6963b9aa8bb4f0
Signed-off-by: Sukwon Ryoo <sw.ryoo@samsung.com>
5 years ago[RAMEN9610-20095][lv] host update 10.5.1.1 for lenovo only
Youngsoo [Mon, 16 Sep 2019 05:16:39 +0000 (14:16 +0900)]
[RAMEN9610-20095][lv] host update 10.5.1.1 for lenovo only

add ipv4 multicast packet filter again.

Change-Id: I6c801c86787e257cd3f04e898e2da269aca0289d
Signed-off-by: Youngsoo <youngss.kim@samsung.com>
5 years ago[RAMEN9610-20095][9630][3830][9610] wlbt: SCSC WLBT Driver Ver. 10.5.1.0
Tarun Karela [Tue, 10 Sep 2019 14:26:57 +0000 (15:26 +0100)]
[RAMEN9610-20095][9630][3830][9610] wlbt: SCSC WLBT Driver Ver. 10.5.1.0

WLBT Driver relase : Version 10.5.1.0

Change-Id: Ia1c5822c979526103ffa9ca2a7e62a59a2991970
SCSC-Bug-Id: Rels-3147
Signed-off-by: Tarun Karela <t.karela@samsung.com>
5 years ago[RAMEN9610-20095][9630][3830][9610] wlbt: Delete Scsc Drivers
Tarun Karela [Tue, 10 Sep 2019 14:26:09 +0000 (15:26 +0100)]
[RAMEN9610-20095][9630][3830][9610] wlbt: Delete Scsc Drivers

Delete Scsc drivers from upstream kernel in prepartion
of appling new SCSC WLBT Driver release
for RAMEN Q

Change-Id: Ic36f3d98770f9e9883e7f5f67cf15769bb10365a
SCSC-Bug-Id: Rels-3147
Signed-off-by: Tarun Karela <t.karela@samsung.com>
5 years ago[RAMEN9610-20090][9610] dts: battery: change max_rawsoc initial value
Seongwoo hong [Fri, 20 Sep 2019 01:19:21 +0000 (10:19 +0900)]
[RAMEN9610-20090][9610] dts: battery: change max_rawsoc initial value

Change-Id: I0e90fdf12c1c9b4ae4e658a9619e78798b667143
Signed-off-by: Seongwoo hong <seong.hong@samsung.com>
5 years ago[RAMEN9610-20069][9610] drivers: fuelgauge: change recalculation condition for SOCni
Keunho Hwang [Mon, 1 Jul 2019 07:25:37 +0000 (16:25 +0900)]
[RAMEN9610-20069][9610] drivers: fuelgauge: change recalculation condition for SOCni

Change-Id: Ia83139177c09bb9471728d1597d71d1d802f7579
Signed-off-by: Keunho Hwang <keunho.hwang@samsung.com>
5 years ago[RAMEN9610-20040][9609] media: radio: Sync p branch update
Yunsu Kim [Wed, 18 Sep 2019 07:16:04 +0000 (16:16 +0900)]
[RAMEN9610-20040][9609] media: radio: Sync p branch update

Change-Id: I61ccfb5d760fa1d3fbb3adc2800347a08380238e
Signed-off-by: Yunsu Kim <iamyunsu.kim@samsung.com>
5 years ago[RAMEN9610-19845][9610] vipx: fix prevent defects
Sanghwa Park [Tue, 10 Sep 2019 15:24:03 +0000 (00:24 +0900)]
[RAMEN9610-19845][9610] vipx: fix prevent defects

  275134: Uninitialized scalar variable
  275231: Uninitialized scalar variable
  275245: Uninitialized pointer read
  275283: Uninitialized scalar variable
  275562: Uninitialized scalar variable
  275638: Uninitialized scalar variable

Change-Id: I12838a018382220052c9c8e99a3e79c8caa4699c
Signed-off-by: Sanghwa Park <senius.park@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19755]wlbt: Resource Leak prevent issue in APF
Srishti Piplani [Thu, 5 Sep 2019 09:50:05 +0000 (15:20 +0530)]
[RAMEN9610-19755]wlbt: Resource Leak prevent issue in APF

Free the program variable, before doing a kmalloc,
in order to fix resource leak prevent issue.

Change-Id: I841c958401abeb7a359e8dacae6da530ee4a39a9
SCSC-Bug-Id: HOST-10865
Signed-off-by: Srishti Piplani <srishti.p@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19737][MODAP-40430] Fix CFI panic on ip_expire
dujeonglee [Thu, 5 Sep 2019 01:01:47 +0000 (10:01 +0900)]
[RAMEN9610-19737][MODAP-40430] Fix CFI panic on ip_expire

Change-Id: I678395a3dc85ceb833532379653d2dd2b8670796
Signed-off-by: dujeonglee <dujeong.lee@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19721][COMMON] media: mfc: DRV5.0: apply spin_lock to ctx_ready
Sunyoung Kang [Tue, 26 Feb 2019 00:22:24 +0000 (09:22 +0900)]
[RAMEN9610-19721][COMMON] media: mfc: DRV5.0: apply spin_lock to ctx_ready

The ctx_ready() and set_bit() should be synchronized.
So this applies the spin_lock to ctx_ready() by using
new function mfc_ctx_ready_set_bit().

Change-Id: I366b64ccfaa18fe929c1a174531aa52c5a97b094
Signed-off-by: Sunyoung Kang <sy0816.kang@samsung.com>
5 years ago[RAMEN9610-19721][COMMON] media: mfc: fix the prevent issue
seungmin.ahn [Tue, 18 Jun 2019 05:12:55 +0000 (14:12 +0900)]
[RAMEN9610-19721][COMMON] media: mfc: fix the prevent issue

Fixed null pointer dereference(FORWARD_NULL)

Change-Id: Idb8f7f271d49ce0ac936e0885bd868d7eb94ea39
Signed-off-by: seungmin.ahn <seungmin.ahn@samsung.com>
5 years ago[RAMEN9610-19721][COMMON] media: mfc: allocation failure doesn't go to panic
Ayoung Sim [Mon, 1 Jul 2019 08:17:20 +0000 (17:17 +0900)]
[RAMEN9610-19721][COMMON] media: mfc: allocation failure doesn't go to panic

Change-Id: I85735db02ac6363c96eda760266378cb8dda9601
Signed-off-by: Ayoung Sim <a.sim@samsung.com>
5 years ago[RAMEN9610-19721][COMMON] media: mfc: adjust FRAME_RATE_RESOLUTION scope
Ayoung Sim [Tue, 18 Jun 2019 04:17:08 +0000 (13:17 +0900)]
[RAMEN9610-19721][COMMON] media: mfc: adjust FRAME_RATE_RESOLUTION scope

FRAME_RATE_RESOLUTION has been used based on 1000ms
in order to calculate with timestamp.
But for H.263 codec only 8 bit is used and maximum value
can be 0xFF(256).
We adjust the FRAME_RATE_RESOLUTION to 100 in case of only H.263.

Change-Id: I4766b65828beba435fe495804b70146218e2dacd
Signed-off-by: Ayoung Sim <a.sim@samsung.com>
5 years ago[RAMEN9610-19721][COMMON] media: mfc: add the lock for qos_queue list
Ayoung Sim [Fri, 31 May 2019 08:10:06 +0000 (17:10 +0900)]
[RAMEN9610-19721][COMMON] media: mfc: add the lock for qos_queue list

Change-Id: Id400dc5dc400b7de17c8aa1157d179c11026d2af
Signed-off-by: Ayoung Sim <a.sim@samsung.com>
5 years ago[RAMEN9610-19706][9610] wlbt: WLBT Kernel Driver 10.3.1.0
Tarun Karela [Thu, 29 Aug 2019 16:46:44 +0000 (17:46 +0100)]
[RAMEN9610-19706][9610] wlbt: WLBT Kernel Driver 10.3.1.0

WLBT kernel driver release scsc_release_10.3.1.0_mx450_p_ww

Change-Id: I4247b339fee79185c052c9bc486c69eb4b7646f0
SCSC-Bug-Id: Rels-3122
Signed-off-by: Tarun Karela <t.karela@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19688][9610] PMIC: RTC: Poweroff Alarm WA
Kun-Pil Jung [Tue, 25 Jun 2019 23:41:54 +0000 (08:41 +0900)]
[RAMEN9610-19688][9610] PMIC: RTC: Poweroff Alarm WA

Change-Id: Ib5f3de229bec484947f08743e2657a54fd142268
Signed-off-by: Kun-Pil Jung <kp.jung@samsung.com>
5 years ago[RAMEN9610-19688][COMMON] drivers: battery: Skip select pdo work
Keunho Hwang [Tue, 21 May 2019 01:55:52 +0000 (01:55 +0000)]
[RAMEN9610-19688][COMMON] drivers: battery: Skip select pdo work

Change-Id: Ic5559dd07d5f80e0bbe7efc58c110b40f8aebed8
Signed-off-by: Keunho Hwang <keunho.hwang@samsung.com>
5 years ago[RAMEN9610-19688][Common] s2mpu09: use ldo scp interrupts
Jieun Yi [Mon, 13 May 2019 02:01:18 +0000 (02:01 +0000)]
[RAMEN9610-19688][Common] s2mpu09: use ldo scp interrupts

Change-Id: Ica4639a4826ddbb05dbb29a15553768cf62ae7f6
Signed-off-by: Jieun Yi <jieun.yi@samsung.com>
5 years ago[RAMEN9610-19685][9630] drivers: gpu: disable MALI_DMA_BUF_LEGACY_COMPAT
SeYeong Byeon [Thu, 5 Sep 2019 01:35:04 +0000 (10:35 +0900)]
[RAMEN9610-19685][9630] drivers: gpu: disable MALI_DMA_BUF_LEGACY_COMPAT

Disables cache flush on dma buf map.
This is not needed anymore and enabling this option
may cause performance issues.

Change-Id: I6278f2ebd52e28b63123aec2cc8b4b1cd3f098f1
Signed-off-by: SeYeong Byeon <sy.byeon@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19678][COMMON] arch: dts: Enable runtime PM ignore for SD card.
JaeHun Jung [Wed, 4 Sep 2019 06:44:09 +0000 (15:44 +0900)]
[RAMEN9610-19678][COMMON] arch: dts: Enable runtime PM ignore for SD card.

Change-Id: Idd546adde3dfeaaec9af1d655b4e28e2d6251c59
Signed-off-by: JaeHun Jung <jh0801.jung@samsung.com>
5 years ago[RAMEN9610-19678][COMMON] mmc: dw_mmc: Add ignore runtime PM notify.
JaeHun Jung [Tue, 25 Jun 2019 02:20:42 +0000 (11:20 +0900)]
[RAMEN9610-19678][COMMON] mmc: dw_mmc: Add ignore runtime PM notify.

MMC does not use runtime PM.
So, Driver don't need register notifier for runtime PM.

Change-Id: I16cd8ded2c21fb00507f77edb3456e826f1d8802
Signed-off-by: JaeHun Jung <jh0801.jung@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19678][COMMON] mmc: dw_mmc: Change regulator_disable from tasklet to workq...
JaeHun Jung [Thu, 30 May 2019 08:21:19 +0000 (17:21 +0900)]
[RAMEN9610-19678][COMMON] mmc: dw_mmc: Change regulator_disable from tasklet to workqueue.

Regulator disable function has mutex_lock. And, mutex_lock has might_sleep().
It can not use in ISR & BH(bottom Half).
So, Using WQ with WQ_UNBOUND, WQ_HIGHPRI for execution.

Change-Id: I4f7a3d1b8d5a27000fb61ee9feb321749c956f59
Signed-off-by: JaeHun Jung <jh0801.jung@samsung.com>
5 years ago[RAMEN9610-19689]driver: staging: chub change chub_resume to complete
Sukmin Kang [Tue, 3 Sep 2019 07:52:55 +0000 (16:52 +0900)]
[RAMEN9610-19689]driver: staging: chub change chub_resume to complete

Change-Id: I66f433c02576a8ae7b22b041333439af2b698176
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19641][COMMON] ext2: support statx syscall
hgchu [Wed, 31 Jul 2019 05:01:06 +0000 (14:01 +0900)]
[RAMEN9610-19641][COMMON] ext2: support statx syscall

Since statx, every filesystem should fill the attributes/attributes_mask
in routine getattr. But the generic_fillattr has not fill that, so add
ext2_getattr to do this. This can fix generic/424 while testing ext2.

Change-Id: I08fa576ebf8191462290f81bdd5fb93d79018b57
Signed-off-by: hgchu <hg.chu@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19639][COMMON] usb: check cdev in retry configuration
Kisang Lee [Thu, 23 May 2019 10:14:37 +0000 (19:14 +0900)]
[RAMEN9610-19639][COMMON] usb: check cdev in retry configuration

Change-Id: I125d4c004c84b33c41c842c49032eeef3b157d0f
Signed-off-by: Kisang Lee <kisang80.lee@samsung.com>
5 years ago[RAMEN9610-19639][COMMON] usb: modified to re-try usb enumeration 5times
SEO HOYOUNG [Wed, 15 May 2019 10:34:41 +0000 (19:34 +0900)]
[RAMEN9610-19639][COMMON] usb: modified to re-try usb enumeration 5times

Change-Id: I2f4cfdb8ded582ae77b41a573de813390827304e
Signed-off-by: SEO HOYOUNG <hy50.seo@samsung.com>
5 years ago[RAMEN9610-19639][COMMON] usb: add DCTL run/stop when enumeration fail.
SEO HOYOUNG [Mon, 13 May 2019 10:44:06 +0000 (19:44 +0900)]
[RAMEN9610-19639][COMMON] usb: add DCTL run/stop when enumeration fail.

Change-Id: I0da546bc9c2053c3f5e8f2867022577919c3c74f
Signed-off-by: SEO HOYOUNG <hy50.seo@samsung.com>
5 years ago[RAMEN9610-19622] Save CP crash infomation when occured reset without dump
Jiyoung Jeong [Thu, 14 Mar 2019 15:00:01 +0000 (00:00 +0900)]
[RAMEN9610-19622] Save CP crash infomation when occured reset without dump

Change-Id: I2e087a78a4a33f8092b0d4b34d0e6dd70488f47d
Signed-off-by: Jiyoung Jeong <ji_0.jeong@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19621][9610] ASoC: abox: Direct clock control
ShinHyung [Tue, 4 Jun 2019 09:41:50 +0000 (18:41 +0900)]
[RAMEN9610-19621][9610] ASoC: abox: Direct clock control

To prevent the failure of the freezing task when entering suspend mode,
Change clock control method from gear_sync to set_rate.

Change-Id: Ieee64f5c90c7b4650de7259e32ca845190dbc8a9
Signed-off-by: ShinHyung <s47.kang@samsung.com>
5 years ago[RAMEN9610-19621][9610] ASoC: abox: added wake_lock to guarantee abox resume completion.
ShinHyung [Wed, 5 Jun 2019 08:58:48 +0000 (17:58 +0900)]
[RAMEN9610-19621][9610] ASoC: abox: added wake_lock to guarantee abox resume completion.

abox_boot_done_work_func(resume operation) didn't work before starting suspend scequence.
To avoid it, Added wake_lock to guarantee abox resume completion.

Change-Id: I531fbda221aaae4782e786e6e8673a7781803975
Signed-off-by: ShinHyung <s47.kang@samsung.com>
5 years ago[RAMEN9610-19595]muic: Support India Turbo-charger (SC-25)
Keunho Hwang [Tue, 9 Jul 2019 08:46:50 +0000 (17:46 +0900)]
[RAMEN9610-19595]muic: Support India Turbo-charger (SC-25)

- Set VNMON Vref 0.5V -> 0.4V
- Set DP_src 0.6 -> 0.75

Change-Id: Iac23950c195a0097f3f0b3ef8e611188ffb204f5
Signed-off-by: Keunho Hwang <keunho.hwang@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19595]ccic : fix init cc detach debounce for battery pack
Junhan Bae [Tue, 25 Jun 2019 03:46:32 +0000 (12:46 +0900)]
[RAMEN9610-19595]ccic : fix init cc detach debounce for battery pack

Change-Id: I66cad46ed950527543e96ca49fd84ca6de3822ff
Signed-off-by: Junhan Bae <junhan84.bae@samsung.com>
5 years ago[RAMEN9610-19595]ccic : add function which control abnormal attach
Junhan Bae [Fri, 14 Jun 2019 01:44:01 +0000 (10:44 +0900)]
[RAMEN9610-19595]ccic : add function which control abnormal attach

Change-Id: Ie888e46deb67ea81c0ec5e160978a42802b9477e
Signed-off-by: Junhan Bae <junhan84.bae@samsung.com>
5 years ago[RAMEN9610-19595]ccic : fix ccic rp source when attach source
Junhan Bae [Wed, 29 May 2019 06:45:58 +0000 (15:45 +0900)]
[RAMEN9610-19595]ccic : fix ccic rp source when attach source

Change-Id: I4c9570f760add4f7b60e358b2662bcd7d6854489
Signed-off-by: Junhan Bae <junhan84.bae@samsung.com>
5 years ago[RAMEN9610-19594][COMMON][NFC] Change nfc related config setting
Wonchul Shin [Tue, 3 Sep 2019 07:13:06 +0000 (16:13 +0900)]
[RAMEN9610-19594][COMMON][NFC] Change nfc related config setting

- Remove LDO_EN pin settings that are not required in ERD B/D

Change-Id: I7f2f880daf35cf7f4a358bfbeb1c9c8e0677e853
Signed-off-by: Wonchul Shin <wchuls.shin@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19593][COMMON][MODAP-30279] ntc_thermistor: Update ncpXXxh103 table
Hyeonseong Gil [Tue, 21 May 2019 06:00:32 +0000 (15:00 +0900)]
[RAMEN9610-19593][COMMON][MODAP-30279] ntc_thermistor: Update ncpXXxh103 table

Change-Id: I23a11145d4db70e178fdce8f22bb52e622c1f580
Signed-off-by: Hyeonseong Gil <hs.gil@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19588][COMMON] pinctrl: samsung: Add Exynos pin debug state
Jaehyoung Choi [Tue, 21 May 2019 04:34:05 +0000 (13:34 +0900)]
[RAMEN9610-19588][COMMON] pinctrl: samsung: Add Exynos pin debug state

In pin drvdata, you can see the current status of each pin.

Change-Id: I1eca9c3e5cbff60fba4bda6530a9f8435eaab28b
Signed-off-by: Jaehyoung Choi <jkkkkk.choi@samsung.com>
Signed-off-by: Shinbeom Choi <sbeom.choi@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19587][COMMON] touchscreen: synaptics: Fix prevent issue
Jaehyoung Choi [Mon, 17 Jun 2019 07:11:22 +0000 (16:11 +0900)]
[RAMEN9610-19587][COMMON] touchscreen: synaptics: Fix prevent issue

Change-Id: I56071262458b93028ffa703e7eba1094ae229c34
Signed-off-by: Jaehyoung Choi <jkkkkk.choi@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19586]vsprintf: fix data type of variable in string_nocheck()
Youngmin Nam [Mon, 10 Jun 2019 08:15:37 +0000 (17:15 +0900)]
[RAMEN9610-19586]vsprintf: fix data type of variable in string_nocheck()

This patch fixes data type of precision with int.
The precision is declared as signed int in struct printf_spec.

Change-Id: Iaa6e2d074ed9d4ca191a8366489a394d79b62ac1
Signed-off-by: Youngmin Nam <youngmin.nam@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19423] wlbt: increase filter id for adnormal multicast
Youngsoo [Thu, 22 Aug 2019 08:25:47 +0000 (17:25 +0900)]
[RAMEN9610-19423] wlbt: increase filter id for adnormal multicast

Change-Id: Ib4e001d96015de9a9cd016a379c699a99a229453
Signed-off-by: Youngsoo <youngss.kim@samsung.com>
5 years ago[RAMEN9610-19423] wlbt: filter abnormal ipv4 multicast packet
dujeonglee [Fri, 24 May 2019 12:05:43 +0000 (21:05 +0900)]
[RAMEN9610-19423] wlbt: filter abnormal ipv4 multicast packet

Change-Id: I50511db5dcec9a9959670eb843ef87c3def99bcc
Signed-off-by: dujeonglee <dujeong.lee@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19423] wlbt : update packet filter for unwanted ARP packet
Yuseok Kim [Tue, 18 Jun 2019 11:00:19 +0000 (20:00 +0900)]
[RAMEN9610-19423] wlbt : update packet filter for unwanted ARP packet

Sometimes, Client send unicast ARP packet with different IP range.
And, Wifi module processes it and wakes up the host.
But, It is weakness from the point of view of power consumption.

Since the desired ARP is offloaded from the FW,
the other ARP packets that are not needed will be dropped.

Change-Id: I34c0c7e29ca5deb1da7da899182e953db6bd7276

5 years ago[RAMEN9610-19422][9630] wlbt: add WLBT drivers 10.1.1.0
Ivan Priest [Tue, 16 Jul 2019 12:54:13 +0000 (13:54 +0100)]
[RAMEN9610-19422][9630] wlbt: add WLBT drivers 10.1.1.0

Add WLBT driver drop for Neus

From tag scsc_release_10.1.1_mx450_p_ww

Change-Id: Ic7fe507ff007a870431f4dcbb6c263e49c334d9c
SCSC-Bug-Id: RELS-3034
Signed-off-by: Ivan Priest <i.priest@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[RAMEN9610-19422][9630] wlbt: prepare for WLBT driver integration
Ivan Priest [Tue, 16 Jul 2019 12:44:03 +0000 (13:44 +0100)]
[RAMEN9610-19422][9630] wlbt: prepare for WLBT driver integration

Replacing drivers with release from SCSC project

Change-Id: Ifb871c6e32744e6016f7a97d08f4150a6452ee2e
SCSC-Bug-Id: RELS-3034
Signed-off-by: Ivan Priest <i.priest@samsung.com>
Signed-off-by: Kim Gunho <gunho.kim@samsung.com>
5 years ago[9610] drivers: gpu: add Bifrost r19p0 in config
Yoojin Park [Thu, 4 Jul 2019 09:11:11 +0000 (18:11 +0900)]
[9610] drivers: gpu: add Bifrost r19p0 in config

Change-Id: I699cb67c76f4b6c24b2995be0ad172b33296fe75
Signed-off-by: Yoojin Park <yoojin1.park@samsung.com>
5 years ago[9610] drivers: gpu: add SECURE_RENDERING codes
Yoojin Park [Mon, 5 Aug 2019 12:45:19 +0000 (21:45 +0900)]
[9610] drivers: gpu: add SECURE_RENDERING codes

Change-Id: I3fbfaf65a4b3ea592efb2dabc5281e61f093343c
Signed-off-by: Yoojin Park <yoojin1.park@samsung.com>
5 years ago[9610] drivers: gpu: remove BTS codes in Bifrost r19p0
Yoojin Park [Thu, 4 Jul 2019 14:18:39 +0000 (23:18 +0900)]
[9610] drivers: gpu: remove BTS codes in Bifrost r19p0

To avoid buiid error

Change-Id: I9f68bcf381b81528341d34e959c2c33d3ba1b50c
Signed-off-by: Yoojin Park <yoojin1.park@samsung.com>
5 years ago[9610] drivers: gpu: adding gpu kernel driver for Bifrost r19p0
Yoojin Park [Thu, 4 Jul 2019 09:45:37 +0000 (18:45 +0900)]
[9610] drivers: gpu: adding gpu kernel driver for Bifrost r19p0

Change-Id: I493e8a9b636db4cfe24a3cd9756937f2250d233f
Signed-off-by: Yoojin Park <yoojin1.park@samsung.com>
5 years ago[COMMON] media: mfc: support H264 5.2 level
Sunyoung Kang [Thu, 8 Aug 2019 10:51:46 +0000 (19:51 +0900)]
[COMMON] media: mfc: support H264 5.2 level

Change-Id: I128a614127cec65d56e8e1edf5aa151846f3c777
Signed-off-by: Sunyoung Kang <sy0816.kang@samsung.com>