Changes in Kconfig

a4a508df2aa34f8650afde54ea804321c618f45f - Merge tag 'v6.18' into next

Sat, 13 Dec 2025 09:18:20 +0000

Merge tag 'v6.18' into nextSync up with the mainline to bring in the latest APIs. List of files: /linux/drivers/android/Kconfig

7362b5b493102c6b71827c2da22117b475528f6d - Merge branch 'for-6.19/nintendo' into for-linus

Tue, 02 Dec 2025 13:46:11 +0000

Merge branch 'for-6.19/nintendo' into for-linus- switch to WQ_PERCPU workaueues (Marco Crivellari)- reduce potential initialization blocking time of hid-nintendo (Willy Huang) List of files: /linux/drivers/android/Kconfig

2ace52718376fdb56aca863da2eebe70d7e2ddb1 - Merge branch 'objtool/core'

Fri, 21 Nov 2025 10:21:20 +0000

Merge branch 'objtool/core'Bring in the UDB and objtool data annotations to avoid conflicts while further extending the bug exceptions.Signed-off-by: Peter Zijlstra List of files: /linux/drivers/android/Kconfig

f39b6c468c52745dbca9a842d91c8373fda208ab - Merge tag 'v6.18-rc6' into for-linus

Tue, 18 Nov 2025 07:16:55 +0000

Merge tag 'v6.18-rc6' into for-linusSync up with the mainline to bring in definition ofINPUT_PROP_HAPTIC_TOUCHPAD. List of files: /linux/drivers/android/Kconfig

cb9f145f638d7afa633632a9290d6ad06caeb8ee - Merge remote-tracking branch 'drm/drm-next' into msm-next-robclark

Sat, 01 Nov 2025 12:47:30 +0000

Merge remote-tracking branch 'drm/drm-next' into msm-next-robclarkBack-merge drm-next to get caught up.Signed-off-by: Rob Clark List of files: /linux/drivers/android/Kconfig

ec2e0fb07d789976c601bec19ecced7a501c3705 - Merge tag 'asoc-fix-v6.18-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus

Thu, 16 Oct 2025 18:14:24 +0000

Merge tag 'asoc-fix-v6.18-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linusASoC: Fixes for v6.18A moderately large collection of driver specific fixes, plus a few newquirks and device IDs. The NAU8821 changes are a little large but morein mechanical ways than in ways that are complex. List of files: /linux/drivers/android/Kconfig

82ee50252dc891e3f3b32d923bb4f656d300b772 - Merge drm/drm-next into drm-xe-next

Tue, 14 Oct 2025 09:31:49 +0000

Merge drm/drm-next into drm-xe-nextBackmerging to bring in 6.18-rc1.Signed-off-by: Thomas Hellström List of files: /linux/drivers/android/Kconfig

48a710760e10a4f36e11233a21860796ba204b1e - Merge drm/drm-fixes into drm-misc-fixes

Tue, 14 Oct 2025 08:59:58 +0000

Merge drm/drm-fixes into drm-misc-fixesUpdating drm-misc-fixes to the state of v6.18-rc1.Signed-off-by: Thomas Zimmermann List of files: /linux/drivers/android/Kconfig

2acee98fcc61052d63fab4539fcb6ee677555645 - Merge drm/drm-next into drm-intel-next

Tue, 14 Oct 2025 07:37:11 +0000

Merge drm/drm-next into drm-intel-nextSync to v6.18-rc1.Signed-off-by: Jani Nikula List of files: /linux/drivers/android/Kconfig

4f38da1f027ea2c9f01bb71daa7a299c191b6940 - spi: Merge up v6.18-rc1

Mon, 13 Oct 2025 12:32:13 +0000

spi: Merge up v6.18-rc1Ensure my CI has a sensible baseline. List of files: /linux/drivers/android/Kconfig

9b966ae42235a88eaea714be09ff3d698535bdfe - Merge drm/drm-next into drm-misc-next

Mon, 13 Oct 2025 07:19:19 +0000

