MT8163: LineageOS 18.1 changes#16
Draft
akku1139 wants to merge 428 commits into
Draft
Conversation
commit 4b848f2 upstream. There's two references floating around here (for the object reference, not the handle_count reference, that's a different thing): - The temporary reference held by vgem_gem_create, acquired by creating the object and released by calling drm_gem_object_put_unlocked. - The reference held by the object handle, created by drm_gem_handle_create. This one generally outlives the function, except if a 2nd thread races with a GEM_CLOSE ioctl call. So usually everything is correct, except in that race case, where the access to gem_object->size could be looking at freed data already. Which again isn't a real problem (userspace shot its feet off already with the race, we could return garbage), but maybe someone can exploit this as an information leak. Cc: Dan Carpenter <dan.carpenter@oracle.com> Cc: Hillf Danton <hdanton@sina.com> Reported-by: syzbot+0dc4444774d419e916c8@syzkaller.appspotmail.com Cc: stable@vger.kernel.org Cc: Emil Velikov <emil.velikov@collabora.com> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Cc: Sean Paul <seanpaul@chromium.org> Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: Eric Anholt <eric@anholt.net> Cc: Sam Ravnborg <sam@ravnborg.org> Cc: Rob Clark <robdclark@chromium.org> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Change-Id: Ie60eb85499e5fe3cd27118c03829faf9ab67d7bc Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20200202132133.1891846-1-daniel.vetter@ffwll.ch [OP: backport to 4.19: adjusted DRM_DEBUG() -> DRM_DEBUG_DRIVER()] Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> [mkbestas: backport to 4.9] Signed-off-by: Michael Bestas <mkbestas@lineageos.org>
[ Upstream commit 177f25d ] Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it during allocation to make sure that it can't be ever used to leak kernel memory via specially-crafted report. Bug: 380395346 Fixes: 27ce405 ("HID: fix data access in implement()") Reported-by: Benoît Sevens <bsevens@google.com> Acked-by: Benjamin Tissoires <bentiss@kernel.org> Signed-off-by: Jiri Kosina <jkosina@suse.com> Signed-off-by: Sasha Levin <sashal@kernel.org> (cherry picked from commit 9d9f5c7) Signed-off-by: Lee Jones <joneslee@google.com> Change-Id: I31f64f2745347137bbc415eb35b7fab5761867f3
Add a system call to make extended file information available, including
file creation and some attribute flags where available through the
underlying filesystem.
The getattr inode operation is altered to take two additional arguments: a
u32 request_mask and an unsigned int flags that indicate the
synchronisation mode. This change is propagated to the vfs_getattr*()
function.
Functions like vfs_stat() are now inline wrappers around new functions
vfs_statx() and vfs_statx_fd() to reduce stack usage.
========
OVERVIEW
========
The idea was initially proposed as a set of xattrs that could be retrieved
with getxattr(), but the general preference proved to be for a new syscall
with an extended stat structure.
A number of requests were gathered for features to be included. The
following have been included:
(1) Make the fields a consistent size on all arches and make them large.
(2) Spare space, request flags and information flags are provided for
future expansion.
(3) Better support for the y2038 problem [Arnd Bergmann] (tv_sec is an
__s64).
(4) Creation time: The SMB protocol carries the creation time, which could
be exported by Samba, which will in turn help CIFS make use of
FS-Cache as that can be used for coherency data (stx_btime).
This is also specified in NFSv4 as a recommended attribute and could
be exported by NFSD [Steve French].
(5) Lightweight stat: Ask for just those details of interest, and allow a
netfs (such as NFS) to approximate anything not of interest, possibly
without going to the server [Trond Myklebust, Ulrich Drepper, Andreas
Dilger] (AT_STATX_DONT_SYNC).
(6) Heavyweight stat: Force a netfs to go to the server, even if it thinks
its cached attributes are up to date [Trond Myklebust]
(AT_STATX_FORCE_SYNC).
And the following have been left out for future extension:
(7) Data version number: Could be used by userspace NFS servers [Aneesh
Kumar].
Can also be used to modify fill_post_wcc() in NFSD which retrieves
i_version directly, but has just called vfs_getattr(). It could get
it from the kstat struct if it used vfs_xgetattr() instead.
(There's disagreement on the exact semantics of a single field, since
not all filesystems do this the same way).
(8) BSD stat compatibility: Including more fields from the BSD stat such
as creation time (st_btime) and inode generation number (st_gen)
[Jeremy Allison, Bernd Schubert].
(9) Inode generation number: Useful for FUSE and userspace NFS servers
[Bernd Schubert].
(This was asked for but later deemed unnecessary with the
open-by-handle capability available and caused disagreement as to
whether it's a security hole or not).
(10) Extra coherency data may be useful in making backups [Andreas Dilger].
(No particular data were offered, but things like last backup
timestamp, the data version number and the DOS archive bit would come
into this category).
(11) Allow the filesystem to indicate what it can/cannot provide: A
filesystem can now say it doesn't support a standard stat feature if
that isn't available, so if, for instance, inode numbers or UIDs don't
exist or are fabricated locally...
(This requires a separate system call - I have an fsinfo() call idea
for this).
(12) Store a 16-byte volume ID in the superblock that can be returned in
struct xstat [Steve French].
(Deferred to fsinfo).
(13) Include granularity fields in the time data to indicate the
granularity of each of the times (NFSv4 time_delta) [Steve French].
(Deferred to fsinfo).
(14) FS_IOC_GETFLAGS value. These could be translated to BSD's st_flags.
Note that the Linux IOC flags are a mess and filesystems such as Ext4
define flags that aren't in linux/fs.h, so translation in the kernel
may be a necessity (or, possibly, we provide the filesystem type too).
(Some attributes are made available in stx_attributes, but the general
feeling was that the IOC flags were to ext[234]-specific and shouldn't
be exposed through statx this way).
(15) Mask of features available on file (eg: ACLs, seclabel) [Brad Boyer,
Michael Kerrisk].
(Deferred, probably to fsinfo. Finding out if there's an ACL or
seclabal might require extra filesystem operations).
(16) Femtosecond-resolution timestamps [Dave Chinner].
(A __reserved field has been left in the statx_timestamp struct for
this - if there proves to be a need).
(17) A set multiple attributes syscall to go with this.
===============
NEW SYSTEM CALL
===============
The new system call is:
int ret = statx(int dfd,
const char *filename,
unsigned int flags,
unsigned int mask,
struct statx *buffer);
The dfd, filename and flags parameters indicate the file to query, in a
similar way to fstatat(). There is no equivalent of lstat() as that can be
emulated with statx() by passing AT_SYMLINK_NOFOLLOW in flags. There is
also no equivalent of fstat() as that can be emulated by passing a NULL
filename to statx() with the fd of interest in dfd.
Whether or not statx() synchronises the attributes with the backing store
can be controlled by OR'ing a value into the flags argument (this typically
only affects network filesystems):
(1) AT_STATX_SYNC_AS_STAT tells statx() to behave as stat() does in this
respect.
(2) AT_STATX_FORCE_SYNC will require a network filesystem to synchronise
its attributes with the server - which might require data writeback to
occur to get the timestamps correct.
(3) AT_STATX_DONT_SYNC will suppress synchronisation with the server in a
network filesystem. The resulting values should be considered
approximate.
mask is a bitmask indicating the fields in struct statx that are of
interest to the caller. The user should set this to STATX_BASIC_STATS to
get the basic set returned by stat(). It should be noted that asking for
more information may entail extra I/O operations.
buffer points to the destination for the data. This must be 256 bytes in
size.
======================
MAIN ATTRIBUTES RECORD
======================
The following structures are defined in which to return the main attribute
set:
struct statx_timestamp {
__s64 tv_sec;
__s32 tv_nsec;
__s32 __reserved;
};
struct statx {
__u32 stx_mask;
__u32 stx_blksize;
__u64 stx_attributes;
__u32 stx_nlink;
__u32 stx_uid;
__u32 stx_gid;
__u16 stx_mode;
__u16 __spare0[1];
__u64 stx_ino;
__u64 stx_size;
__u64 stx_blocks;
__u64 __spare1[1];
struct statx_timestamp stx_atime;
struct statx_timestamp stx_btime;
struct statx_timestamp stx_ctime;
struct statx_timestamp stx_mtime;
__u32 stx_rdev_major;
__u32 stx_rdev_minor;
__u32 stx_dev_major;
__u32 stx_dev_minor;
__u64 __spare2[14];
};
The defined bits in request_mask and stx_mask are:
STATX_TYPE Want/got stx_mode & S_IFMT
STATX_MODE Want/got stx_mode & ~S_IFMT
STATX_NLINK Want/got stx_nlink
STATX_UID Want/got stx_uid
STATX_GID Want/got stx_gid
STATX_ATIME Want/got stx_atime{,_ns}
STATX_MTIME Want/got stx_mtime{,_ns}
STATX_CTIME Want/got stx_ctime{,_ns}
STATX_INO Want/got stx_ino
STATX_SIZE Want/got stx_size
STATX_BLOCKS Want/got stx_blocks
STATX_BASIC_STATS [The stuff in the normal stat struct]
STATX_BTIME Want/got stx_btime{,_ns}
STATX_ALL [All currently available stuff]
stx_btime is the file creation time, stx_mask is a bitmask indicating the
data provided and __spares*[] are where as-yet undefined fields can be
placed.
Time fields are structures with separate seconds and nanoseconds fields
plus a reserved field in case we want to add even finer resolution. Note
that times will be negative if before 1970; in such a case, the nanosecond
fields will also be negative if not zero.
The bits defined in the stx_attributes field convey information about a
file, how it is accessed, where it is and what it does. The following
attributes map to FS_*_FL flags and are the same numerical value:
STATX_ATTR_COMPRESSED File is compressed by the fs
STATX_ATTR_IMMUTABLE File is marked immutable
STATX_ATTR_APPEND File is append-only
STATX_ATTR_NODUMP File is not to be dumped
STATX_ATTR_ENCRYPTED File requires key to decrypt in fs
Within the kernel, the supported flags are listed by:
KSTAT_ATTR_FS_IOC_FLAGS
[Are any other IOC flags of sufficient general interest to be exposed
through this interface?]
New flags include:
STATX_ATTR_AUTOMOUNT Object is an automount trigger
These are for the use of GUI tools that might want to mark files specially,
depending on what they are.
Fields in struct statx come in a number of classes:
(0) stx_dev_*, stx_blksize.
These are local system information and are always available.
(1) stx_mode, stx_nlinks, stx_uid, stx_gid, stx_[amc]time, stx_ino,
stx_size, stx_blocks.
These will be returned whether the caller asks for them or not. The
corresponding bits in stx_mask will be set to indicate whether they
actually have valid values.
If the caller didn't ask for them, then they may be approximated. For
example, NFS won't waste any time updating them from the server,
unless as a byproduct of updating something requested.
If the values don't actually exist for the underlying object (such as
UID or GID on a DOS file), then the bit won't be set in the stx_mask,
even if the caller asked for the value. In such a case, the returned
value will be a fabrication.
Note that there are instances where the type might not be valid, for
instance Windows reparse points.
(2) stx_rdev_*.
This will be set only if stx_mode indicates we're looking at a
blockdev or a chardev, otherwise will be 0.
(3) stx_btime.
Similar to (1), except this will be set to 0 if it doesn't exist.
=======
TESTING
=======
The following test program can be used to test the statx system call:
samples/statx/test-statx.c
Just compile and run, passing it paths to the files you want to examine.
The file is built automatically if CONFIG_SAMPLES is enabled.
Here's some example output. Firstly, an NFS directory that crosses to
another FSID. Note that the AUTOMOUNT attribute is set because transiting
this directory will cause d_automount to be invoked by the VFS.
[root@andromeda ~]# /tmp/test-statx -A /warthog/data
statx(/warthog/data) = 0
results=7ff
Size: 4096 Blocks: 8 IO Block: 1048576 directory
Device: 00:26 Inode: 1703937 Links: 125
Access: (3777/drwxrwxrwx) Uid: 0 Gid: 4041
Access: 2016-11-24 09:02:12.219699527+0000
Modify: 2016-11-17 10:44:36.225653653+0000
Change: 2016-11-17 10:44:36.225653653+0000
Attributes: 0000000000001000 (-------- -------- -------- -------- -------- -------- ---m---- --------)
Secondly, the result of automounting on that directory.
[root@andromeda ~]# /tmp/test-statx /warthog/data
statx(/warthog/data) = 0
results=7ff
Size: 4096 Blocks: 8 IO Block: 1048576 directory
Device: 00:27 Inode: 2 Links: 125
Access: (3777/drwxrwxrwx) Uid: 0 Gid: 4041
Access: 2016-11-24 09:02:12.219699527+0000
Modify: 2016-11-17 10:44:36.225653653+0000
Change: 2016-11-17 10:44:36.225653653+0000
Change-Id: I345d9bd6cf1947ac3f4dcb3db761088c36028aeb
Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
The new syscall statx is implemented as generic code, so enable it for architectures like openrisc which use the generic syscall table. Fixes: a528d35 ("statx: Add a system call to make enhanced file info available") Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Al Viro <viro@zeniv.linux.org.uk> Cc: David Howells <dhowells@redhat.com> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Will Deacon <will.deacon@arm.com> Cc: linux-arm-kernel@lists.infradead.org Change-Id: Ia35ef2d98bbfa602f1c8aa5996b5ce88c2740271 Signed-off-by: Stafford Horne <shorne@gmail.com> Signed-off-by: Will Deacon <will.deacon@arm.com>
Hook up three pkey syscalls (which we don't implement) and the new statx syscall, as has been done for arch/arm/. Change-Id: Icb4ab7840a6ac2ad8cf2f43bbbaab741e97cfc39 Signed-off-by: Will Deacon <will.deacon@arm.com>
Change-Id: I3cc50b099cb593e58d596ed65708c6e3f6983aff Signed-off-by: bengris32 <bengris32@protonmail.ch>
The arm64 uapi sigcontext.h can be included by 32-bit userspace modules. Since arm and arm64 sigcontext definition are not compatible, add arm sigcontext definition to arm64 sigcontext.h. Change-Id: I94109b094f6c8376fdaeb2822d7b26d18ddfb2bc Signed-off-by: David Ng <dave@codeaurora.org> Signed-off-by: Ameya Thakur <ameyat@codeaurora.org>
[Detail] 1. add Errata 814220/824069/855873 for arm 2. add Errata 855873 for arm64 MTK-Commit-Id: e6db68d967adca4887610aa9dcf72ed985265b79 Change-Id: I8064281a9c398cf8cf413c978652c881562039a6 CR-Id: ALPS03683436 Feature: Platform Signed-off-by: Shun-Chih Yu <shun-chih.yu@mediatek.com>
[Detail] add mblock_v2 structure and define MTK-Commit-Id: 438b4d5bc25acd4db5cbfc8c203aa9870bd2342a Change-Id: I34046d10704dd352e4c5491de371e01005232ed1 Signed-off-by: Johnson Lin <johnson.lin@mediatek.com> CR-Id: ALPS03635841 Feature: mblock
[Detail] Decrease L1_CACHE_SHIFT to meet MTK h/w design MTK-Commit-Id: 0bdd50c19cb532b059590ee02b1fa64cb5f37755 Change-Id: I0b2ca700433225da655a84609ab8f68c91e53578 CR-Id: ALPS03824358 Feature: n/a Signed-off-by: Andy <chia-hao.hsu@mediatek.com> (cherry picked from commit 771d0509efcc2b760360b59060aa34a584eb0a11)
[Detail]
For arm64:
Imporve backward-compatibility for thrid-party applications
by patching the "Hardware", "Processor", and "model name"
information in /proc/cpuinfo.
For arm:
Imporve backward-compatibility for thrid-party applications
by patching the "Processor" information in /proc/cpuinfo.
Further, for the machines that support device tree, the hardware
machine name should be retrieved from device tree instead of mdesc.
This change also add a message to notify that some process reads
/proc/cpuinfo as a hint for debugging.
MTK-Commit-Id: c8b16cbe979579f7342df1edb2c638910b6dfc2f
[bengris32: Remove useless pr_debug("Dump cpuinfo\n"); message]
Change-Id: Ia3f7c5f8e20bd551262d7e876d300497b67d1f22
CR-Id: ALPS03683436
Feature: Others
Signed-off-by: Shun-Chih Yu <shun-chih.yu@mediatek.com>
use mt-boot method to boot up multiple cpus Dependence List: DCM API [Roger Lu] - Use DCM_READY define SPM API [YT Lee] - Use SPM_READY define Test: [0.150620] Brought up 4 CPUs MTK-Commit-Id: 9f906cc8d9fdb0264cd92536d8f90e435962a9f7 Change-Id: I0ef13ae37e3593bdee1cc0fed0e10cf567949cec Signed-off-by: Louis Yu <louis.yu@mediatek.com> CR-Id: ALPS03527364 Feature: CPU Hotplug
[Detail] For soc timer based broadcasting and irq affinity feature is enabled, if the dying cpu is exactly the target of IRQ by SoC timer, we shall change the irq affinity to another online cpu to make sure irq will be serviced. MTK-Commit-Id: f4f8cc2f62dffaf7636bdb9abcfaa6e76e44233e Change-Id: I130a7c398d5d67e0e8363f4cd4bb0c0a80cced55 Signed-off-by: Stanley Chu <stanley.chu@mediatek.com> CR-Id: ALPS03460960 Feature: Others
[Detail] In hotplug_cpu__broadcast_tick_pull(), ie., cpu hot plug off case, soc-timer based broadcasting event timer may be set KTIME_MAX as its next event time. Scenario example: in tick_handle_oneshot_broadcast(), if all cpus next events are expired, bc->next_event will be set as KTIME_MAX, and meanwhile cpu hot plug-off event happens. This shall have no critical issue because bc timer will be set as normal next event later. However we fix it anyway to avoid any future potential issues. [Solution] In this case, apply 1 dummy tick as next_event for clockevents_program_event to re-arm soc timer anyway. MTK-Commit-Id: 106449eeba37ff7bfae54bab1aa63ea55cb45ef5 Change-Id: I94b32c0879216b6796ce20b89a85c305436e1567 CR-Id: ALPS03460960 Feature: All Core Always Online (ACAO-MCU Deep Idle) Signed-off-by: hongxu.zhao <hongxu.zhao@mediatek.com>
[Detail] Do change bctimers irq affinity only and nothing else if bctimer has no next_event in hotplug_cpu__broadcast_tick_pull(). MTK-Commit-Id: 89265ade51f1eb9c4497d84d6a639c87e3f5c1e1 Change-Id: I9ff293c8c3a47278a7b09560c105eca24f55fb37 CR-Id: ALPS03730049 Feature: MTBF(*) Signed-off-by: hongxu.zhao <hongxu.zhao@mediatek.com>
[Detail] MTK PATCH to fix ARM v8.0 live spinlock issue. Flush lock value here if timer cancelling or deletion is not finished. In this case, Other CPU may need to get cpu_base spinlock to update running timer information. Flush lock value specifically after unlocking to promise that other CPU can see correct lock value to avoid starvation or unfair spinlock competition. MTK-Commit-Id: 7dca09116e6932669a94eb50a27f0d0fe3a2b360 Change-Id: I3573eb9668d928ce72966b12f81cad86827426e1 Signed-off-by: Jane Zhang <Jane.Zhang@mediatek.com> CR-Id: ALPS03753015 Feature: Others (cherry picked from commit fd02c0503e947124d62662d5875132d2257ba7a4)
[Detail] Add PM QoS Class and add owner concept 1. CPU Memeory Bandwidth 2. GPU Memeory Bandwidth 3. MM Memeory Bandwidth 4. OTHER Memeory Bandwidth 5. DDR OPP 6. VCORE OPP 7. VCORE DVFS FORCE OPP MTK-Commit-Id: 7d3d7d9dff0e7cfdf6a6e9f579d12c2d54836231 Change-Id: Ifb8b9cfa04cff701341066ee8248aaeed9bda20e Signed-off-by: Cheng-En Chung <cheng-en.chung@mediatek.com> CR-Id: ALPS03678607 Feature: VCORE DVFS
[Detail] 1. Add mediatek enhancement to pstore 2. Enable pstore MTK-Commit-Id: b38d85acc28c878be3fa3395a03148afb6b69a78 Change-Id: I252a01848af09acd229b799d5d70cce52eb4abe4 Signed-off-by: Ji Zhang <ji.zhang@mediatek.com> CR-Id: ALPS03513313 Feature: Others
[Detail] Currently only DMESG and CONSOLE record types are protected, and it isnt obvious that they are using a capability check. Instead switch to explicit root directory mode of 0750 to keep files private by default. This will allow the removal of the capability check, which was non-obvious and forces a process to have possibly too much privilege when simple post-boot chgrp for readers would be possible without it. Signed-off-by: Kees Cook <keescook@chromium.org> Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com> (cherry picked from commit d7caa33) MTK-Commit-Id: 313752f1d49e22eef8322a6ab62f79daa7789f0b Change-Id: Ie53c8aeb26d5d508fdd0811e2c11ff7bcc436b50 Signed-off-by: Ji Zhang <ji.zhang@mediatek.com> CR-Id: ALPS03786642 Feature: CTS(*) (cherry picked from commit 889fbf7a0ae30016b117f7fa51f18830b8b5a567)
…umps" [Detail] This reverts commit 68c4a4f, with various conflict clean-ups. The capability check required too much privilege compared to simple DAC controls. A system builder was forced to have crash handler processes run with CAP_SYSLOG which would give it the ability to read (and wipe) the _current_ dmesg, which is much more access than being given access only to the historical log stored in pstorefs. With the prior commit to make the root directory 0750, the files are protected by default but a system builder can now opt to give access to a specific group (via chgrp on the pstorefs root directory) without being forced to also give away CAP_SYSLOG. Suggested-by: Nick Kralevich <nnk@google.com> Signed-off-by: Kees Cook <keescook@chromium.org> Reviewed-by: Petr Mladek <pmladek@suse.cz> Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com> (cherry picked from commit c71b02e) MTK-Commit-Id: 37e8f48457d9362602c49dbabb02e4d06bdcf953 Change-Id: I0d147ebae2bfbd1062b9f63006d2129fcfe3eb76 Signed-off-by: Ji Zhang <ji.zhang@mediatek.com> CR-Id: ALPS03786642 Feature: CTS(*) (cherry picked from commit e19d9ffa683d6bd29b1287c6514cbfa355ac60ce)
fix build errors when KSAN kernel config is enabled MTK-Commit-Id: 4e159b36dbc96771fede9043af7d0f40d394aa81 Change-Id: Iee28dbd79b010573d4d0caeafafc3b1768d94330 Signed-off-by: Xinghua Yang <xinghua.yang@mediatek.com> CR-Id: ALPS04111158 Feature: Android Exception Engine(AEE) (cherry-pick from 99532aaff7f8e40a3066192e67d8178747ce1e37)
Change-Id: Iedec0b775eb414e905f986f4a01e2cd6865d1150 Signed-off-by: bengris32 <bengris32@protonmail.ch>
…g a CPU CPU hotplug operations take place in preemptible context. This leaves the hotplugging thread at the mercy of overall system load and CPU availability. If the hotplugging thread does not get an opportunity to execute after it has already begun a hotplug operation, CPUs can end up being stuck in a quasi online state. In the worst case a CPU can be stuck in a state where the migration thread is parked while another task is executing and changing affinity in a loop. This combination can result in unbounded execution time for the running task until the hotplugging thread gets the chance to run to complete the hotplug operation. Fix the said problem by ensuring that hotplug can only occur from threads belonging to the RT sched class. This allows the hotplugging thread priority on the CPU no matter what the system load or the number of available CPUs are. If a SCHED_NORMAL task attempts to hotplug a CPU, we temporarily elevate it's scheduling policy to RT. Furthermore, we disallow hotplugging operations to begin if the calling task belongs to the idle and deadline classes or those that use the SCHED_BATCH policy. Bug: 169238689 Change-Id: Idbb1384626e6ddff46c0d2ce752eee68396c78af Signed-off-by: Syed Rameez Mustafa <rameezmustafa@codeaurora.org> [psodagud@codeaurora.org: Fixed compilation issues] Signed-off-by: Prasad Sodagudi <psodagud@codeaurora.org>
Change-Id: If55755c5df8a6760b87158cb19c16a093c864f1f Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: I2bf2e2f924a88deecd4287ce171de75381efb008 Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: I592d972a095adecdcc70effababa1b5fc5f6e36e Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: Iddcd9fd775ca45ade27c6fe6438a57ddb366c4e4 Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: Ibaa04fcb25a91b9e0fecacc737c65f52a65f01bf Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: Icaae319af6bb8f283dba92fd8790d265b70b1baa Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: I55cbc277b37ead6945d359af916168e4fd27cb7d Signed-off-by: Joel Stein <js@funkturm.net>
Change-Id: Ib86ea3661dce37ff939cf459971c046fa84ad2fa Signed-off-by: Jack Matthews <jack@jackmatthe.ws>
Change-Id: I7653d7c108f4a1d8271b3ac16964986feaf62ffc Signed-off-by: Sultan Alsawaf <sultanxda@gmail.com>
Change-Id: I37eb9a340872753aa6c80938e80cbc62a9b62c32 Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: I9afa66417c0c8aca9e9fc21427a34c6521a098ad Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: I482ad8401247279effcd69d523d64b95a464aa62 Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: Ic4db1314a4cca456ad37a5a5e6ced6ebd328e6e6 Signed-off-by: bengris32 <bengris32@protonmail.ch>
Replace previously checked debugging globals with macros so that the alternative codepaths are compiled out. Change-Id: I175d22d7eeaf72f618455a7e3463bb6ec76d6532 Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: Id33017c4be7a0e6bcbc412ab429ce5f902bbcf6d Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: Ie78454af84054f53a674b1d31551111bade3d940 Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: I7cb7648daea1619f930725627ee1fc0bd7a2e971 Signed-off-by: bengris32 <bengris32@protonmail.ch>
This check seems rather redundant, touch boost doesn't behave any differently with it removed (since all drivers report BTN_TOUCH events anyway), apart from one major difference being touch boost no longer gets stuck being active on crown. Change-Id: I5a81eb34eae9e9e8ac9eedd0c0a57d5f01c65d1d Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: Id5d0b5c9107ef5150cc5430d57555f1655e8a8cd Signed-off-by: bengris32 <bengris32@protonmail.ch>
From "Echo_Show_5_2nd_Gen_src-6.5.7.1-20251112.tar.bz2"
Change-Id: Ia9f6ee8e0720f9b7428e249018d707416decae57
Change-Id: I35143c5fbf87dbbbb66e1a132758fa943ab1511a
Change-Id: I6fbe21b280a459893c649a8abe5d2d39f97cc3ff Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: I5ef24a1177ca62bcddec833a453df0988c5731b0
Change-Id: If2dd4d5e8c98fb3c7611e78c48202c6106222d87
Change-Id: I03d44fa184b6b0acfa9635fd27101053857a212d
Add optional 'disable_reset' device tree property to skip the GPIO reset sequence during probe. On some hardware configurations, the codec reset line is controlled externally (FPGA/SPI) instead of being directly connected to the SoC. When disable_reset is set, the driver skips GPIO acquisition and reset operations, letting external hardware manage the codec reset. Change-Id: Id40a871407f66678a8337b80acf086f923b162f6
Change-Id: Id70b54ae0458d7e0703183b189de1eec976b06d4
Change-Id: Id3992c7015b78c649486c938c99e362d4731221c
get_alsps_dts_func() wasn't reading is_supported_two_point_als_cali, black_als_range, or white_als_range, even though jsa1214 uses all three. The properties are set in DTS but the parser silently ignored them. On devices whose factory alscal stores packed two-point data (als_cal > 65535, cali_high in low 16 bits, cali_low in high 16), this meant jsa1214 fell back to CALI_DEFAULT_DATA (2) and lux came out ~275x too high. cronos was reporting 21400 lux in an 80 lux room because of it. Change-Id: If7ce727a32bd5cd00cad61fdeefc9a5dc5b2349c
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.