Merge drm/drm-next into drm-misc-nextUpdating drm-misc-next to the state of v6.18-rc1.Signed-off-by: Thomas Zimmermann List of files: /linux/drivers/android/Kconfig

39e9d5f63075f4d54e3b59b8238478c32af92755 - Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf before 6.18-rc1

Sun, 12 Oct 2025 01:27:47 +0000

Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf before 6.18-rc1Cross-merge BPF and other fixes after downstream PR.No conflicts.Signed-off-by: Alexei Starovoitov List of files: /linux/drivers/android/Kconfig

8b87f67b4c87452e21721887fa8dec1f4c6b2b7c - Merge branch 'next' into for-linus

Wed, 08 Oct 2025 04:53:13 +0000

Merge branch 'next' into for-linusPrepare input updates for 6.18 merge window. List of files: /linux/drivers/android/Kconfig

6093a688a07da07808f0122f9aa2a3eed250d853 - Merge tag 'char-misc-6.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc

Sat, 04 Oct 2025 23:26:32 +0000

Merge tag 'char-misc-6.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-miscPull Char/Misc/IIO/Binder updates from Greg KH: "Here is the big set of char/misc/iio and other driver subsystem changes for 6.18-rc1. Loads of different stuff in here, it was a busy development cycle in lots of different subsystems, with over 27k new lines added to the tree. Included in here are: - IIO updates including new drivers, reworking of existing apis, and other goodness in the sensor subsystems - MEI driver updates and additions - NVMEM driver updates - slimbus removal for an unused driver and some other minor updates - coresight driver updates and additions - MHI driver updates - comedi driver updates and fixes - extcon driver updates - interconnect driver additions - eeprom driver updates and fixes - minor UIO driver updates - tiny W1 driver updates But the majority of new code is in the rust bindings and additions, which includes: - misc driver rust binding updates for read/write support, we can now write "normal" misc drivers in rust fully, and the sample driver shows how this can be done. - Initial framework for USB driver rust bindings, which are disabled for now in the build, due to limited support, but coming in through this tree due to dependencies on other rust binding changes that were in here. I'll be enabling these back on in the build in the usb.git tree after -rc1 is out so that developers can continue to work on these in linux-next over the next development cycle. - Android Binder driver implemented in Rust. This is the big one, and was driving a huge majority of the rust binding work over the past years. Right now there are two binder drivers in the kernel, selected only at build time as to which one to use as binder wants to be included in the system at boot time. The binder C maintainers all agreed on this, as eventually, they want the C code to be removed from the tree, but it will take a few releases to get there while both are maintained to ensure that the rust implementation is fully stable and compliant with the existing userspace apis. All of these have been in linux-next for a while"* tag 'char-misc-6.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc: (320 commits) rust: usb: keep usb::Device private for now rust: usb: don't retain device context for the interface parent USB: disable rust bindings from the build for now samples: rust: add a USB driver sample rust: usb: add basic USB abstractions coresight: Add label sysfs node support dt-bindings: arm: Add label in the coresight components coresight: tnoc: add new AMBA ID to support Trace Noc V2 coresight: Fix incorrect handling for return value of devm_kzalloc coresight: tpda: fix the logic to setup the element size coresight: trbe: Return NULL pointer for allocation failures coresight: Refactor runtime PM coresight: Make clock sequence consistent coresight: Refactor driver data allocation coresight: Consolidate clock enabling coresight: Avoid enable programming clock duplicately coresight: Appropriately disable trace bus clocks coresight: Appropriately disable programming clocks coresight: etm4x: Support atclk coresight: catu: Support atclk ... List of files: /linux/drivers/android/Kconfig

eafedbc7c050c44744fbdf80bdf3315e860b7513 - rust_binder: add Rust Binder driver

Fri, 19 Sep 2025 06:42:07 +0000

rust_binder: add Rust Binder driverWe're generally not proponents of rewrites (nasty uncomfortable thingsthat make you late for dinner!). So why rewrite Binder?Binder has been evolving over the past 15+ years to meet the evolvingneeds of Android. Its responsibilities, expectations, and complexityhave grown considerably during that time. While we expect Binder tocontinue to evolve along with Android, there are a number of factorsthat currently constrain our ability to develop/maintain it. Brieflythose are:1. Complexity: Binder is at the intersection of everything in Android and fulfills many responsibilities beyond IPC. It has become many things to many people, and due to its many features and their interactions with each other, its complexity is quite high. In just 6kLOC it must deliver transactions to the right threads. It must correctly parse and translate the contents of transactions, which can contain several objects of different types (e.g., pointers, fds) that can interact with each other. It controls the size of thread pools in userspace, and ensures that transactions are assigned to threads in ways that avoid deadlocks where the threadpool has run out of threads. It must track refcounts of objects that are shared by several processes by forwarding refcount changes between the processes correctly. It must handle numerous error scenarios and it combines/nests 13 different locks, 7 reference counters, and atomic variables. Finally, It must do all of this as fast and efficiently as possible. Minor performance regressions can cause a noticeably degraded user experience.2. Things to improve: Thousand-line functions [1], error-prone error handling [2], and confusing structure can occur as a code base grows organically. After more than a decade of development, this codebase could use an overhaul.[1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/android/binder.c?h=v6.5#n2896[2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/android/binder.c?h=v6.5#n36583. Security critical: Binder is a critical part of Android's sandboxing strategy. Even Android's most de-privileged sandboxes (e.g. the Chrome renderer, or SW Codec) have direct access to Binder. More than just about any other component, it's important that Binder provide robust security, and itself be robust against security vulnerabilities.It's #1 (high complexity) that has made continuing to evolve Binder andresolving #2 (tech debt) exceptionally difficult without causing #3(security issues). For Binder to continue to meet Android's needs, weneed better ways to manage (and reduce!) complexity without increasingthe risk.The biggest change is obviously the choice of programming language. Wedecided to use Rust because it directly addresses a number of thechallenges within Binder that we have faced during the last years. Itprevents mistakes with ref counting, locking, bounds checking, and alsodoes a lot to reduce the complexity of error handling. Additionally,we've been able to use the more expressive type system to encode theownership semantics of the various structs and pointers, which takes thecomplexity of managing object lifetimes out of the hands of theprogrammer, reducing the risk of use-after-frees and similar problems.Rust has many different pointer types that it uses to encode ownershipsemantics into the type system, and this is probably one of the mostimportant aspects of how it helps in Binder. The Binder driver has a lotof different objects that have complex ownership semantics; somepointers own a refcount, some pointers have exclusive ownership, andsome pointers just reference the object and it is kept alive in someother manner. With Rust, we can use a different pointer type for eachkind of pointer, which enables the compiler to enforce that theownership semantics are implemented correctly.Another useful feature is Rust's error handling. Rust allows for moresimplified error handling with features such as destructors, and you getcompilation failures if errors are not properly handled. This means thateven though Rust requires you to spend more lines of code than C onthings such as writing down invariants that are left implicit in C, theRust driver is still slightly smaller than C binder: Rust is 5.5kLOC andC is 5.8kLOC. (These numbers are excluding blank lines, comments,binderfs, and any debugging facilities in C that are not yet implementedin the Rust driver. The numbers include abstractions in rust/kernel/that are unlikely to be used by other drivers than Binder.)Although this rewrite completely rethinks how the code is structured andhow assumptions are enforced, we do not fundamentally change *how* thedriver does the things it does. A lot of careful thought has gone intothe existing design. The rewrite is aimed rather at improving codehealth, structure, readability, robustness, security, maintainabilityand extensibility. We also include more inline documentation, andimprove how assumptions in the code are enforced. Furthermore, allunsafe code is annotated with a SAFETY comment that explains why it iscorrect.We have left the binderfs filesystem component in C. Rewriting it inRust would be a large amount of work and requires a lot of bindings tothe file system interfaces. Binderfs has not historically had the samechallenges with security and complexity, so rewriting binderfs seems tohave lower value than the rest of Binder.Correctness and feature parity------------------------------Rust binder passes all tests that validate the correctness of Binder inthe Android Open Source Project. We can boot a device, and run a varietyof apps and functionality without issues. We have performed this both onthe Cuttlefish Android emulator device, and on a Pixel 6 Pro.As for feature parity, Rust binder currently implements all featuresthat C binder supports, with the exception of some debugging facilities.The missing debugging facilities will be added before we submit the Rustimplementation upstream.Tracepoints-----------I did not include all of the tracepoints as I felt that the mechansimfor making C access fields of Rust structs should be discussed on listseparately. I also did not include the support for building Rust Binderas a module since that requires exporting a bunch of additional symbolson the C side.Original RFC Link with old benchmark numbers: https://lore.kernel.org/r/20231101-rust-binder-v1-0-08ba9197f637@google.comCo-developed-by: Wedson Almeida Filho Signed-off-by: Wedson Almeida Filho Co-developed-by: Matt Gilbride Signed-off-by: Matt Gilbride Acked-by: Carlos Llamas Acked-by: Paul Moore Signed-off-by: Alice Ryhl Link: https://lore.kernel.org/r/20250919-rust-binder-v2-1-a384b09f28dd@google.comSigned-off-by: Greg Kroah-Hartman List of files: /linux/drivers/android/Kconfig

f088104d837a991c65e51fa30bb4196169b3244d - Merge drm/drm-next into drm-intel-gt-next

Tue, 16 Sep 2025 10:53:20 +0000

Merge drm/drm-next into drm-intel-gt-nextBackmerge in order to get the commit: 048832a3f400 ("drm/i915: Refactor shmem_pwrite() to use kiocb and write_iter")To drm-intel-gt-next as there are followup fixes to be applied.Signed-off-by: Joonas Lahtinen List of files: /linux/drivers/android/Kconfig

b4d90dbc4c1bc4bd3eb2d2989330af0eb95c98e8 - Merge drm/drm-next into drm-misc-next-fixes

Mon, 15 Sep 2025 08:23:28 +0000

Merge drm/drm-next into drm-misc-next-fixesBackmerging to drm-misc-next-fixes to get features and fixes fromv6.17-rc6.Signed-off-by: Thomas Zimmermann List of files: /linux/drivers/android/Kconfig

702fdf3513b045f596f836d9a4b8672c76f11834 - Merge drm/drm-next into drm-intel-next

Wed, 10 Sep 2025 12:01:42 +0000

Merge drm/drm-next into drm-intel-nextCatching up with some display dependencies.Signed-off-by: Rodrigo Vivi List of files: /linux/drivers/android/Kconfig

4b051897df2375414587a245ecb9bb1a4d26b3b8 - Merge tag 'v6.17-rc2' into HEAD

Thu, 21 Aug 2025 18:46:49 +0000

Merge tag 'v6.17-rc2' into HEADSync up with mainline to bring in changes to include/linux/sprintf.h List of files: /linux/drivers/android/Kconfig

63740349eba78f242bcbf60d5244d7f2b2600853 - binder: introduce transaction reports via netlink

Sun, 27 Jul 2025 18:29:06 +0000

binder: introduce transaction reports via netlinkIntroduce a generic netlink multicast event to report binder transactionfailures to userspace. This allows subscribers to monitor these eventsand take appropriate actions, such as stopping a misbehaving applicationthat is spamming a service with huge amount of transactions.The multicast event contains full details of the failed transactions,including the sender/target PIDs, payload size and specific error code.This interface is defined using a YAML spec, from which the UAPI andkernel headers and source are auto-generated.Signed-off-by: Li Li Signed-off-by: Carlos Llamas Link: https://lore.kernel.org/r/20250727182932.2499194-4-cmllamas@google.comSigned-off-by: Greg Kroah-Hartman List of files: /linux/drivers/android/Kconfig