futex: mark futex_detect_cmpxchg() as 'noinline'
Subsystems (2)
PATCH 1/2 futex: mark futex_detect_cmpxchg() as 'noinline'
On 32-bit ARM, I got a link failure in futex_init() when building with clang in some random configurations:
kernel/futex.o:(.text.fixup+0x5c): relocation truncated to fit: R_ARM_JUMP24 against `.init.text'
As far as I can tell, the problem is that a branch is over 16MB apart in those configurations, but only if it branches back to the init text.
Marking the futex_detect_cmpxchg() function as noinline and not __init avoids the problem for me.
--- kernel/futex.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/futex.c +1 -1
@@ -3849,7 +3849,7 @@ SYSCALL_DEFINE6(futex_time32, u32 __user *, uaddr, int, op, u32, val, }#endif /* CONFIG_COMPAT_32BIT_TIME */ -static void __init futex_detect_cmpxchg (void ) +static noinline void futex_detect_cmpxchg(void) {#ifndef CONFIG_HAVE_FUTEX_CMPXCHG u32 curval;
Signature · 1 line
2.20.0
PATCH 2/2 ARM: futex: make futex_detect_cmpxchg more reliable
Passing registers containing zero as both the address (NULL pointer) and data into cmpxchg_futex_value_locked() leads clang to assign the same register for both inputs on ARM, which triggers a warning explaining that this instruction has unpredictable behavior on ARMv5.
/tmp/futex-7e740e.s: Assembler messages:/tmp/futex-7e740e.s:12713: Warning: source register same as write-back base
This patch was suggested by Mikael Pettersson back in 2011 (!) with gcc-4.4, as Mikael wrote:
"One way of fixing this is to make uaddr an input/output register, since "that prevents it from overlapping any other input or output."
but then withdrawn as the warning was determined to be harmless, and it apparently never showed up again with later gcc versions.
Now the same problem is back when compiling with clang, and we are trying to get clang to build the kernel without warnings, as gcc normally does.
--- arch/arm/include/asm/futex.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
arch/arm/include/asm/futex.h +5 -5
@@ -110,13 +110,13 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr,preempt_disable (); __ua_flags =uaccess_save_and_enable (); __asm__ __volatile__("@futex_atomic_cmpxchg_inatomic\n" - "1: " TUSER(ldr) " %1, [%4]\n" -" teq %1, %2\n" + "1: " TUSER(ldr) " %1, [%2]\n" +" teq %1, %3\n" " it eq @ explicit IT needed for the 2b label\n" - "2: " TUSER(streq) " %3, [%4]\n" + "2: " TUSER(streq) " %4, [%2]\n" __futex_atomic_ex_table("%5" ) - : "+r" (ret), "=&r" (val) - : "r" (oldval), "r" (newval), "r" (uaddr), "Ir" (-EFAULT) + : "+&r" (ret), "=&r" (val), "+&r" (uaddr) + : "r" (oldval), "r" (newval), "Ir" (-EFAULT) : "cc", "memory"); uaccess_restore(__ua_flags);
Signature · 7 lines
2.20.0 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 41 lines · Arnd Bergmann
Passing registers containing zero as both the address (NULL pointer) and data into
cmpxchg_futex_value_locked()leads clang to assign the same register for both inputs on ARM, which triggers a warning explaining that this instruction has unpredictable behavior on ARMv5.
/tmp/futex-7e740e.s: Assembler messages:/tmp/futex-7e740e.s:12713: Warning: source register same as write-back baseThis patch was suggested by Mikael Pettersson back in 2011 (!) with gcc-4.4, as Mikael wrote:
"One way of fixing this is to make uaddr an input/output register, since "that prevents it from overlapping any other input or output."but then withdrawn as the warning was determined to be harmless, and it apparently never showed up again with later gcc versions.
Now the same problem is back when compiling with clang, and we are trying to get clang to build the kernel without warnings, as gcc normally does.
Cc Mikael Pettersson <[email protected]>Cc Mikael Pettersson <[email protected]>Cc Dave Martin <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/include/asm/futex.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)arch/arm/include/asm/futex.h +2
-2@@ -110,13 +110,13 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr,preempt_disable (); __ua_flags =uaccess_save_and_enable (); __asm__ __volatile__("@futex_atomic_cmpxchg_inatomic\n" - "1: " TUSER(ldr) " %1, [%4]\n" -" teq %1, %2\n" + "1: " TUSER(ldr) " %1, [%2]\n" +" teq %1, %3\n"
arch/arm/include/asm/futex.h futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr, · line 121
Quoted 10 lines
arch/arm/include/asm/futex.h +3
-3" it eq @ explicit IT needed for the 2b label\n" - "2: " TUSER(streq) " %3, [%4]\n" + "2: " TUSER(streq) " %4, [%2]\n" __futex_atomic_ex_table("%5" ) - : "+r" (ret), "=&r" (val) - : "r" (oldval), "r" (newval), "r" (uaddr), "Ir" (-EFAULT) + : "+&r" (ret), "=&r" (val), "+&r" (uaddr) + : "r" (oldval), "r" (newval), "Ir" (-EFAULT) : "cc", "memory"); uaccess_restore(__ua_flags);
Underspecification of constraints to extended inline assembly is a common issue exposed by other compilers (and possibly but in-effect infrequently compiler upgrades).
So the reordering of the constraints means the in the assembly (notes for other reviewers):
%2 -> %3
%3 -> %4
%4 -> %2
Yep, looks good to me, thanks for finding this old patch and resending, Arnd!
I think it would be good to further credit Mikael with reported by and suggested by tags, but not sure which email address is preferred?
Signature · 2 lines
Thanks, ~Nick Desaulniers
Russell King - ARM Linux admin
maintainerRe: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 54 lines · Nick Desaulniers
Quoted 41 lines · Arnd Bergmann
Passing registers containing zero as both the address (NULL pointer) and data into
cmpxchg_futex_value_locked()leads clang to assign the same register for both inputs on ARM, which triggers a warning explaining that this instruction has unpredictable behavior on ARMv5.
/tmp/futex-7e740e.s: Assembler messages:/tmp/futex-7e740e.s:12713: Warning: source register same as write-back baseThis patch was suggested by Mikael Pettersson back in 2011 (!) with gcc-4.4, as Mikael wrote:
"One way of fixing this is to make uaddr an input/output register, since "that prevents it from overlapping any other input or output."but then withdrawn as the warning was determined to be harmless, and it apparently never showed up again with later gcc versions.
Now the same problem is back when compiling with clang, and we are trying to get clang to build the kernel without warnings, as gcc normally does.
Cc Mikael Pettersson <[email protected]>Cc Mikael Pettersson <[email protected]>Cc Dave Martin <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/include/asm/futex.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)arch/arm/include/asm/futex.h +2
-2@@ -110,13 +110,13 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr,preempt_disable (); __ua_flags =uaccess_save_and_enable (); __asm__ __volatile__("@futex_atomic_cmpxchg_inatomic\n" - "1: " TUSER(ldr) " %1, [%4]\n" -" teq %1, %2\n" + "1: " TUSER(ldr) " %1, [%2]\n" +" teq %1, %3\n" arch/arm/include/asm/futex.h futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr, · line 121
Quoted 10 lines
arch/arm/include/asm/futex.h +3
-3" it eq @ explicit IT needed for the 2b label\n" - "2: " TUSER(streq) " %3, [%4]\n" + "2: " TUSER(streq) " %4, [%2]\n" __futex_atomic_ex_table("%5" ) - : "+r" (ret), "=&r" (val) - : "r" (oldval), "r" (newval), "r" (uaddr), "Ir" (-EFAULT) + : "+&r" (ret), "=&r" (val), "+&r" (uaddr) + : "r" (oldval), "r" (newval), "Ir" (-EFAULT) : "cc", "memory"); uaccess_restore(__ua_flags);Underspecification of constraints to extended inline assembly is a
Quoted 8 lines
common issue exposed by other compilers (and possibly but in-effect infrequently compiler upgrades).
So the reordering of the constraints means the in the assembly (notes for other reviewers):
%2 -> %3
%3 -> %4
%4 -> %2
Yep, looks good to me, thanks for finding this old patch and resending, Arnd!
I don't see what is "underspecified" in the original constraints. Please explain.
Signature · 3 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up
Re: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 8 lines · Russell King - ARM Linux admin
Quoted 3 lines · Nick Desaulniers
Underspecification of constraints to extended inline assembly is a common issue exposed by other compilers (and possibly but in-effect infrequently compiler upgrades).
I don't see what is "underspecified" in the original constraints. Please explain.
From the link:
The problem is that in the T(streq) insn, %3 and %4 MUST be different registers, but nothing in the asm() constrains them to be different.
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
"One way of fixing this is to make uaddr an input/output register, since "that prevents it from overlapping any other input or output."
Signature · 2 lines
Thanks, ~Nick Desaulniers
Russell King - ARM Linux admin
maintainerRe: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 8 lines · Nick Desaulniers
Quoted 6 lines · Russell King - ARM Linux admin
Quoted 3 lines · Nick Desaulniers
Underspecification of constraints to extended inline assembly is a common issue exposed by other compilers (and possibly but in-effect infrequently compiler upgrades).
Quoted 7 lines
Quoted 2 lines
I don't see what is "underspecified" in the original constraints. Please explain.
From the link:
The problem is that in the T(streq) insn, %3 and %4 MUST be different registers, but nothing in the
asm()constrains them to be different.
Thanks, but that is not what I'm asking. See my reply to Ard.
Signature · 3 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up
Re: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
In reply to Russell King - ARM Linux adminQuoted 65 lines · Russell King - ARM Linux admin
Quoted 54 lines · Nick Desaulniers
Quoted 41 lines · Arnd Bergmann
Passing registers containing zero as both the address (NULL pointer) and data into
cmpxchg_futex_value_locked()leads clang to assign the same register for both inputs on ARM, which triggers a warning explaining that this instruction has unpredictable behavior on ARMv5.
/tmp/futex-7e740e.s: Assembler messages:/tmp/futex-7e740e.s:12713: Warning: source register same as write-back baseThis patch was suggested by Mikael Pettersson back in 2011 (!) with gcc-4.4, as Mikael wrote:
"One way of fixing this is to make uaddr an input/output register, since "that prevents it from overlapping any other input or output."but then withdrawn as the warning was determined to be harmless, and it apparently never showed up again with later gcc versions.
Now the same problem is back when compiling with clang, and we are trying to get clang to build the kernel without warnings, as gcc normally does.
Cc Mikael Pettersson <[email protected]>Cc Mikael Pettersson <[email protected]>Cc Dave Martin <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/include/asm/futex.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)arch/arm/include/asm/futex.h +2
-2@@ -110,13 +110,13 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr,preempt_disable (); __ua_flags =uaccess_save_and_enable (); __asm__ __volatile__("@futex_atomic_cmpxchg_inatomic\n" - "1: " TUSER(ldr) " %1, [%4]\n" -" teq %1, %2\n" + "1: " TUSER(ldr) " %1, [%2]\n" +" teq %1, %3\n" arch/arm/include/asm/futex.h futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr, · line 121
Quoted 10 lines
arch/arm/include/asm/futex.h +3
-3" it eq @ explicit IT needed for the 2b label\n" - "2: " TUSER(streq) " %3, [%4]\n" + "2: " TUSER(streq) " %4, [%2]\n" __futex_atomic_ex_table("%5" ) - : "+r" (ret), "=&r" (val) - : "r" (oldval), "r" (newval), "r" (uaddr), "Ir" (-EFAULT) + : "+&r" (ret), "=&r" (val), "+&r" (uaddr) + : "r" (oldval), "r" (newval), "Ir" (-EFAULT) : "cc", "memory"); uaccess_restore(__ua_flags);Underspecification of constraints to extended inline assembly is a
Quoted 8 lines
common issue exposed by other compilers (and possibly but in-effect infrequently compiler upgrades).
So the reordering of the constraints means the in the assembly (notes for other reviewers):
%2 -> %3
%3 -> %4
%4 -> %2
Yep, looks good to me, thanks for finding this old patch and resending, Arnd!
Quoted 3 lines
I don't see what is "underspecified" in the original constraints. Please explain.
I agree that that statement makes little sense.
As Russell points out in the referenced thread, there is nothing wrong with the generated assembly, given that the UNPREDICTABLE opcode is unreachable in practice. Unfortunately, we have no way to flag this diagnostic as a known false positive, and AFAICT, there is no reason we couldn't end up with the same diagnostic popping up for GCC builds in the future, considering that the register assignment matches the constraints. (We have seen somewhat similar issues where constant folded function clones are emitted with a constant argument that could never occur in reality [0])
Given the above, the only meaningful way to invoke this function is with different registers assigned to %3 and %4, and so tightening the constraints to guarantee that does not actually result in worse code (except maybe for the instantiations that we won't ever call in the first place). So I think we should fix this.
I wonder if just adding
BUG_ON(__builtin_constant_p(uaddr));
at the beginning makes any difference - this shouldn't result in any object code differences since the conditional will always evaluate to false at build time for instantiations we care about.
Russell King - ARM Linux admin
maintainerRe: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 91 lines · Ard Biesheuvel
Quoted 65 lines · Russell King - ARM Linux admin
Quoted 54 lines · Nick Desaulniers
Quoted 41 lines · Arnd Bergmann
Passing registers containing zero as both the address (NULL pointer) and data into
cmpxchg_futex_value_locked()leads clang to assign the same register for both inputs on ARM, which triggers a warning explaining that this instruction has unpredictable behavior on ARMv5.
/tmp/futex-7e740e.s: Assembler messages:/tmp/futex-7e740e.s:12713: Warning: source register same as write-back baseThis patch was suggested by Mikael Pettersson back in 2011 (!) with gcc-4.4, as Mikael wrote:
"One way of fixing this is to make uaddr an input/output register, since "that prevents it from overlapping any other input or output."but then withdrawn as the warning was determined to be harmless, and it apparently never showed up again with later gcc versions.
Now the same problem is back when compiling with clang, and we are trying to get clang to build the kernel without warnings, as gcc normally does.
Cc Mikael Pettersson <[email protected]>Cc Mikael Pettersson <[email protected]>Cc Dave Martin <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/include/asm/futex.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)arch/arm/include/asm/futex.h +2
-2@@ -110,13 +110,13 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr,preempt_disable (); __ua_flags =uaccess_save_and_enable (); __asm__ __volatile__("@futex_atomic_cmpxchg_inatomic\n" - "1: " TUSER(ldr) " %1, [%4]\n" -" teq %1, %2\n" + "1: " TUSER(ldr) " %1, [%2]\n" +" teq %1, %3\n" arch/arm/include/asm/futex.h futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr, · line 121
Quoted 10 lines
arch/arm/include/asm/futex.h +3
-3" it eq @ explicit IT needed for the 2b label\n" - "2: " TUSER(streq) " %3, [%4]\n" + "2: " TUSER(streq) " %4, [%2]\n" __futex_atomic_ex_table("%5" ) - : "+r" (ret), "=&r" (val) - : "r" (oldval), "r" (newval), "r" (uaddr), "Ir" (-EFAULT) + : "+&r" (ret), "=&r" (val), "+&r" (uaddr) + : "r" (oldval), "r" (newval), "Ir" (-EFAULT) : "cc", "memory"); uaccess_restore(__ua_flags);Underspecification of constraints to extended inline assembly is a
Quoted 8 lines
common issue exposed by other compilers (and possibly but in-effect infrequently compiler upgrades).
So the reordering of the constraints means the in the assembly (notes for other reviewers):
%2 -> %3
%3 -> %4
%4 -> %2
Yep, looks good to me, thanks for finding this old patch and resending, Arnd!Quoted 3 lines
I don't see what is "underspecified" in the original constraints. Please explain.
I agree that that statement makes little sense.
As Russell points out in the referenced thread, there is nothing wrong with the generated assembly, given that the UNPREDICTABLE opcode is unreachable in practice. Unfortunately, we have no way to flag this diagnostic as a known false positive, and AFAICT, there is no reason we couldn't end up with the same diagnostic popping up for GCC builds in the future, considering that the register assignment matches the constraints. (We have seen somewhat similar issues where constant folded function clones are emitted with a constant argument that could never occur in reality [0])
Given the above, the only meaningful way to invoke this function is with different registers assigned to %3 and %4, and so tightening the constraints to guarantee that does not actually result in worse code (except maybe for the instantiations that we won't ever call in the first place). So I think we should fix this.
I wonder if just adding
Quoted 8 lines
BUG_ON(__builtin_constant_p(uaddr));
at the beginning makes any difference - this shouldn't result in any object code differences since the conditional will always evaluate to false at build time for instantiations we care about.
What I'm actually asking is:
The GCC manual says that input operands _may_ overlap output operands since GCC assumes that input operands are consumed before output operands are written. This is an explicit statement.
The GCC manual does not say that input operands may overlap with each other, and the behaviour of GCC thus far (apart from one version, presumably caused by a bug) has been that input operands are unique.
Clang appears to be different: it allows input operands that are registers, and contain the same constant value to be the same physical register.
The assertion is that the constraints are under-specified. I am questioning that assertion.
If the constraints are under-specified, I would have expected gcc-4.4's behaviour to have persisted, and we would've been told by gcc's developers to fix our code. That didn't happen, and instead gcc seems to have been fixed. So, my conclusion is that it is intentional that input operands to asm() do not overlap with themselves.
It seems to me that the work-around for clang is to change every input operand to be an output operand with a "+&r" contraint - an operand that is both read and written by the "instruction", and that the operand is "earlyclobber". For something that is really only read, that seems strange.
Also, reading GCC's manual, it would appear that "+&" is wrong.
`+'
Means that this operand is both read and written by the instruction.
When the compiler fixes up the operands to satisfy the constraints, it needs to know which operands are inputs to the instruction and which are outputs from it. =' identifies an output; +' identifies an operand that is both input and output; all other
^^^^^^^^^^^^^^^^^^^^^
operands are assumed to be input only.
`&'
Means (in a particular alternative) that this operand is an "earlyclobber" operand, which is modified before the instruction is finished using the input operands. Therefore, this operand may not lie in a register that is used as an input operand or as part ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ of any memory address.
So "+" says that this operand is an input but "&" says that it must not be in a register that is used as an input. That's contradictory, and I think we can expect GCC to barf or at least end up doing strange stuff, if not with existing versions, then with future versions.
Hence, I'm asking for clarification why it is thought that the existing code underspecifies the asm constraints, and I'm trying to get some more thought about what the constraints should be, in case there is a need to use "better" constraints.
Signature · 3 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up
Re: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 104 lines · Russell King - ARM Linux admin
Quoted 91 lines · Ard Biesheuvel
Quoted 65 lines · Russell King - ARM Linux admin
Quoted 54 lines · Nick Desaulniers
Quoted 41 lines · Arnd Bergmann
Passing registers containing zero as both the address (NULL pointer) and data into
cmpxchg_futex_value_locked()leads clang to assign the same register for both inputs on ARM, which triggers a warning explaining that this instruction has unpredictable behavior on ARMv5.
/tmp/futex-7e740e.s: Assembler messages:/tmp/futex-7e740e.s:12713: Warning: source register same as write-back baseThis patch was suggested by Mikael Pettersson back in 2011 (!) with gcc-4.4, as Mikael wrote:
"One way of fixing this is to make uaddr an input/output register, since "that prevents it from overlapping any other input or output."but then withdrawn as the warning was determined to be harmless, and it apparently never showed up again with later gcc versions.
Now the same problem is back when compiling with clang, and we are trying to get clang to build the kernel without warnings, as gcc normally does.
Cc Mikael Pettersson <[email protected]>Cc Mikael Pettersson <[email protected]>Cc Dave Martin <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/include/asm/futex.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)arch/arm/include/asm/futex.h +2
-2@@ -110,13 +110,13 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr,preempt_disable (); __ua_flags =uaccess_save_and_enable (); __asm__ __volatile__("@futex_atomic_cmpxchg_inatomic\n" - "1: " TUSER(ldr) " %1, [%4]\n" -" teq %1, %2\n" + "1: " TUSER(ldr) " %1, [%2]\n" +" teq %1, %3\n" arch/arm/include/asm/futex.h futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr, · line 121
Quoted 10 lines
arch/arm/include/asm/futex.h +3
-3" it eq @ explicit IT needed for the 2b label\n" - "2: " TUSER(streq) " %3, [%4]\n" + "2: " TUSER(streq) " %4, [%2]\n" __futex_atomic_ex_table("%5" ) - : "+r" (ret), "=&r" (val) - : "r" (oldval), "r" (newval), "r" (uaddr), "Ir" (-EFAULT) + : "+&r" (ret), "=&r" (val), "+&r" (uaddr) + : "r" (oldval), "r" (newval), "Ir" (-EFAULT) : "cc", "memory"); uaccess_restore(__ua_flags);Underspecification of constraints to extended inline assembly is a
Quoted 8 lines
common issue exposed by other compilers (and possibly but in-effect infrequently compiler upgrades).
So the reordering of the constraints means the in the assembly (notes for other reviewers):
%2 -> %3
%3 -> %4
%4 -> %2
Yep, looks good to me, thanks for finding this old patch and resending, Arnd!Quoted 3 lines
I don't see what is "underspecified" in the original constraints. Please explain.
I agree that that statement makes little sense.
As Russell points out in the referenced thread, there is nothing wrong with the generated assembly, given that the UNPREDICTABLE opcode is unreachable in practice. Unfortunately, we have no way to flag this diagnostic as a known false positive, and AFAICT, there is no reason we couldn't end up with the same diagnostic popping up for GCC builds in the future, considering that the register assignment matches the constraints. (We have seen somewhat similar issues where constant folded function clones are emitted with a constant argument that could never occur in reality [0])
Given the above, the only meaningful way to invoke this function is with different registers assigned to %3 and %4, and so tightening the constraints to guarantee that does not actually result in worse code (except maybe for the instantiations that we won't ever call in the first place). So I think we should fix this.
I wonder if just adding
Quoted 8 lines
BUG_ON(__builtin_constant_p(uaddr));
at the beginning makes any difference - this shouldn't result in any object code differences since the conditional will always evaluate to false at build time for instantiations we care about.
What I'm actually asking is:
Quoted 8 lines
The GCC manual says that input operands _may_ overlap output operands since GCC assumes that input operands are consumed before output operands are written. This is an explicit statement.
The GCC manual does not say that input operands may overlap with each other, and the behaviour of GCC thus far (apart from one version, presumably caused by a bug) has been that input operands are unique.
Not entirely. I have run into issues where GCC assumes that registers that are only used for input operands are left untouched by the asm code. I.e., if you put an asm() block in a loop and modify an input register, your code may break on the next pass, even if the input register does not overlap with an output register.
To me, that seems to suggest that whether or not inputs may overlap is irrelevant, since they are not expected to be modified.
Quoted 4 lines
Clang appears to be different: it allows input operands that are registers, and contain the same constant value to be the same physical register.
Quoted 9 lines
The assertion is that the constraints are under-specified. I am questioning that assertion.
If the constraints are under-specified, I would have expected gcc-4.4's behaviour to have persisted, and we would've been told by gcc's developers to fix our code. That didn't happen, and instead gcc seems to have been fixed. So, my conclusion is that it is intentional that input operands to
asm()do not overlap with themselves.
Whether we hit the error or not is not deterministic. Like in the ilog2() case I quoted, GCC may decide to instantiate a constant folded ['curried', if you will] clone of a function, and so even if any calls to futex_atomic_cmpxchg_inatomic() with constant NULL args for newval and uaddr are compiled, it does not mean they occur like that in the C code.
Quoted 27 lines
It seems to me that the work-around for clang is to change every input operand to be an output operand with a "+&r" contraint - an operand that is both read and written by the "instruction", and that the operand is "earlyclobber". For something that is really only read, that seems strange.
Also, reading GCC's manual, it would appear that "+&" is wrong.
`+'
Means that this operand is both read and written by the instruction.When the compiler fixes up the operands to satisfy the constraints, it needs to know which operands are inputs to the instruction and which are outputs from it.
=' identifies an output;+' identifies an operand that is both input and output; all other
^^^^^^^^^^^^^^^^^^^^^
operands are assumed to be input only.`&'
Means (in a particular alternative) that this operand is an "earlyclobber" operand, which is modified before the instruction is finished using the input operands. Therefore, this operand may not lie in a register that is used as an input operand or as part ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ of any memory address.
Quoted 5 lines
So "+" says that this operand is an input but "&" says that it must not be in a register that is used as an input. That's contradictory, and I think we can expect GCC to barf or at least end up doing strange stuff, if not with existing versions, then with future versions.
I wondered about the same thing: given that the asm itself is a black box to the compiler, it can never reuse an in/output register for output, so when it is clobbered is irrelevant.
Quoted 5 lines
Hence, I'm asking for clarification why it is thought that the existing code underspecifies the asm constraints, and I'm trying to get some more thought about what the constraints should be, in case there is a need to use "better" constraints.
I think the constraints are correct, but as I argued before, tightening the constraints to ensure that uaddr and newval are not mapped onto the same register should not result in any object code changes, except for the case where the compiler instantiated a constprop clone that is bogus to begin with.
Re: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 189 lines · Ard Biesheuvel
Quoted 104 lines · Russell King - ARM Linux admin
Quoted 91 lines · Ard Biesheuvel
Quoted 65 lines · Russell King - ARM Linux admin
Quoted 54 lines · Nick Desaulniers
Quoted 41 lines · Arnd Bergmann
Passing registers containing zero as both the address (NULL pointer) and data into
cmpxchg_futex_value_locked()leads clang to assign the same register for both inputs on ARM, which triggers a warning explaining that this instruction has unpredictable behavior on ARMv5.
/tmp/futex-7e740e.s: Assembler messages:/tmp/futex-7e740e.s:12713: Warning: source register same as write-back baseThis patch was suggested by Mikael Pettersson back in 2011 (!) with gcc-4.4, as Mikael wrote:
"One way of fixing this is to make uaddr an input/output register, since "that prevents it from overlapping any other input or output."but then withdrawn as the warning was determined to be harmless, and it apparently never showed up again with later gcc versions.
Now the same problem is back when compiling with clang, and we are trying to get clang to build the kernel without warnings, as gcc normally does.
Cc Mikael Pettersson <[email protected]>Cc Mikael Pettersson <[email protected]>Cc Dave Martin <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/include/asm/futex.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)arch/arm/include/asm/futex.h +2
-2@@ -110,13 +110,13 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr,preempt_disable (); __ua_flags =uaccess_save_and_enable (); __asm__ __volatile__("@futex_atomic_cmpxchg_inatomic\n" - "1: " TUSER(ldr) " %1, [%4]\n" -" teq %1, %2\n" + "1: " TUSER(ldr) " %1, [%2]\n" +" teq %1, %3\n" arch/arm/include/asm/futex.h futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr, · line 121
Quoted 10 lines
arch/arm/include/asm/futex.h +3
-3" it eq @ explicit IT needed for the 2b label\n" - "2: " TUSER(streq) " %3, [%4]\n" + "2: " TUSER(streq) " %4, [%2]\n" __futex_atomic_ex_table("%5" ) - : "+r" (ret), "=&r" (val) - : "r" (oldval), "r" (newval), "r" (uaddr), "Ir" (-EFAULT) + : "+&r" (ret), "=&r" (val), "+&r" (uaddr) + : "r" (oldval), "r" (newval), "Ir" (-EFAULT) : "cc", "memory"); uaccess_restore(__ua_flags);Underspecification of constraints to extended inline assembly is a
Quoted 8 lines
common issue exposed by other compilers (and possibly but in-effect infrequently compiler upgrades).
So the reordering of the constraints means the in the assembly (notes for other reviewers):
%2 -> %3
%3 -> %4
%4 -> %2
Yep, looks good to me, thanks for finding this old patch and resending, Arnd!Quoted 3 lines
I don't see what is "underspecified" in the original constraints. Please explain.
I agree that that statement makes little sense.
As Russell points out in the referenced thread, there is nothing wrong with the generated assembly, given that the UNPREDICTABLE opcode is unreachable in practice. Unfortunately, we have no way to flag this diagnostic as a known false positive, and AFAICT, there is no reason we couldn't end up with the same diagnostic popping up for GCC builds in the future, considering that the register assignment matches the constraints. (We have seen somewhat similar issues where constant folded function clones are emitted with a constant argument that could never occur in reality [0])
Given the above, the only meaningful way to invoke this function is with different registers assigned to %3 and %4, and so tightening the constraints to guarantee that does not actually result in worse code (except maybe for the instantiations that we won't ever call in the first place). So I think we should fix this.
I wonder if just adding
Quoted 8 lines
BUG_ON(__builtin_constant_p(uaddr));
at the beginning makes any difference - this shouldn't result in any object code differences since the conditional will always evaluate to false at build time for instantiations we care about.
What I'm actually asking is:
Quoted 8 lines
The GCC manual says that input operands _may_ overlap output operands since GCC assumes that input operands are consumed before output operands are written. This is an explicit statement.
The GCC manual does not say that input operands may overlap with each other, and the behaviour of GCC thus far (apart from one version, presumably caused by a bug) has been that input operands are unique.
Not entirely. I have run into issues where GCC assumes that registers that are only used for input operands are left untouched by the asm code. I.e., if you put an
asm()block in a loop and modify an input register, your code may break on the next pass, even if the input register does not overlap with an output register.To me, that seems to suggest that whether or not inputs may overlap is irrelevant, since they are not expected to be modified.
Quoted 4 lines
Clang appears to be different: it allows input operands that are registers, and contain the same constant value to be the same physical register.
Quoted 9 lines
The assertion is that the constraints are under-specified. I am questioning that assertion.
If the constraints are under-specified, I would have expected gcc-4.4's behaviour to have persisted, and we would've been told by gcc's developers to fix our code. That didn't happen, and instead gcc seems to have been fixed. So, my conclusion is that it is intentional that input operands to
asm()do not overlap with themselves.Whether we hit the error or not is not deterministic. Like in the
ilog2()case I quoted, GCC may decide to instantiate a constant folded ['curried', if you will] clone of a function, and so even if any calls tofutex_atomic_cmpxchg_inatomic()with constant NULL args for newval and uaddr are compiled, it does not mean they occur like that in the C code.Quoted 27 lines
It seems to me that the work-around for clang is to change every input operand to be an output operand with a "+&r" contraint - an operand that is both read and written by the "instruction", and that the operand is "earlyclobber". For something that is really only read, that seems strange.
Also, reading GCC's manual, it would appear that "+&" is wrong.
`+'
Means that this operand is both read and written by the instruction.When the compiler fixes up the operands to satisfy the constraints, it needs to know which operands are inputs to the instruction and which are outputs from it.
=' identifies an output;+' identifies an operand that is both input and output; all other
^^^^^^^^^^^^^^^^^^^^^
operands are assumed to be input only.`&'
Means (in a particular alternative) that this operand is an "earlyclobber" operand, which is modified before the instruction is finished using the input operands. Therefore, this operand may not lie in a register that is used as an input operand or as part ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ of any memory address.Quoted 5 lines
So "+" says that this operand is an input but "&" says that it must not be in a register that is used as an input. That's contradictory, and I think we can expect GCC to barf or at least end up doing strange stuff, if not with existing versions, then with future versions.
I wondered about the same thing: given that the asm itself is a black box to the compiler, it can never reuse an in/output register for output, so when it is clobbered is irrelevant.
Quoted 5 lines
Hence, I'm asking for clarification why it is thought that the existing code underspecifies the asm constraints, and I'm trying to get some more thought about what the constraints should be, in case there is a need to use "better" constraints.
Quoted 5 lines
I think the constraints are correct, but as I argued before, tightening the constraints to ensure that uaddr and newval are not mapped onto the same register should not result in any object code changes, except for the case where the compiler instantiated a constprop clone that is bogus to begin with.
Compiling the following code
"""
#include <stdio.h>
static void foo(void *a, int b)
{
asm("str %0, [%1]" :: "r"(a), "r"(b));
}int main(void)
{
foo(NULL, 0);
}"""
with GCC 6.3 (at -O2) gives me
.arch armv7-a
.eabi_attribute 28, 1
.eabi_attribute 20, 1
.eabi_attribute 21, 1
.eabi_attribute 23, 3
.eabi_attribute 24, 1
.eabi_attribute 25, 1
.eabi_attribute 26, 2
.eabi_attribute 30, 2
.eabi_attribute 34, 1
.eabi_attribute 18, 4
.file "futex.c"
.section .text.startup,"ax",%progbits
.align 1
.p2align 2,,3
.global main
.syntax unified
.thumb
.thumb_func
.fpu vfpv3-d16
.type main, %function
main:
@ args = 0, pretend = 0, frame = 0
@ frame_needed = 0, uses_anonymous_args = 0
@ link register save eliminated.
movs r0, #0
.syntax unified
@ 6 "/tmp/futex.c" 1
str r0, [r0]
@ 0 "" 2
.thumb
.syntax unified
bx lr
.size main, .-main
.ident "GCC: (Debian 6.3.0-18) 6.3.0 20170516"
.section .note.GNU-stack,"",%progbits
and so GCC definitely behaves similar in this regard.
Russell King - ARM Linux admin
maintainerRe: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 55 lines · Ard Biesheuvel
Compiling the following code
"""
#include <stdio.h>static void
foo(void *a, int b){ asm("str %0, [%1]" :: "r"(a), "r"(b)); }int main(void)
{ foo(NULL, 0); }"""
with GCC 6.3 (at -O2) gives me
.arch armv7-a
.eabi_attribute 28, 1
.eabi_attribute 20, 1
.eabi_attribute 21, 1
.eabi_attribute 23, 3
.eabi_attribute 24, 1
.eabi_attribute 25, 1
.eabi_attribute 26, 2
.eabi_attribute 30, 2
.eabi_attribute 34, 1
.eabi_attribute 18, 4
.file "futex.c"
.section .text.startup,"ax",%progbits
.align 1
.p2align 2,,3
.global main
.syntax unified
.thumb
.thumb_func
.fpu vfpv3-d16
.type main, %function
main:
@ args = 0, pretend = 0, frame = 0
@frame_needed= 0,uses_anonymous_args= 0
@ link register save eliminated.
movs r0, #0
.syntax unified
@ 6 "/tmp/futex.c" 1
str r0, [r0]
@ 0 "" 2
.thumb
.syntax unified
bx lr
.size main, .-main
.ident "GCC: (Debian 6.3.0-18) 6.3.0 20170516"
.section .note.GNU-stack,"",%progbits
Quoted 1 line
and so GCC definitely behaves similar in this regard.
Let's take this further - a volatile is required for these cases to avoid gcc eliminating the asm() due to the output not being used:
#define NULL ((void *)0)
static void foo(void *a, int b)
{
asm volatile("str %1, [%0]" : "=&r" (a) : "0" (a), "r" (b));
}
int main(void)
{
foo(NULL, 0);
}produces:
mov r3, #0
mov r2, r3
str r2, [r2]which looks to me to be incorrect to the GCC manual - the '&' on the output operand should mean that it does not conflict with other input operands, but clearly 'r2' has ended up being 'b' as well. I suspect this is a bug, or if not, is completely counter-intuitive from the description in the GCC manual.
Using "+r" (a) : "r" (b) also results in:
mov r3, #0
str r3, [r3]It seems that only using "+&r" (a) : "r" (b) avoids a and b being in the same register, but I question whether we are stepping into undefined compiler behaviour with that.
Signature · 3 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up
Russell King - ARM Linux admin
maintainerRe: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
In reply to Ard BiesheuvelQuoted 115 lines · Ard Biesheuvel
Quoted 104 lines · Russell King - ARM Linux admin
Quoted 91 lines · Ard Biesheuvel
Quoted 65 lines · Russell King - ARM Linux admin
Quoted 54 lines · Nick Desaulniers
Quoted 41 lines · Arnd Bergmann
Passing registers containing zero as both the address (NULL pointer) and data into
cmpxchg_futex_value_locked()leads clang to assign the same register for both inputs on ARM, which triggers a warning explaining that this instruction has unpredictable behavior on ARMv5.
/tmp/futex-7e740e.s: Assembler messages:/tmp/futex-7e740e.s:12713: Warning: source register same as write-back baseThis patch was suggested by Mikael Pettersson back in 2011 (!) with gcc-4.4, as Mikael wrote:
"One way of fixing this is to make uaddr an input/output register, since "that prevents it from overlapping any other input or output."but then withdrawn as the warning was determined to be harmless, and it apparently never showed up again with later gcc versions.
Now the same problem is back when compiling with clang, and we are trying to get clang to build the kernel without warnings, as gcc normally does.
Cc Mikael Pettersson <[email protected]>Cc Mikael Pettersson <[email protected]>Cc Dave Martin <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/include/asm/futex.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)arch/arm/include/asm/futex.h +2
-2@@ -110,13 +110,13 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr,preempt_disable (); __ua_flags =uaccess_save_and_enable (); __asm__ __volatile__("@futex_atomic_cmpxchg_inatomic\n" - "1: " TUSER(ldr) " %1, [%4]\n" -" teq %1, %2\n" + "1: " TUSER(ldr) " %1, [%2]\n" +" teq %1, %3\n" arch/arm/include/asm/futex.h futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr, · line 121
Quoted 10 lines
arch/arm/include/asm/futex.h +3
-3" it eq @ explicit IT needed for the 2b label\n" - "2: " TUSER(streq) " %3, [%4]\n" + "2: " TUSER(streq) " %4, [%2]\n" __futex_atomic_ex_table("%5" ) - : "+r" (ret), "=&r" (val) - : "r" (oldval), "r" (newval), "r" (uaddr), "Ir" (-EFAULT) + : "+&r" (ret), "=&r" (val), "+&r" (uaddr) + : "r" (oldval), "r" (newval), "Ir" (-EFAULT) : "cc", "memory"); uaccess_restore(__ua_flags);Underspecification of constraints to extended inline assembly is a
Quoted 8 lines
common issue exposed by other compilers (and possibly but in-effect infrequently compiler upgrades).
So the reordering of the constraints means the in the assembly (notes for other reviewers):
%2 -> %3
%3 -> %4
%4 -> %2
Yep, looks good to me, thanks for finding this old patch and resending, Arnd!Quoted 3 lines
I don't see what is "underspecified" in the original constraints. Please explain.
I agree that that statement makes little sense.
As Russell points out in the referenced thread, there is nothing wrong with the generated assembly, given that the UNPREDICTABLE opcode is unreachable in practice. Unfortunately, we have no way to flag this diagnostic as a known false positive, and AFAICT, there is no reason we couldn't end up with the same diagnostic popping up for GCC builds in the future, considering that the register assignment matches the constraints. (We have seen somewhat similar issues where constant folded function clones are emitted with a constant argument that could never occur in reality [0])
Given the above, the only meaningful way to invoke this function is with different registers assigned to %3 and %4, and so tightening the constraints to guarantee that does not actually result in worse code (except maybe for the instantiations that we won't ever call in the first place). So I think we should fix this.
I wonder if just adding
Quoted 8 lines
BUG_ON(__builtin_constant_p(uaddr));
at the beginning makes any difference - this shouldn't result in any object code differences since the conditional will always evaluate to false at build time for instantiations we care about.
What I'm actually asking is:
Quoted 8 lines
The GCC manual says that input operands _may_ overlap output operands since GCC assumes that input operands are consumed before output operands are written. This is an explicit statement.
The GCC manual does not say that input operands may overlap with each other, and the behaviour of GCC thus far (apart from one version, presumably caused by a bug) has been that input operands are unique.
Quoted 5 lines
Not entirely. I have run into issues where GCC assumes that registers that are only used for input operands are left untouched by the asm code. I.e., if you put an
asm()block in a loop and modify an input register, your code may break on the next pass, even if the input register does not overlap with an output register.
GCC has had the expectation for decades that _input_ operands are not changed in value by the code in the assembly. This isn't quite the same thing as the uniqueness of the register allocation for input operands.
Quoted 2 lines
To me, that seems to suggest that whether or not inputs may overlap is irrelevant, since they are not expected to be modified.
How is:
stmfd sp!, {r0-r3, ip, lr}
bl foo
ldmfd sp!, {r0-r3, ip, lr}where r1 may be an input operand (to pass an argument to foo) any different from:
ldrt r0, [r1]
as far as whether r1 is modified in both cases? In both cases, the value of r1 is read and written by both instructions, but in both cases the value of r1 remains the same no matter what the value of r1 was.
The "input operands should not be modified" is entirely orthogonal to the input operand register allocation.
Quoted 14 lines
Quoted 4 lines
Clang appears to be different: it allows input operands that are registers, and contain the same constant value to be the same physical register.
Quoted 9 lines
The assertion is that the constraints are under-specified. I am questioning that assertion.
If the constraints are under-specified, I would have expected gcc-4.4's behaviour to have persisted, and we would've been told by gcc's developers to fix our code. That didn't happen, and instead gcc seems to have been fixed. So, my conclusion is that it is intentional that input operands to
asm()do not overlap with themselves.
Quoted 6 lines
Whether we hit the error or not is not deterministic. Like in the
ilog2()case I quoted, GCC may decide to instantiate a constant folded ['curried', if you will] clone of a function, and so even if any calls tofutex_atomic_cmpxchg_inatomic()with constant NULL args for newval and uaddr are compiled, it does not mean they occur like that in the C code.
Again, I think this is different: gcc knows what the C code is doing and can optimise it. GCC doesn't have any idea what the code in an asm() is doing beyond what the constraints are telling it, and the rules for those constraints set out in the GCC manual.
Given that we are explicitly talking about the register allocation for input operands, I'm not sure how the ilog2() case you mention applies.
Quoted 33 lines
Quoted 27 lines
It seems to me that the work-around for clang is to change every input operand to be an output operand with a "+&r" contraint - an operand that is both read and written by the "instruction", and that the operand is "earlyclobber". For something that is really only read, that seems strange.
Also, reading GCC's manual, it would appear that "+&" is wrong.
`+'
Means that this operand is both read and written by the instruction.When the compiler fixes up the operands to satisfy the constraints, it needs to know which operands are inputs to the instruction and which are outputs from it.
=' identifies an output;+' identifies an operand that is both input and output; all other
^^^^^^^^^^^^^^^^^^^^^
operands are assumed to be input only.`&'
Means (in a particular alternative) that this operand is an "earlyclobber" operand, which is modified before the instruction is finished using the input operands. Therefore, this operand may not lie in a register that is used as an input operand or as part ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ of any memory address.Quoted 5 lines
So "+" says that this operand is an input but "&" says that it must not be in a register that is used as an input. That's contradictory, and I think we can expect GCC to barf or at least end up doing strange stuff, if not with existing versions, then with future versions.
Quoted 3 lines
I wondered about the same thing: given that the asm itself is a black box to the compiler, it can never reuse an in/output register for output, so when it is clobbered is irrelevant.
Let me try again - you seem to have completely missed my point.
+ specifies that the operand is an input.
& specifies that the operand is not an input.
+ and & are contradictory.
GCC is at liberty to not assign a value to an operand with a +& modifier, or error out such a construction.
Quoted 11 lines
Quoted 5 lines
Hence, I'm asking for clarification why it is thought that the existing code underspecifies the asm constraints, and I'm trying to get some more thought about what the constraints should be, in case there is a need to use "better" constraints.
I think the constraints are correct, but as I argued before, tightening the constraints to ensure that uaddr and newval are not mapped onto the same register should not result in any object code changes, except for the case where the compiler instantiated a constprop clone that is bogus to begin with.
... by tightening it to an undefined combination of constraint modifiers that just happens to seem to do the right thing. No, this is not proper "engineering". This is bodging.
Signature · 3 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up
Re: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 142 lines · Russell King - ARM Linux admin
Quoted 115 lines · Ard Biesheuvel
Quoted 104 lines · Russell King - ARM Linux admin
Quoted 91 lines · Ard Biesheuvel
Quoted 65 lines · Russell King - ARM Linux admin
Quoted 54 lines · Nick Desaulniers
Quoted 41 lines · Arnd Bergmann
Passing registers containing zero as both the address (NULL pointer) and data into
cmpxchg_futex_value_locked()leads clang to assign the same register for both inputs on ARM, which triggers a warning explaining that this instruction has unpredictable behavior on ARMv5.
/tmp/futex-7e740e.s: Assembler messages:/tmp/futex-7e740e.s:12713: Warning: source register same as write-back baseThis patch was suggested by Mikael Pettersson back in 2011 (!) with gcc-4.4, as Mikael wrote:
"One way of fixing this is to make uaddr an input/output register, since "that prevents it from overlapping any other input or output."but then withdrawn as the warning was determined to be harmless, and it apparently never showed up again with later gcc versions.
Now the same problem is back when compiling with clang, and we are trying to get clang to build the kernel without warnings, as gcc normally does.
Cc Mikael Pettersson <[email protected]>Cc Mikael Pettersson <[email protected]>Cc Dave Martin <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/include/asm/futex.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)arch/arm/include/asm/futex.h +2
-2@@ -110,13 +110,13 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr,preempt_disable (); __ua_flags =uaccess_save_and_enable (); __asm__ __volatile__("@futex_atomic_cmpxchg_inatomic\n" - "1: " TUSER(ldr) " %1, [%4]\n" -" teq %1, %2\n" + "1: " TUSER(ldr) " %1, [%2]\n" +" teq %1, %3\n" arch/arm/include/asm/futex.h futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr, · line 121
Quoted 10 lines
arch/arm/include/asm/futex.h +3
-3" it eq @ explicit IT needed for the 2b label\n" - "2: " TUSER(streq) " %3, [%4]\n" + "2: " TUSER(streq) " %4, [%2]\n" __futex_atomic_ex_table("%5" ) - : "+r" (ret), "=&r" (val) - : "r" (oldval), "r" (newval), "r" (uaddr), "Ir" (-EFAULT) + : "+&r" (ret), "=&r" (val), "+&r" (uaddr) + : "r" (oldval), "r" (newval), "Ir" (-EFAULT) : "cc", "memory"); uaccess_restore(__ua_flags);Underspecification of constraints to extended inline assembly is a
Quoted 8 lines
common issue exposed by other compilers (and possibly but in-effect infrequently compiler upgrades).
So the reordering of the constraints means the in the assembly (notes for other reviewers):
%2 -> %3
%3 -> %4
%4 -> %2
Yep, looks good to me, thanks for finding this old patch and resending, Arnd!Quoted 3 lines
I don't see what is "underspecified" in the original constraints. Please explain.
I agree that that statement makes little sense.
As Russell points out in the referenced thread, there is nothing wrong with the generated assembly, given that the UNPREDICTABLE opcode is unreachable in practice. Unfortunately, we have no way to flag this diagnostic as a known false positive, and AFAICT, there is no reason we couldn't end up with the same diagnostic popping up for GCC builds in the future, considering that the register assignment matches the constraints. (We have seen somewhat similar issues where constant folded function clones are emitted with a constant argument that could never occur in reality [0])
Given the above, the only meaningful way to invoke this function is with different registers assigned to %3 and %4, and so tightening the constraints to guarantee that does not actually result in worse code (except maybe for the instantiations that we won't ever call in the first place). So I think we should fix this.
I wonder if just adding
Quoted 8 lines
BUG_ON(__builtin_constant_p(uaddr));
at the beginning makes any difference - this shouldn't result in any object code differences since the conditional will always evaluate to false at build time for instantiations we care about.
What I'm actually asking is:
Quoted 8 lines
The GCC manual says that input operands _may_ overlap output operands since GCC assumes that input operands are consumed before output operands are written. This is an explicit statement.
The GCC manual does not say that input operands may overlap with each other, and the behaviour of GCC thus far (apart from one version, presumably caused by a bug) has been that input operands are unique.
Quoted 5 lines
Not entirely. I have run into issues where GCC assumes that registers that are only used for input operands are left untouched by the asm code. I.e., if you put an
asm()block in a loop and modify an input register, your code may break on the next pass, even if the input register does not overlap with an output register.GCC has had the expectation for decades that _input_ operands are not changed in value by the code in the assembly. This isn't quite the same thing as the uniqueness of the register allocation for input operands.
Quoted 2 lines
To me, that seems to suggest that whether or not inputs may overlap is irrelevant, since they are not expected to be modified.
How is:
stmfd sp!, {r0-r3, ip, lr} bl foo ldmfd sp!, {r0-r3, ip, lr}where r1 may be an input operand (to pass an argument to foo) any different from:
ldrt r0, [r1]
Quoted 8 lines
as far as whether r1 is modified in both cases? In both cases, the value of r1 is read and written by both instructions, but in both cases the value of r1 remains the same no matter what the value of r1 was.
The "input operands should not be modified" is entirely orthogonal to the input operand register allocation.
The question is whether it is reasonable for GCC to use the same register for input operands that have the same value. From the assumption that GCC makes that the asm will not modified follows directly that we can use the same register for different operands.
And in fact, since that asm code (when built in ARM mode) does modify the register, uaddr should not be an input operand to begin with. In other words, there is an actual bug here, and this patch fixes it.
Quoted 21 lines
Quoted 14 lines
Quoted 4 lines
Clang appears to be different: it allows input operands that are registers, and contain the same constant value to be the same physical register.
Quoted 9 lines
The assertion is that the constraints are under-specified. I am questioning that assertion.
If the constraints are under-specified, I would have expected gcc-4.4's behaviour to have persisted, and we would've been told by gcc's developers to fix our code. That didn't happen, and instead gcc seems to have been fixed. So, my conclusion is that it is intentional that input operands to
asm()do not overlap with themselves.Quoted 6 lines
Whether we hit the error or not is not deterministic. Like in the
ilog2()case I quoted, GCC may decide to instantiate a constant folded ['curried', if you will] clone of a function, and so even if any calls tofutex_atomic_cmpxchg_inatomic()with constant NULL args for newval and uaddr are compiled, it does not mean they occur like that in the C code.
Quoted 8 lines
Again, I think this is different: gcc knows what the C code is doing and can optimise it. GCC doesn't have any idea what the code in an
asm()is doing beyond what the constraints are telling it, and the rules for those constraints set out in the GCC manual.Given that we are explicitly talking about the register allocation for input operands, I'm not sure how the
ilog2()case you mention applies.
The relevance of the ilog2() case is that we are dealing with an invocation of the function that never actually occurs in the code. The compiler emits it as part of an optimization step, and this is how we end up with constant operands for newval and uaddr.
Quoted 39 lines
Quoted 33 lines
Quoted 27 lines
It seems to me that the work-around for clang is to change every input operand to be an output operand with a "+&r" contraint - an operand that is both read and written by the "instruction", and that the operand is "earlyclobber". For something that is really only read, that seems strange.
Also, reading GCC's manual, it would appear that "+&" is wrong.
`+'
Means that this operand is both read and written by the instruction.When the compiler fixes up the operands to satisfy the constraints, it needs to know which operands are inputs to the instruction and which are outputs from it.
=' identifies an output;+' identifies an operand that is both input and output; all other
^^^^^^^^^^^^^^^^^^^^^
operands are assumed to be input only.`&'
Means (in a particular alternative) that this operand is an "earlyclobber" operand, which is modified before the instruction is finished using the input operands. Therefore, this operand may not lie in a register that is used as an input operand or as part ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ of any memory address.Quoted 5 lines
So "+" says that this operand is an input but "&" says that it must not be in a register that is used as an input. That's contradictory, and I think we can expect GCC to barf or at least end up doing strange stuff, if not with existing versions, then with future versions.
Quoted 3 lines
I wondered about the same thing: given that the asm itself is a black box to the compiler, it can never reuse an in/output register for output, so when it is clobbered is irrelevant.
Let me try again - you seem to have completely missed my point.
Quoted 8 lines
+ specifies that the operand is an input.
& specifies that the operand is not an input.+ and & are contradictory.
GCC is at liberty to not assign a value to an operand with a +& modifier, or error out such a construction.
I agree that the +& does not make sense.
Quoted 12 lines
Quoted 11 lines
Quoted 5 lines
Hence, I'm asking for clarification why it is thought that the existing code underspecifies the asm constraints, and I'm trying to get some more thought about what the constraints should be, in case there is a need to use "better" constraints.
I think the constraints are correct, but as I argued before, tightening the constraints to ensure that uaddr and newval are not mapped onto the same register should not result in any object code changes, except for the case where the compiler instantiated a constprop clone that is bogus to begin with.
Quoted 4 lines
... by tightening it to an undefined combination of constraint modifiers that just happens to seem to do the right thing. No, this is not proper "engineering". This is bodging.
As I argued above, using an input operand for uaddr is incorrect (in ARM mode) since the instruction does modify the register. So modulo the +&, I think the patch is an improvement.
Russell King - ARM Linux admin
maintainerRe: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 153 lines · Ard Biesheuvel
Quoted 142 lines · Russell King - ARM Linux admin
Quoted 115 lines · Ard Biesheuvel
Quoted 104 lines · Russell King - ARM Linux admin
Quoted 91 lines · Ard Biesheuvel
Quoted 65 lines · Russell King - ARM Linux admin
Quoted 54 lines · Nick Desaulniers
Quoted 41 lines · Arnd Bergmann
Passing registers containing zero as both the address (NULL pointer) and data into
cmpxchg_futex_value_locked()leads clang to assign the same register for both inputs on ARM, which triggers a warning explaining that this instruction has unpredictable behavior on ARMv5.
/tmp/futex-7e740e.s: Assembler messages:/tmp/futex-7e740e.s:12713: Warning: source register same as write-back baseThis patch was suggested by Mikael Pettersson back in 2011 (!) with gcc-4.4, as Mikael wrote:
"One way of fixing this is to make uaddr an input/output register, since "that prevents it from overlapping any other input or output."but then withdrawn as the warning was determined to be harmless, and it apparently never showed up again with later gcc versions.
Now the same problem is back when compiling with clang, and we are trying to get clang to build the kernel without warnings, as gcc normally does.
Cc Mikael Pettersson <[email protected]>Cc Mikael Pettersson <[email protected]>Cc Dave Martin <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/include/asm/futex.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)arch/arm/include/asm/futex.h +2
-2@@ -110,13 +110,13 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr,preempt_disable (); __ua_flags =uaccess_save_and_enable (); __asm__ __volatile__("@futex_atomic_cmpxchg_inatomic\n" - "1: " TUSER(ldr) " %1, [%4]\n" -" teq %1, %2\n" + "1: " TUSER(ldr) " %1, [%2]\n" +" teq %1, %3\n" arch/arm/include/asm/futex.h futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr, · line 121
Quoted 10 lines
arch/arm/include/asm/futex.h +3
-3" it eq @ explicit IT needed for the 2b label\n" - "2: " TUSER(streq) " %3, [%4]\n" + "2: " TUSER(streq) " %4, [%2]\n" __futex_atomic_ex_table("%5" ) - : "+r" (ret), "=&r" (val) - : "r" (oldval), "r" (newval), "r" (uaddr), "Ir" (-EFAULT) + : "+&r" (ret), "=&r" (val), "+&r" (uaddr) + : "r" (oldval), "r" (newval), "Ir" (-EFAULT) : "cc", "memory"); uaccess_restore(__ua_flags);Underspecification of constraints to extended inline assembly is a
Quoted 8 lines
common issue exposed by other compilers (and possibly but in-effect infrequently compiler upgrades).
So the reordering of the constraints means the in the assembly (notes for other reviewers):
%2 -> %3
%3 -> %4
%4 -> %2
Yep, looks good to me, thanks for finding this old patch and resending, Arnd!Quoted 3 lines
I don't see what is "underspecified" in the original constraints. Please explain.
I agree that that statement makes little sense.
As Russell points out in the referenced thread, there is nothing wrong with the generated assembly, given that the UNPREDICTABLE opcode is unreachable in practice. Unfortunately, we have no way to flag this diagnostic as a known false positive, and AFAICT, there is no reason we couldn't end up with the same diagnostic popping up for GCC builds in the future, considering that the register assignment matches the constraints. (We have seen somewhat similar issues where constant folded function clones are emitted with a constant argument that could never occur in reality [0])
Given the above, the only meaningful way to invoke this function is with different registers assigned to %3 and %4, and so tightening the constraints to guarantee that does not actually result in worse code (except maybe for the instantiations that we won't ever call in the first place). So I think we should fix this.
I wonder if just adding
Quoted 8 lines
BUG_ON(__builtin_constant_p(uaddr));
at the beginning makes any difference - this shouldn't result in any object code differences since the conditional will always evaluate to false at build time for instantiations we care about.
What I'm actually asking is:
Quoted 8 lines
The GCC manual says that input operands _may_ overlap output operands since GCC assumes that input operands are consumed before output operands are written. This is an explicit statement.
The GCC manual does not say that input operands may overlap with each other, and the behaviour of GCC thus far (apart from one version, presumably caused by a bug) has been that input operands are unique.
Quoted 5 lines
Not entirely. I have run into issues where GCC assumes that registers that are only used for input operands are left untouched by the asm code. I.e., if you put an
asm()block in a loop and modify an input register, your code may break on the next pass, even if the input register does not overlap with an output register.GCC has had the expectation for decades that _input_ operands are not changed in value by the code in the assembly. This isn't quite the same thing as the uniqueness of the register allocation for input operands.
Quoted 2 lines
To me, that seems to suggest that whether or not inputs may overlap is irrelevant, since they are not expected to be modified.
How is:
stmfd sp!, {r0-r3, ip, lr} bl foo ldmfd sp!, {r0-r3, ip, lr}where r1 may be an input operand (to pass an argument to foo) any different from:
ldrt r0, [r1]Quoted 8 lines
as far as whether r1 is modified in both cases? In both cases, the value of r1 is read and written by both instructions, but in both cases the value of r1 remains the same no matter what the value of r1 was.
The "input operands should not be modified" is entirely orthogonal to the input operand register allocation.
Quoted 8 lines
The question is whether it is reasonable for GCC to use the same register for input operands that have the same value. From the assumption that GCC makes that the asm will not modified follows directly that we can use the same register for different operands.
And in fact, since that asm code (when built in ARM mode) does modify the register, uaddr should not be an input operand to begin with. In other words, there is an actual bug here, and this patch fixes it.
Again, you miss my point.
Quoted 106 lines
Quoted 21 lines
Quoted 14 lines
Quoted 4 lines
Clang appears to be different: it allows input operands that are registers, and contain the same constant value to be the same physical register.
Quoted 9 lines
The assertion is that the constraints are under-specified. I am questioning that assertion.
If the constraints are under-specified, I would have expected gcc-4.4's behaviour to have persisted, and we would've been told by gcc's developers to fix our code. That didn't happen, and instead gcc seems to have been fixed. So, my conclusion is that it is intentional that input operands to
asm()do not overlap with themselves.Quoted 6 lines
Whether we hit the error or not is not deterministic. Like in the
ilog2()case I quoted, GCC may decide to instantiate a constant folded ['curried', if you will] clone of a function, and so even if any calls tofutex_atomic_cmpxchg_inatomic()with constant NULL args for newval and uaddr are compiled, it does not mean they occur like that in the C code.Quoted 8 lines
Again, I think this is different: gcc knows what the C code is doing and can optimise it. GCC doesn't have any idea what the code in an
asm()is doing beyond what the constraints are telling it, and the rules for those constraints set out in the GCC manual.Given that we are explicitly talking about the register allocation for input operands, I'm not sure how the
ilog2()case you mention applies.The relevance of the
ilog2()case is that we are dealing with an invocation of the function that never actually occurs in the code. The compiler emits it as part of an optimization step, and this is how we end up with constant operands for newval and uaddr.Quoted 39 lines
Quoted 33 lines
Quoted 27 lines
It seems to me that the work-around for clang is to change every input operand to be an output operand with a "+&r" contraint - an operand that is both read and written by the "instruction", and that the operand is "earlyclobber". For something that is really only read, that seems strange.
Also, reading GCC's manual, it would appear that "+&" is wrong.
`+'
Means that this operand is both read and written by the instruction.When the compiler fixes up the operands to satisfy the constraints, it needs to know which operands are inputs to the instruction and which are outputs from it.
=' identifies an output;+' identifies an operand that is both input and output; all other
^^^^^^^^^^^^^^^^^^^^^
operands are assumed to be input only.`&'
Means (in a particular alternative) that this operand is an "earlyclobber" operand, which is modified before the instruction is finished using the input operands. Therefore, this operand may not lie in a register that is used as an input operand or as part ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ of any memory address.Quoted 5 lines
So "+" says that this operand is an input but "&" says that it must not be in a register that is used as an input. That's contradictory, and I think we can expect GCC to barf or at least end up doing strange stuff, if not with existing versions, then with future versions.
Quoted 3 lines
I wondered about the same thing: given that the asm itself is a black box to the compiler, it can never reuse an in/output register for output, so when it is clobbered is irrelevant.
Let me try again - you seem to have completely missed my point.
Quoted 8 lines
+ specifies that the operand is an input.
& specifies that the operand is not an input.+ and & are contradictory.
GCC is at liberty to not assign a value to an operand with a +& modifier, or error out such a construction.
I agree that the +& does not make sense.
Quoted 12 lines
Quoted 11 lines
Quoted 5 lines
Hence, I'm asking for clarification why it is thought that the existing code underspecifies the asm constraints, and I'm trying to get some more thought about what the constraints should be, in case there is a need to use "better" constraints.
I think the constraints are correct, but as I argued before, tightening the constraints to ensure that uaddr and newval are not mapped onto the same register should not result in any object code changes, except for the case where the compiler instantiated a constprop clone that is bogus to begin with.
Quoted 4 lines
... by tightening it to an undefined combination of constraint modifiers that just happens to seem to do the right thing. No, this is not proper "engineering". This is bodging.
As I argued above, using an input operand for uaddr is incorrect (in ARM mode) since the instruction does modify the register. So modulo the +&, I think the patch is an improvement.
Signature · 3 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up
Re: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 160 lines · Russell King - ARM Linux admin
Quoted 158 lines · Ard Biesheuvel
Quoted 142 lines · Russell King - ARM Linux admin
Quoted 115 lines · Ard Biesheuvel
Quoted 104 lines · Russell King - ARM Linux admin
Quoted 91 lines · Ard Biesheuvel
Quoted 65 lines · Russell King - ARM Linux admin
Quoted 54 lines · Nick Desaulniers
Quoted 41 lines · Arnd Bergmann
Passing registers containing zero as both the address (NULL pointer) and data into
cmpxchg_futex_value_locked()leads clang to assign the same register for both inputs on ARM, which triggers a warning explaining that this instruction has unpredictable behavior on ARMv5.
/tmp/futex-7e740e.s: Assembler messages:/tmp/futex-7e740e.s:12713: Warning: source register same as write-back baseThis patch was suggested by Mikael Pettersson back in 2011 (!) with gcc-4.4, as Mikael wrote:
"One way of fixing this is to make uaddr an input/output register, since "that prevents it from overlapping any other input or output."but then withdrawn as the warning was determined to be harmless, and it apparently never showed up again with later gcc versions.
Now the same problem is back when compiling with clang, and we are trying to get clang to build the kernel without warnings, as gcc normally does.
Cc Mikael Pettersson <[email protected]>Cc Mikael Pettersson <[email protected]>Cc Dave Martin <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/include/asm/futex.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)arch/arm/include/asm/futex.h +2
-2@@ -110,13 +110,13 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr,preempt_disable (); __ua_flags =uaccess_save_and_enable (); __asm__ __volatile__("@futex_atomic_cmpxchg_inatomic\n" - "1: " TUSER(ldr) " %1, [%4]\n" -" teq %1, %2\n" + "1: " TUSER(ldr) " %1, [%2]\n" +" teq %1, %3\n" arch/arm/include/asm/futex.h futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr, · line 121
Quoted 10 lines
arch/arm/include/asm/futex.h +3
-3" it eq @ explicit IT needed for the 2b label\n" - "2: " TUSER(streq) " %3, [%4]\n" + "2: " TUSER(streq) " %4, [%2]\n" __futex_atomic_ex_table("%5" ) - : "+r" (ret), "=&r" (val) - : "r" (oldval), "r" (newval), "r" (uaddr), "Ir" (-EFAULT) + : "+&r" (ret), "=&r" (val), "+&r" (uaddr) + : "r" (oldval), "r" (newval), "Ir" (-EFAULT) : "cc", "memory"); uaccess_restore(__ua_flags);Underspecification of constraints to extended inline assembly is a
Quoted 8 lines
common issue exposed by other compilers (and possibly but in-effect infrequently compiler upgrades).
So the reordering of the constraints means the in the assembly (notes for other reviewers):
%2 -> %3
%3 -> %4
%4 -> %2
Yep, looks good to me, thanks for finding this old patch and resending, Arnd!Quoted 3 lines
I don't see what is "underspecified" in the original constraints. Please explain.
I agree that that statement makes little sense.
As Russell points out in the referenced thread, there is nothing wrong with the generated assembly, given that the UNPREDICTABLE opcode is unreachable in practice. Unfortunately, we have no way to flag this diagnostic as a known false positive, and AFAICT, there is no reason we couldn't end up with the same diagnostic popping up for GCC builds in the future, considering that the register assignment matches the constraints. (We have seen somewhat similar issues where constant folded function clones are emitted with a constant argument that could never occur in reality [0])
Given the above, the only meaningful way to invoke this function is with different registers assigned to %3 and %4, and so tightening the constraints to guarantee that does not actually result in worse code (except maybe for the instantiations that we won't ever call in the first place). So I think we should fix this.
I wonder if just adding
Quoted 8 lines
BUG_ON(__builtin_constant_p(uaddr));
at the beginning makes any difference - this shouldn't result in any object code differences since the conditional will always evaluate to false at build time for instantiations we care about.
What I'm actually asking is:
Quoted 8 lines
The GCC manual says that input operands _may_ overlap output operands since GCC assumes that input operands are consumed before output operands are written. This is an explicit statement.
The GCC manual does not say that input operands may overlap with each other, and the behaviour of GCC thus far (apart from one version, presumably caused by a bug) has been that input operands are unique.
Quoted 5 lines
Not entirely. I have run into issues where GCC assumes that registers that are only used for input operands are left untouched by the asm code. I.e., if you put an
asm()block in a loop and modify an input register, your code may break on the next pass, even if the input register does not overlap with an output register.GCC has had the expectation for decades that _input_ operands are not changed in value by the code in the assembly. This isn't quite the same thing as the uniqueness of the register allocation for input operands.
Quoted 2 lines
To me, that seems to suggest that whether or not inputs may overlap is irrelevant, since they are not expected to be modified.
How is:
stmfd sp!, {r0-r3, ip, lr} bl foo ldmfd sp!, {r0-r3, ip, lr}where r1 may be an input operand (to pass an argument to foo) any different from:
ldrt r0, [r1]Quoted 8 lines
as far as whether r1 is modified in both cases? In both cases, the value of r1 is read and written by both instructions, but in both cases the value of r1 remains the same no matter what the value of r1 was.
The "input operands should not be modified" is entirely orthogonal to the input operand register allocation.
The question is whether it is reasonable for GCC to use the same register for input operands that have the same value. From the assumption that GCC makes that the asm will not modified follows directly that we can use the same register for different operands.
Quoted 6 lines
Quoted 3 lines
And in fact, since that asm code (when built in ARM mode) does modify the register, uaddr should not be an input operand to begin with. In other words, there is an actual bug here, and this patch fixes it.
Again, you miss my point.
Perhaps. So let me summarize what I do understand.
1) if futex_atomic_cmpxchg_inatomic() is instantiated *and executed* with the same compile time constant value of 0x0 for newval and uaddr, we end up with an opcode for the STRT instruction that is CONSTRAINED UNPREDICTABLE, but we will never execute it since the preceding load will fault and enter the fixup handler.
2) such occurrences of futex_atomic_cmpxchg_inatomic() are unlikely to occur in the code, but may be instantiated by the compiler when doing constant propagation (like in the ilog2() case I quoted), but these instantiations will never be called
3) both clang and gcc may map different inline asm input operands onto the same register if the value is guaranteed to be the same (i.e., they are both compile time constants)
My statement about uaddr was slightly misguided, in the sense that our invocation of STRT does use the post-index variant, but with an increment of zero, so the value written back to the register equals the original value. But it does explain why this opcode is CONSTRAINED UNPREDICTABLE in the first place.
Given 2) above, I wonder if anyone could confirm whether adding 'BUG_ON(__builtin_constant_p(uaddr))' silences the warning as well.
Re: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 19 lines · Ard Biesheuvel
Quoted 1 line · Russell King - ARM Linux admin
On Fri, Mar 08, 2019 at 11:45:21AM +0100, Ard Biesheuvel wrote:
Perhaps. So let me summarize what I do understand.
1) if
futex_atomic_cmpxchg_inatomic()is instantiated *and executed* with the same compile time constant value of0x0for newval and uaddr, we end up with an opcode for the STRT instruction that is CONSTRAINED UNPREDICTABLE, but we will never execute it since the preceding load will fault and enter the fixup handler.
2) such occurrences offutex_atomic_cmpxchg_inatomic()are unlikely to occur in the code, but may be instantiated by the compiler when doing constant propagation (like in theilog2()case I quoted), but these instantiations will never be called
3) both clang and gcc may map different inline asm input operands onto the same register if the value is guaranteed to be the same (i.e., they are both compile time constants)
Quoted 8 lines
My statement about uaddr was slightly misguided, in the sense that our invocation of STRT does use the post-index variant, but with an increment of zero, so the value written back to the register equals the original value. But it does explain why this opcode is CONSTRAINED UNPREDICTABLE in the first place.
Given 2) above, I wonder if anyone could confirm whether adding 'BUG_ON(__builtin_constant_p(uaddr))' silences the warning as well.
Like this?
arch/arm/include/asm/futex.h +1 -0
@@ -57,6 +57,7 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr,/* Prefetching cannot fault */ prefetchw (uaddr); __ua_flags =uaccess_save_and_enable (); +BUG_ON (__builtin_constant_p (uaddr) || !uaddr); __asm__ __volatile__("@futex_atomic_cmpxchg_inatomic\n" "1: ldrex %1, [%4]\n" " teq %1, %2\n"
This had no effect here.
My first attempt (before finding the original patch from Mikael Pettersson) was to change the probe to pass '1' as the value instead of '0', that worked fine.
Arnd
Re: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 46 lines · Arnd Bergmann
Quoted 19 lines · Ard Biesheuvel
Quoted 1 line · Russell King - ARM Linux admin
On Fri, Mar 08, 2019 at 11:45:21AM +0100, Ard Biesheuvel wrote:
Perhaps. So let me summarize what I do understand.
1) if
futex_atomic_cmpxchg_inatomic()is instantiated *and executed* with the same compile time constant value of0x0for newval and uaddr, we end up with an opcode for the STRT instruction that is CONSTRAINED UNPREDICTABLE, but we will never execute it since the preceding load will fault and enter the fixup handler.
2) such occurrences offutex_atomic_cmpxchg_inatomic()are unlikely to occur in the code, but may be instantiated by the compiler when doing constant propagation (like in theilog2()case I quoted), but these instantiations will never be called
3) both clang and gcc may map different inline asm input operands onto the same register if the value is guaranteed to be the same (i.e., they are both compile time constants)Quoted 8 lines
My statement about uaddr was slightly misguided, in the sense that our invocation of STRT does use the post-index variant, but with an increment of zero, so the value written back to the register equals the original value. But it does explain why this opcode is CONSTRAINED UNPREDICTABLE in the first place.
Given 2) above, I wonder if anyone could confirm whether adding 'BUG_ON(__builtin_constant_p(uaddr))' silences the warning as well.
Like this?
arch/arm/include/asm/futex.h +1
-0@@ -57,6 +57,7 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr,/* Prefetching cannot fault */ prefetchw (uaddr); __ua_flags =uaccess_save_and_enable (); +BUG_ON (__builtin_constant_p (uaddr) || !uaddr); __asm__ __volatile__("@futex_atomic_cmpxchg_inatomic\n" "1: ldrex %1, [%4]\n" " teq %1, %2\n"
Quoted 6 lines
This had no effect here.
My first attempt (before finding the original patch from Mikael Pettersson) was to change the probe to pass '1' as the value instead of '0', that worked fine.
Which probe is that?
Re: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 4 lines · Ard Biesheuvel
Quoted 3 lines · Arnd Bergmann
Quoted 1 line · Ard Biesheuvel
On Fri, 8 Mar 2019 at 11:58, Russell King - ARM Linux admin <[email protected]> wrote:
Quoted 8 lines
Quoted 6 lines
Quoted 1 line
Quoted 1 line · Ard Biesheuvel
My first attempt (before finding the original patch from Mikael Pettersson) was to change the probe to pass '1' as the value instead of '0', that worked fine.
Which probe is that?
kernel/futex.c +1 -1
@@ -3864,7 +3864,7 @@ static void __init futex_detect_cmpxchg(void)* implementation, the non-functional ones will return * -ENOSYS. */ -if (cmpxchg_futex_value_locked (&curval,NULL ,0 ,0 ) == -EFAULT ) +if (cmpxchg_futex_value_locked (&curval,NULL ,1 ,1 ) == -EFAULT ) futex_cmpxchg_enabled =1 ;#endif }
Arnd
Re: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 22 lines · Arnd Bergmann
Quoted 12 lines · Ard Biesheuvel
Quoted 9 lines · Arnd Bergmann
Quoted 2 lines · Ard Biesheuvel
Quoted 1 line · Russell King - ARM Linux admin
On Fri, Mar 08, 2019 at 11:45:21AM +0100, Ard Biesheuvel wrote:
My first attempt (before finding the original patch from Mikael Pettersson) was to change the probe to pass '1' as the value instead of '0', that worked fine.
Which probe is that?
kernel/futex.c +0
-0
kernel/futex.c static void __init futex_detect_cmpxchg(void) · line 3870
Quoted 8 lines
kernel/futex.c +1
-1@@ -3864,7 +3864,7 @@ static void __init futex_detect_cmpxchg(void)* implementation, the non-functional ones will return * -ENOSYS. */ -if (cmpxchg_futex_value_locked (&curval,NULL ,0 ,0 ) == -EFAULT ) +if (cmpxchg_futex_value_locked (&curval,NULL ,1 ,1 ) == -EFAULT ) futex_cmpxchg_enabled =1 ;#endif }
Ah ok.
That explains a lot.
Can't we just return -EFAULT if uaddr is NULL? Or does that defeat this check?
Note that PA-RISC has
/* futex.c wants to do a cmpxchg_inatomic on kernel NULL, which is
* our gateway page, and causes no end of trouble...
*/
if (uaccess_kernel() && !uaddr)
return -EFAULT;Re: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
Quoted 35 lines · Ard Biesheuvel
Quoted 22 lines · Arnd Bergmann
Quoted 12 lines · Ard Biesheuvel
Quoted 9 lines · Arnd Bergmann
Quoted 2 lines · Ard Biesheuvel
Quoted 1 line · Russell King - ARM Linux admin
On Fri, Mar 08, 2019 at 11:45:21AM +0100, Ard Biesheuvel wrote:
My first attempt (before finding the original patch from Mikael Pettersson) was to change the probe to pass '1' as the value instead of '0', that worked fine.
Which probe is that?
kernel/futex.c +0
-0kernel/futex.c static void __init futex_detect_cmpxchg(void) · line 3870
Quoted 8 lines
kernel/futex.c +1
-1@@ -3864,7 +3864,7 @@ static void __init futex_detect_cmpxchg(void)* implementation, the non-functional ones will return * -ENOSYS. */ -if (cmpxchg_futex_value_locked (&curval,NULL ,0 ,0 ) == -EFAULT ) +if (cmpxchg_futex_value_locked (&curval,NULL ,1 ,1 ) == -EFAULT ) futex_cmpxchg_enabled =1 ;#endif }Ah ok.
Quoted 3 lines
That explains a lot.
Can't we just return
-EFAULTif uaddr is NULL? Or does that defeat this check?
I think that would work here, it would just create a tiny overhead for each call to futex_atomic_cmpxchg_inatomic().
Semi-related side note:
After I looked at access_ok() for a bit too long, I tried replacing it with
#define access_ok(addr, size) \
(((u64)(uintptr_t)addr + (u64)(size_t)size) >=current_thread_info()->addr_limit)
which interestingly seemed to improve the output with clang (it lets it combine multiple access_ok() checks and schedule the instructions better, compared to our inline asm implementation), but it unfortunately creates horrible code with gcc.
Arnd
Re: [PATCH 2/2] ARM: futex: make futex_detect_cmpxchg more reliable
In reply to Ard BiesheuvelQuoted 149 lines · Ard Biesheuvel
Quoted 147 lines · Russell King - ARM Linux admin
Quoted 115 lines · Ard Biesheuvel
Quoted 104 lines · Russell King - ARM Linux admin
Quoted 91 lines · Ard Biesheuvel
Quoted 65 lines · Russell King - ARM Linux admin
Quoted 54 lines · Nick Desaulniers
Quoted 41 lines · Arnd Bergmann
Passing registers containing zero as both the address (NULL pointer) and data into
cmpxchg_futex_value_locked()leads clang to assign the same register for both inputs on ARM, which triggers a warning explaining that this instruction has unpredictable behavior on ARMv5.
/tmp/futex-7e740e.s: Assembler messages:/tmp/futex-7e740e.s:12713: Warning: source register same as write-back baseThis patch was suggested by Mikael Pettersson back in 2011 (!) with gcc-4.4, as Mikael wrote:
"One way of fixing this is to make uaddr an input/output register, since "that prevents it from overlapping any other input or output."but then withdrawn as the warning was determined to be harmless, and it apparently never showed up again with later gcc versions.
Now the same problem is back when compiling with clang, and we are trying to get clang to build the kernel without warnings, as gcc normally does.
Cc Mikael Pettersson <[email protected]>Cc Mikael Pettersson <[email protected]>Cc Dave Martin <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>--- arch/arm/include/asm/futex.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)arch/arm/include/asm/futex.h +2
-2@@ -110,13 +110,13 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr,preempt_disable (); __ua_flags =uaccess_save_and_enable (); __asm__ __volatile__("@futex_atomic_cmpxchg_inatomic\n" - "1: " TUSER(ldr) " %1, [%4]\n" -" teq %1, %2\n" + "1: " TUSER(ldr) " %1, [%2]\n" +" teq %1, %3\n" arch/arm/include/asm/futex.h futex_atomic_cmpxchg_inatomic(u32 *uval, u32 __user *uaddr, · line 121
Quoted 10 lines
arch/arm/include/asm/futex.h +3
-3" it eq @ explicit IT needed for the 2b label\n" - "2: " TUSER(streq) " %3, [%4]\n" + "2: " TUSER(streq) " %4, [%2]\n" __futex_atomic_ex_table("%5" ) - : "+r" (ret), "=&r" (val) - : "r" (oldval), "r" (newval), "r" (uaddr), "Ir" (-EFAULT) + : "+&r" (ret), "=&r" (val), "+&r" (uaddr) + : "r" (oldval), "r" (newval), "Ir" (-EFAULT) : "cc", "memory"); uaccess_restore(__ua_flags);Underspecification of constraints to extended inline assembly is a
Quoted 8 lines
common issue exposed by other compilers (and possibly but in-effect infrequently compiler upgrades).
So the reordering of the constraints means the in the assembly (notes for other reviewers):
%2 -> %3
%3 -> %4
%4 -> %2
Yep, looks good to me, thanks for finding this old patch and resending, Arnd!Quoted 3 lines
I don't see what is "underspecified" in the original constraints. Please explain.
I agree that that statement makes little sense.
As Russell points out in the referenced thread, there is nothing wrong with the generated assembly, given that the UNPREDICTABLE opcode is unreachable in practice. Unfortunately, we have no way to flag this diagnostic as a known false positive, and AFAICT, there is no reason we couldn't end up with the same diagnostic popping up for GCC builds in the future, considering that the register assignment matches the constraints. (We have seen somewhat similar issues where constant folded function clones are emitted with a constant argument that could never occur in reality [0])
Given the above, the only meaningful way to invoke this function is with different registers assigned to %3 and %4, and so tightening the constraints to guarantee that does not actually result in worse code (except maybe for the instantiations that we won't ever call in the first place). So I think we should fix this.
I wonder if just adding
Quoted 8 lines
BUG_ON(__builtin_constant_p(uaddr));
at the beginning makes any difference - this shouldn't result in any object code differences since the conditional will always evaluate to false at build time for instantiations we care about.
What I'm actually asking is:
Quoted 8 lines
The GCC manual says that input operands _may_ overlap output operands since GCC assumes that input operands are consumed before output operands are written. This is an explicit statement.
The GCC manual does not say that input operands may overlap with each other, and the behaviour of GCC thus far (apart from one version, presumably caused by a bug) has been that input operands are unique.
Quoted 5 lines
Not entirely. I have run into issues where GCC assumes that registers that are only used for input operands are left untouched by the asm code. I.e., if you put an
asm()block in a loop and modify an input register, your code may break on the next pass, even if the input register does not overlap with an output register.GCC has had the expectation for decades that _input_ operands are not changed in value by the code in the assembly. This isn't quite the same thing as the uniqueness of the register allocation for input operands.
Quoted 2 lines
To me, that seems to suggest that whether or not inputs may overlap is irrelevant, since they are not expected to be modified.
How is:
stmfd sp!, {r0-r3, ip, lr} bl foo ldmfd sp!, {r0-r3, ip, lr}where r1 may be an input operand (to pass an argument to foo) any different from:
ldrt r0, [r1]as far as whether r1 is modified in both cases? In both cases, the value of r1 is read and written by both instructions, but in both cases the value of r1 remains the same no matter what the value of r1 was.
Quoted 8 lines
Quoted 3 lines
The "input operands should not be modified" is entirely orthogonal to the input operand register allocation.
The question is whether it is reasonable for GCC to use the same register for input operands that have the same value. From the assumption that GCC makes that the asm will not modified follows directly that we can use the same register for different operands.
Whether "reasonable" or not, GCC does it. And I don't think this is new behaviour...
int f(void)
{
int res;
asm ("ADD %0, %0, %0" : "=r" (res) : "r" (77), "r" (77));
return res;
}->
00000000 <f>:
0: e3a0004d mov r0, #77 ; 0x4d 4: e0800000 add r0, r0, r0 8: e12fff1e bx lr
Quoted 3 lines
And in fact, since that asm code (when built in ARM mode) does modify the register, uaddr should not be an input operand to begin with. In other words, there is an actual bug here, and this patch fixes it.
Does the old code modify the register?
As I read it, the register is written (in the ARM case) by the underlying STRT instruction, but since the post-index offset it 0, the value written back is the same as the value originally read.
In ARMv7-A,
strt r0, [r0], #imm
will store the original (unmodified) value of r0 if I read the pseudocode correctly. I can't remember the history, but I think that older architecture versions provided a choice about whether the unmodified or modified value was stored. So gas probably just checks whether the registers are the same and emits a warning to be on the safe side. If #imm is 0 (as in the existing futex code here) then it may make no difference in practice though.
So, I'm not absolutely convinced there's a bug here, unless this is truly specified as UNPREDICATABLE in older arch versions.
But the warning it at least annoying and use of "&" to prevent gas allocating things to the same register is already widespread for "+" asm arguments, even for arm.
If the _value_ of the affected operand is not changed by the asm, I think we don't strictly need "+", but we are using "&" here for its register allocation side-effects, and "&" (for its original purpose at least) is only applicable to output ("=" or "+") operands.
So I think the patch probably makes sense.
IMHO the gas documentation is misleading (or at least unhelpful).
Cheers
---Dave
Quoted 11 lines · Arnd Bergmann
On 32-bit ARM, I got a link failure in
futex_init()when building with clang in some random configurations:kernel/futex.o:(.text.fixup+0x5c): relocation truncated to fit:
R_ARM_JUMP24against `.init.text'As far as I can tell, the problem is that a branch is over 16MB apart in those configurations, but only if it branches back to the init text.
Marking the
futex_detect_cmpxchg()function as noinline and not__initavoids the problem for me.
Perhaps the __init and __exit #defines should be noinline to allow discarding of the code.
These defines are already marked with __section so I'd've expected these to be noinline anyway.
--- include/linux/init.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
include/linux/init.h +2 -2
@@ -47,7 +47,7 @@/* These are for everybody (although not all archs will actually discard it in modules) */ -#define __init __section(.init.text) __cold __latent_entropy __noinitretpoline +#define __init __section(.init.text) __cold __latent_entropy __noinitretpoline noinline#define __initdata __section(.init.data)#define __initconst __section(.init.rodata)#define __exitdata __section(.exit.data)
@@ -80,7 +80,7 @@#define __exitused __used#endif -#define __exit __section(.exit.text) __exitused __cold notrace +#define __exit __section(.exit.text) __exitused __cold notrace noinline/* Used for MEMORY_HOTPLUG */ #define __meminit __section(.meminit.text) __cold notrace \
Russell King - ARM Linux admin
maintainerQuoted 10 lines · Joe Perches
Quoted 9 lines · Arnd Bergmann
On 32-bit ARM, I got a link failure in
futex_init()when building with clang in some random configurations:kernel/futex.o:(.text.fixup+0x5c): relocation truncated to fit:
R_ARM_JUMP24against `.init.text'As far as I can tell, the problem is that a branch is over 16MB apart in those configurations, but only if it branches back to the init text.
Quoted 5 lines
Quoted 2 lines
Marking the
futex_detect_cmpxchg()function as noinline and not__initavoids the problem for me.Perhaps the
__initand__exit#defines should be noinline to allow discarding of the code.
How does that help this case? The problem is futex_detect_cmpxchg() being placed in .init.text which is too far from .text.fixup. Whether it is inlined or not is immaterial since both futex_detect_cmpxchg() and its only caller futex_init() are both __init functions.
It seems to me to be completely sane to have:
static void __init foo(...)
{
}
static int __init foo_init(...)
{
foo();
}and have the expectation that the compiler _can_, if it desires, inline foo() into foo_init().
Let me re-iterate: the inlining of futex_detect_cmpxchg() into futex_init() is not the issue here.
Signature · 3 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up
Quoted 11 lines · Russell King - ARM Linux admin
Quoted 10 lines · Joe Perches
Quoted 9 lines · Arnd Bergmann
On 32-bit ARM, I got a link failure in
futex_init()when building with clang in some random configurations:kernel/futex.o:(.text.fixup+0x5c): relocation truncated to fit:
R_ARM_JUMP24against `.init.text'As far as I can tell, the problem is that a branch is over 16MB apart in those configurations, but only if it branches back to the init text.
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
Marking the
futex_detect_cmpxchg()function as noinline and not__initavoids the problem for me.Perhaps the
__initand__exit#defines should be noinline to allow discarding of the code.How does that help this case?
It doesn't particularly.
It does help any other case that might arise.
Quoted 6 lines
It seems to me to be completely sane to have:
static void
__initfoo(...)
{
}
Quoted 7 lines
static int
__initfoo_init(...){ foo(); }and have the expectation that the compiler _can_, if it desires, inline
foo()intofoo_init().
True, but init function performance requirements are generally trivial and isolating the possibility of defects like this seems a reasonable trade-off to me.
Russell King - ARM Linux admin
maintainerQuoted 15 lines · Joe Perches
Quoted 14 lines · Russell King - ARM Linux admin
Quoted 13 lines · Joe Perches
Quoted 11 lines · Arnd Bergmann
On 32-bit ARM, I got a link failure in
futex_init()when building with clang in some random configurations:kernel/futex.o:(.text.fixup+0x5c): relocation truncated to fit:
R_ARM_JUMP24against `.init.text'As far as I can tell, the problem is that a branch is over 16MB apart in those configurations, but only if it branches back to the init text.
Marking the
futex_detect_cmpxchg()function as noinline and not__initavoids the problem for me.
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
Perhaps the
__initand__exit#defines should be noinline to allow discarding of the code.How does that help this case?
It doesn't particularly.
It does help any other case that might arise.
Please describe what "any other case" you are thinking of - as already stated, your patch would have no beneficial effect for the observed issue.
In fact, it _could_ do exactly the opposite. Where functions can be inlined, they may become smaller due to no need for function prologue and epilogue, and other optimisations. Forcing the compiler to avoid inlining them could result in larger code, which means a higher chance of triggering the "relocation truncated to fit" problem.
The converse is also a possibility too - it all depends on the inlining behaviour of the compiler towards static functions, and the resulting size of the code.
What may be right for one architecture and compiler may not be right for another.
Signature · 3 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up
Quoted 5 lines · Arnd Bergmann
On 32-bit ARM, I got a link failure in
futex_init()when building with clang in some random configurations:kernel/futex.o:(.text.fixup+0x5c): relocation truncated to fit:
R_ARM_JUMP24against `.init.text'
Do we know what function from the fixup text section is calling futex_detect_cmpxchg? I'm curious if this is maybe another case of -Wsection where some function may be in the wrong section?
Quoted 29 lines
As far as I can tell, the problem is that a branch is over 16MB apart in those configurations, but only if it branches back to the init text.
Marking the
futex_detect_cmpxchg()function as noinline and not__initavoids the problem for me.Signed-off-by Arnd Bergmann <[email protected]>--- kernel/futex.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)kernel/futex.c +1
-2@@ -3849,7 +3849,7 @@ SYSCALL_DEFINE6(futex_time32, u32 __user *, uaddr, int, op, u32, val, }#endif /* CONFIG_COMPAT_32BIT_TIME */ -static void __init futex_detect_cmpxchg (void ) +static noinline void futex_detect_cmpxchg(void) {#ifndef CONFIG_HAVE_FUTEX_CMPXCHG u32 curval; --2.20.0
Signature · 2 lines
Thanks, ~Nick Desaulniers
Quoted 11 lines · Nick Desaulniers
Quoted 5 lines · Arnd Bergmann
On 32-bit ARM, I got a link failure in
futex_init()when building with clang in some random configurations:kernel/futex.o:(.text.fixup+0x5c): relocation truncated to fit:
R_ARM_JUMP24against `.init.text'Do we know what function from the fixup text section is calling
futex_detect_cmpxchg? I'm curious if this is maybe another case of -Wsection where some function may be in the wrong section?
Looks like this is the call stack:
futex_init ->
futex_detect_cmpxchg ->
cmpxchg_futex_value_locked ->
futex_atomic_cmpxchg_inatomicThis is the same issue I reported: https://github.com/ClangBuiltLinux/linux/issues/325
Marking arm's futex_atomic_cmpxchg_inatomic as noinline also fixes this so maybe that's it?
Cheers,
Nathan
Quoted 34 lines
Quoted 29 lines
As far as I can tell, the problem is that a branch is over 16MB apart in those configurations, but only if it branches back to the init text.
Marking the
futex_detect_cmpxchg()function as noinline and not__initavoids the problem for me.Signed-off-by Arnd Bergmann <[email protected]>--- kernel/futex.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)kernel/futex.c +1
-2@@ -3849,7 +3849,7 @@ SYSCALL_DEFINE6(futex_time32, u32 __user *, uaddr, int, op, u32, val, }#endif /* CONFIG_COMPAT_32BIT_TIME */ -static void __init futex_detect_cmpxchg (void ) +static noinline void futex_detect_cmpxchg(void) {#ifndef CONFIG_HAVE_FUTEX_CMPXCHG u32 curval; --2.20.0
Signature · 2 lines
Thanks, ~Nick Desaulniers
Quoted 17 lines · Nathan Chancellor
Quoted 11 lines · Nick Desaulniers
Quoted 5 lines · Arnd Bergmann
On 32-bit ARM, I got a link failure in
futex_init()when building with clang in some random configurations:kernel/futex.o:(.text.fixup+0x5c): relocation truncated to fit:
R_ARM_JUMP24against `.init.text'Do we know what function from the fixup text section is calling
futex_detect_cmpxchg? I'm curious if this is maybe another case of -Wsection where some function may be in the wrong section?Looks like this is the call stack:
futex_init->
Quoted 8 lines
futex_detect_cmpxchg -> cmpxchg_futex_value_locked -> futex_atomic_cmpxchg_inatomicThis is the same issue I reported: https://github.com/ClangBuiltLinux/linux/issues/325
Marking arm's
futex_atomic_cmpxchg_inatomicas noinline also fixes this so maybe that's it?
I think part of the problem is the linker sometimes failing to generate veneers for long calls. I've seen this in the past with relocations in non-executable sections, but it's possible that the problem here is having a relocation to a section that doesn't start with ".text".
I have not analyzed the linker behavior in more detail, but have experimentally shown that the problem doesn't happen if the relocation is from the .text.fixup segment to .text rather than .init.text. It's also possible that this is simply a result of the relative distance of the locations in memory as Russell said, so it could come back if the kernel grows further.
Arnd
Quoted 22 lines · Arnd Bergmann
On 32-bit ARM, I got a link failure in
futex_init()when building with clang in some random configurations:kernel/futex.o:(.text.fixup+0x5c): relocation truncated to fit:
R_ARM_JUMP24against `.init.text'As far as I can tell, the problem is that a branch is over 16MB apart in those configurations, but only if it branches back to the init text.
Marking the
futex_detect_cmpxchg()function as noinline and not__initavoids the problem for me.Signed-off-by Arnd Bergmann <[email protected]>--- kernel/futex.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)kernel/futex.c +0
-0
kernel/futex.c SYSCALL_DEFINE6(futex_time32, u32 __user *, uaddr, int, op, u32, val, · line 3855
Quoted 8 lines
kernel/futex.c +1
-1@@ -3849,7 +3849,7 @@ SYSCALL_DEFINE6(futex_time32, u32 __user *, uaddr, int, op, u32, val, }#endif /* CONFIG_COMPAT_32BIT_TIME */ -static void __init futex_detect_cmpxchg (void ) +static noinline void futex_detect_cmpxchg(void) {#ifndef CONFIG_HAVE_FUTEX_CMPXCHG u32 curval;
What ever happened to this patch?
I'm seeing this again with the attached config + next-20201211 (for testing https://bugs.llvm.org/show_bug.cgi?id=48492). Had to apply this patch to build the kernel.
Thanks,
-- Marco
#
# Automatically generated file; DO NOT EDIT.
# Linux/arm 5.10.0-rc7 Kernel Configuration
#CONFIG_CC_VERSION_TEXT="clang version 11.0.1 (https://github.com/llvm/llvm-project.git 3ac2d963bca4851cf8fb97341f6bd542460e6d7a)" CONFIG_GCC_VERSION=0CONFIG_LD_VERSION=235010000CONFIG_CC_IS_CLANG=yCONFIG_CLANG_VERSION=110001CONFIG_LLD_VERSION=0CONFIG_CC_HAS_ASM_GOTO=yCONFIG_CC_HAS_ASM_GOTO_OUTPUT=yCONFIG_CC_HAS_ASM_INLINE=yCONFIG_CONSTRUCTORS=yCONFIG_IRQ_WORK=yCONFIG_BUILDTIME_TABLE_SORT=y
#
# General setup
#CONFIG_INIT_ENV_ARG_LIMIT=32
# CONFIG_COMPILE_TEST is not setCONFIG_LOCALVERSION=""CONFIG_LOCALVERSION_AUTO=yCONFIG_BUILD_SALT=""CONFIG_HAVE_KERNEL_GZIP=yCONFIG_HAVE_KERNEL_LZMA=yCONFIG_HAVE_KERNEL_XZ=yCONFIG_HAVE_KERNEL_LZO=yCONFIG_HAVE_KERNEL_LZ4=yCONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not setCONFIG_DEFAULT_INIT=""CONFIG_DEFAULT_HOSTNAME="(none)"CONFIG_SWAP=yCONFIG_SYSVIPC=yCONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_WATCH_QUEUE is not setCONFIG_CROSS_MEMORY_ATTACH=y
# CONFIG_USELIB is not set
# CONFIG_AUDIT is not setCONFIG_HAVE_ARCH_AUDITSYSCALL=y
#
# IRQ subsystem
#CONFIG_GENERIC_IRQ_PROBE=yCONFIG_GENERIC_IRQ_SHOW=yCONFIG_GENERIC_IRQ_SHOW_LEVEL=yCONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK=yCONFIG_GENERIC_IRQ_MIGRATION=yCONFIG_HARDIRQS_SW_RESEND=yCONFIG_GENERIC_IRQ_CHIP=yCONFIG_IRQ_DOMAIN=yCONFIG_IRQ_DOMAIN_HIERARCHY=yCONFIG_GENERIC_IRQ_IPI=yCONFIG_GENERIC_MSI_IRQ=yCONFIG_GENERIC_MSI_IRQ_DOMAIN=yCONFIG_HANDLE_DOMAIN_IRQ=yCONFIG_IRQ_FORCED_THREADING=yCONFIG_SPARSE_IRQ=y
# CONFIG_GENERIC_IRQ_DEBUGFS is not set
# end of IRQ subsystem
CONFIG_GENERIC_IRQ_MULTI_HANDLER=yCONFIG_GENERIC_TIME_VSYSCALL=yCONFIG_GENERIC_CLOCKEVENTS=yCONFIG_ARCH_HAS_TICK_BROADCAST=yCONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
#
# Timers subsystem
#CONFIG_TICK_ONESHOT=yCONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not setCONFIG_NO_HZ_IDLE=y
# CONFIG_NO_HZ_FULL is not setCONFIG_NO_HZ=yCONFIG_HIGH_RES_TIMERS=y
# end of Timers subsystem
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not setCONFIG_PREEMPT=yCONFIG_PREEMPTION=y
#
# CPU/Task time and stats accounting
#CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
# CONFIG_IRQ_TIME_ACCOUNTING is not setCONFIG_SCHED_THERMAL_PRESSURE=y
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_PSI is not set
# end of CPU/Task time and stats accounting
CONFIG_CPU_ISOLATION=y
#
# RCU Subsystem
#CONFIG_TREE_RCU=yCONFIG_PREEMPT_RCU=y
# CONFIG_RCU_EXPERT is not setCONFIG_SRCU=yCONFIG_TREE_SRCU=yCONFIG_TASKS_RCU_GENERIC=yCONFIG_TASKS_RCU=yCONFIG_TASKS_RUDE_RCU=yCONFIG_TASKS_TRACE_RCU=yCONFIG_RCU_STALL_COMMON=yCONFIG_RCU_NEED_SEGCBLIST=y
# end of RCU Subsystem
# CONFIG_IKCONFIG is not set
# CONFIG_IKHEADERS is not setCONFIG_LOG_BUF_SHIFT=17CONFIG_LOG_CPU_MAX_BUF_SHIFT=12CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13CONFIG_GENERIC_SCHED_CLOCK=y
#
# Scheduler features
#
# CONFIG_UCLAMP_TASK is not set
# end of Scheduler features
CONFIG_CGROUPS=yCONFIG_PAGE_COUNTER=yCONFIG_MEMCG=yCONFIG_MEMCG_SWAP=yCONFIG_MEMCG_KMEM=y
# CONFIG_BLK_CGROUP is not set
# CONFIG_CGROUP_SCHED is not set
# CONFIG_CGROUP_PIDS is not set
# CONFIG_CGROUP_RDMA is not set
# CONFIG_CGROUP_FREEZER is not set
# CONFIG_CPUSETS is not set
# CONFIG_CGROUP_DEVICE is not set
# CONFIG_CGROUP_CPUACCT is not set
# CONFIG_CGROUP_PERF is not set
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_NAMESPACES is not set
# CONFIG_CHECKPOINT_RESTORE is not set
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_SYSFS_DEPRECATED is not set
# CONFIG_RELAY is not setCONFIG_BLK_DEV_INITRD=yCONFIG_INITRAMFS_SOURCE=""CONFIG_RD_GZIP=yCONFIG_RD_BZIP2=yCONFIG_RD_LZMA=yCONFIG_RD_XZ=yCONFIG_RD_LZO=yCONFIG_RD_LZ4=yCONFIG_RD_ZSTD=y
# CONFIG_BOOT_CONFIG is not setCONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not setCONFIG_LD_ORPHAN_WARN=yCONFIG_SYSCTL=yCONFIG_HAVE_UID16=yCONFIG_BPF=yCONFIG_EXPERT=yCONFIG_UID16=yCONFIG_MULTIUSER=y
# CONFIG_SGETMASK_SYSCALL is not setCONFIG_SYSFS_SYSCALL=yCONFIG_FHANDLE=yCONFIG_POSIX_TIMERS=yCONFIG_PRINTK=yCONFIG_PRINTK_NMI=yCONFIG_BUG=yCONFIG_ELF_CORE=yCONFIG_BASE_FULL=yCONFIG_FUTEX=yCONFIG_FUTEX_PI=yCONFIG_EPOLL=yCONFIG_SIGNALFD=yCONFIG_TIMERFD=yCONFIG_EVENTFD=yCONFIG_SHMEM=yCONFIG_AIO=yCONFIG_IO_URING=yCONFIG_ADVISE_SYSCALLS=yCONFIG_MEMBARRIER=yCONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not setCONFIG_KALLSYMS_BASE_RELATIVE=y
# CONFIG_BPF_SYSCALL is not set
# CONFIG_USERFAULTFD is not setCONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=yCONFIG_RSEQ=y
# CONFIG_DEBUG_RSEQ is not setCONFIG_EMBEDDED=yCONFIG_HAVE_PERF_EVENTS=yCONFIG_PERF_USE_VMALLOC=y
# CONFIG_PC104 is not set
#
# Kernel Performance Events And Counters
#CONFIG_PERF_EVENTS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
# end of Kernel Performance Events And Counters
CONFIG_VM_EVENT_COUNTERS=yCONFIG_SLUB_DEBUG=y
# CONFIG_SLUB_MEMCG_SYSFS_ON is not setCONFIG_COMPAT_BRK=y
# CONFIG_SLAB is not setCONFIG_SLUB=y
# CONFIG_SLOB is not setCONFIG_SLAB_MERGE_DEFAULT=y
# CONFIG_SLAB_FREELIST_RANDOM is not set
# CONFIG_SLAB_FREELIST_HARDENED is not set
# CONFIG_SHUFFLE_PAGE_ALLOCATOR is not setCONFIG_SLUB_CPU_PARTIAL=yCONFIG_SYSTEM_DATA_VERIFICATION=y
# CONFIG_PROFILING is not setCONFIG_TRACEPOINTS=y
# end of General setup
CONFIG_ARM=yCONFIG_ARM_HAS_SG_CHAIN=yCONFIG_ARM_DMA_USE_IOMMU=yCONFIG_ARM_DMA_IOMMU_ALIGNMENT=8CONFIG_SYS_SUPPORTS_APM_EMULATION=yCONFIG_HAVE_PROC_CPU=yCONFIG_NO_IOPORT_MAP=yCONFIG_STACKTRACE_SUPPORT=yCONFIG_LOCKDEP_SUPPORT=yCONFIG_TRACE_IRQFLAGS_SUPPORT=yCONFIG_ARCH_HAS_BANDGAP=yCONFIG_FIX_EARLYCON_MEM=yCONFIG_GENERIC_HWEIGHT=yCONFIG_GENERIC_CALIBRATE_DELAY=yCONFIG_ZONE_DMA=yCONFIG_ARCH_SUPPORTS_UPROBES=yCONFIG_ARM_PATCH_PHYS_VIRT=yCONFIG_GENERIC_BUG=yCONFIG_PGTABLE_LEVELS=2
#
# System Type
#CONFIG_MMU=yCONFIG_ARCH_MMAP_RND_BITS_MIN=8CONFIG_ARCH_MMAP_RND_BITS_MAX=16CONFIG_ARCH_MULTIPLATFORM=y
# CONFIG_ARCH_EP93XX is not set
# CONFIG_ARCH_FOOTBRIDGE is not set
# CONFIG_ARCH_IOP32X is not set
# CONFIG_ARCH_IXP4XX is not set
# CONFIG_ARCH_DOVE is not set
# CONFIG_ARCH_PXA is not set
# CONFIG_ARCH_RPC is not set
# CONFIG_ARCH_SA1100 is not set
# CONFIG_ARCH_S3C24XX is not set
# CONFIG_ARCH_OMAP1 is not set
#
# Multiple platform selection
#
#
# CPU Core family selection
#
# CONFIG_ARCH_MULTI_V6 is not setCONFIG_ARCH_MULTI_V7=yCONFIG_ARCH_MULTI_V6_V7=y
# end of Multiple platform selection
CONFIG_ARCH_VIRT=y
# CONFIG_ARCH_ACTIONS is not setCONFIG_ARCH_ALPINE=yCONFIG_ARCH_ARTPEC=yCONFIG_MACH_ARTPEC6=yCONFIG_ARCH_ASPEED=yCONFIG_MACH_ASPEED_G6=yCONFIG_ARCH_AT91=yCONFIG_SOC_SAMA5D2=yCONFIG_SOC_SAMA5D3=yCONFIG_SOC_SAMA5D4=y
#
# Clocksource driver selection
#CONFIG_ATMEL_CLOCKSOURCE_PIT=yCONFIG_ATMEL_CLOCKSOURCE_TCB=yCONFIG_HAVE_AT91_UTMI=yCONFIG_HAVE_AT91_USB_CLK=yCONFIG_COMMON_CLK_AT91=yCONFIG_HAVE_AT91_SMD=yCONFIG_HAVE_AT91_H32MX=yCONFIG_HAVE_AT91_GENERATED_CLK=yCONFIG_HAVE_AT91_AUDIO_PLL=yCONFIG_HAVE_AT91_I2S_MUX_CLK=yCONFIG_SOC_SAM_V7=yCONFIG_SOC_SAMA5=yCONFIG_ATMEL_PM=yCONFIG_ARCH_BCM=y
#
# IPROC architected SoCs
#CONFIG_ARCH_BCM_IPROC=yCONFIG_ARCH_BCM_CYGNUS=yCONFIG_ARCH_BCM_HR2=yCONFIG_ARCH_BCM_NSP=yCONFIG_ARCH_BCM_5301X=y
#
# KONA architected SoCs
#CONFIG_ARCH_BCM_MOBILE=yCONFIG_ARCH_BCM_281XX=yCONFIG_ARCH_BCM_21664=y
# CONFIG_ARCH_BCM_23550 is not setCONFIG_ARCH_BCM_MOBILE_L2_CACHE=yCONFIG_ARCH_BCM_MOBILE_SMC=yCONFIG_ARCH_BCM_MOBILE_SMP=y
#
# Other Architectures
#CONFIG_ARCH_BCM2835=y
# CONFIG_ARCH_BCM_53573 is not setCONFIG_ARCH_BCM_63XX=yCONFIG_ARCH_BRCMSTB=yCONFIG_ARCH_BERLIN=yCONFIG_MACH_BERLIN_BG2=yCONFIG_MACH_BERLIN_BG2CD=yCONFIG_MACH_BERLIN_BG2Q=yCONFIG_ARCH_DIGICOLOR=yCONFIG_ARCH_EXYNOS=yCONFIG_S5P_DEV_MFC=yCONFIG_ARCH_EXYNOS3=yCONFIG_ARCH_EXYNOS4=yCONFIG_ARCH_EXYNOS5=y
#
# Exynos SoCs
#CONFIG_SOC_EXYNOS3250=yCONFIG_CPU_EXYNOS4210=yCONFIG_SOC_EXYNOS4412=yCONFIG_SOC_EXYNOS5250=yCONFIG_SOC_EXYNOS5260=yCONFIG_SOC_EXYNOS5410=yCONFIG_SOC_EXYNOS5420=yCONFIG_SOC_EXYNOS5800=yCONFIG_EXYNOS_MCPM=yCONFIG_EXYNOS_CPU_SUSPEND=yCONFIG_ARCH_HIGHBANK=yCONFIG_ARCH_HISI=y
#
# Hisilicon platform type
#
CONFIG_ARCH_HI3xxx=yCONFIG_ARCH_HIP01=yCONFIG_ARCH_HIP04=yCONFIG_ARCH_HIX5HD2=y
# end of Hisilicon platform type
CONFIG_ARCH_MXC=yCONFIG_MXC_TZIC=yCONFIG_HAVE_IMX_ANATOP=yCONFIG_HAVE_IMX_GPC=yCONFIG_HAVE_IMX_MMDC=yCONFIG_HAVE_IMX_SRC=y
#
# Cortex-A platforms
#CONFIG_SOC_IMX5=yCONFIG_SOC_IMX50=yCONFIG_SOC_IMX51=yCONFIG_SOC_IMX53=yCONFIG_SOC_IMX6=yCONFIG_SOC_IMX6Q=yCONFIG_SOC_IMX6SL=yCONFIG_SOC_IMX6SLL=yCONFIG_SOC_IMX6SX=yCONFIG_SOC_IMX6UL=yCONFIG_SOC_LS1021A=y
#
# Cortex-A/Cortex-M asymmetric multiprocessing platforms #CONFIG_SOC_IMX7D_CA7=yCONFIG_SOC_IMX7D=yCONFIG_SOC_IMX7ULP=yCONFIG_SOC_VF610=y CONFIG_VF_USE_ARM_GLOBAL_TIMER=y
# CONFIG_VF_USE_PIT_TIMER is not set CONFIG_ARCH_KEYSTONE=yCONFIG_ARCH_MEDIATEK=yCONFIG_MACH_MT2701=yCONFIG_MACH_MT6589=yCONFIG_MACH_MT6592=yCONFIG_MACH_MT7623=yCONFIG_MACH_MT7629=yCONFIG_MACH_MT8127=yCONFIG_MACH_MT8135=yCONFIG_ARCH_MESON=yCONFIG_MACH_MESON6=yCONFIG_MACH_MESON8=yCONFIG_ARCH_MILBEAUT=y CONFIG_ARCH_MILBEAUT_M10V=yCONFIG_ARCH_MMP=y
#
# Marvell PXA168/910/MMP2 Implementations
#
# CONFIG_MACH_BROWNSTONE is not set
# CONFIG_MACH_FLINT is not set
# CONFIG_MACH_MARVELL_JASPER is not setCONFIG_MACH_MMP2_DT=yCONFIG_MACH_MMP3_DT=y
# end of Marvell PXA168/910/MMP2 Implementations
# CONFIG_USB_EHCI_MV_U2O is not set
# CONFIG_ARCH_MSTARV7 is not setCONFIG_ARCH_MVEBU=yCONFIG_MACH_MVEBU_ANY=yCONFIG_MACH_MVEBU_V7=yCONFIG_MACH_ARMADA_370=yCONFIG_MACH_ARMADA_375=yCONFIG_MACH_ARMADA_38X=yCONFIG_MACH_ARMADA_39X=yCONFIG_MACH_ARMADA_XP=yCONFIG_MACH_DOVE=y
# CONFIG_ARCH_NPCM is not setCONFIG_ARCH_OMAP=y
#
# TI OMAP Common Features
#
#
# OMAP Feature Selections
#
# CONFIG_POWER_AVS_OMAP is not set
# CONFIG_OMAP_RESET_CLOCKS is not set CONFIG_OMAP_32K_TIMER=y
# CONFIG_OMAP3_L2_AUX_SECURE_SAVE_RESTORE is not set
# end of TI OMAP Common Features
CONFIG_MACH_OMAP_GENERIC=y
#
# TI OMAP/AM/DM/DRA Family
#CONFIG_OMAP_HWMOD=yCONFIG_ARCH_OMAP3=yCONFIG_ARCH_OMAP4=yCONFIG_SOC_OMAP5=yCONFIG_SOC_AM33XX=yCONFIG_SOC_AM43XX=yCONFIG_SOC_DRA7XX=yCONFIG_ARCH_OMAP2PLUS=yCONFIG_OMAP_INTERCONNECT_BARRIER=y
#
# TI OMAP2/3/4 Specific Features
#CONFIG_ARCH_OMAP2PLUS_TYPICAL=yCONFIG_SOC_HAS_OMAP2_SDRC=yCONFIG_SOC_HAS_REALTIME_COUNTER=yCONFIG_SOC_OMAP3430=yCONFIG_SOC_TI81XX=yCONFIG_OMAP_PACKAGE_CBB=y
#
# OMAP Legacy Platform Data Board Type
#CONFIG_MACH_OMAP3517EVM=yCONFIG_MACH_OMAP3_PANDORA=y
# CONFIG_OMAP3_SDRC_AC_TIMING is not set
# end of TI OMAP2/3/4 Specific Features
# CONFIG_OMAP5_ERRATA_801819 is not set
# end of TI OMAP/AM/DM/DRA Family
CONFIG_ARCH_SIRF=y
#
# CSR SiRF atlas6/primaII/Atlas7 Specific Features #CONFIG_ARCH_ATLAS6=yCONFIG_ARCH_ATLAS7=yCONFIG_ARCH_PRIMA2=yCONFIG_SIRF_IRQ=yCONFIG_PXA_SSP=mCONFIG_ARCH_QCOM=y
# CONFIG_ARCH_IPQ40XX is not set CONFIG_ARCH_MSM8X60=y CONFIG_ARCH_MSM8960=y CONFIG_ARCH_MSM8974=y
# CONFIG_ARCH_MDM9615 is not set
# CONFIG_ARCH_RDA is not set
# CONFIG_ARCH_REALTEK is not set
# CONFIG_ARCH_REALVIEW is not set CONFIG_ARCH_ROCKCHIP=y
# CONFIG_ARCH_S5PV210 is not set CONFIG_ARCH_RENESAS=y CONFIG_ARCH_SOCFPGA=y
# CONFIG_SOCFPGA_SUSPEND is not set CONFIG_PLAT_SPEAR=y CONFIG_ARCH_SPEAR13XX=y CONFIG_MACH_SPEAR1310=y CONFIG_MACH_SPEAR1340=yCONFIG_ARCH_STI=yCONFIG_SOC_STIH415=yCONFIG_SOC_STIH416=yCONFIG_SOC_STIH407=yCONFIG_ARCH_STM32=y CONFIG_MACH_STM32MP157=y CONFIG_ARCH_SUNXI=yCONFIG_MACH_SUN4I=yCONFIG_MACH_SUN5I=yCONFIG_MACH_SUN6I=yCONFIG_MACH_SUN7I=yCONFIG_MACH_SUN8I=yCONFIG_MACH_SUN9I=y CONFIG_ARCH_SUNXI_MC_SMP=y
# CONFIG_ARCH_TANGO is not set CONFIG_ARCH_TEGRA=yCONFIG_ARCH_UNIPHIER=yCONFIG_ARCH_U8500=y CONFIG_UX500_SOC_DB8500=y CONFIG_UX500_DEBUG_UART=2 CONFIG_ARCH_VEXPRESS=y CONFIG_ARCH_VEXPRESS_CORTEX_A5_A9_ERRATA=y # CONFIG_ARCH_VEXPRESS_DCSCB is not set CONFIG_ARCH_VEXPRESS_SPC=y CONFIG_ARCH_VEXPRESS_TC2_PM=y CONFIG_ARCH_VT8500=yCONFIG_ARCH_WM8850=y
# CONFIG_ARCH_ZX is not set CONFIG_ARCH_ZYNQ=yCONFIG_PLAT_ORION=yCONFIG_PLAT_PXA=yCONFIG_PLAT_VERSATILE=y
#
# Processor Type
#CONFIG_CPU_PJ4=yCONFIG_CPU_PJ4B=yCONFIG_CPU_V7=yCONFIG_CPU_THUMB_CAPABLE=y
CONFIG_CPU_32v6K=y
CONFIG_CPU_32v7=yCONFIG_CPU_ABRT_EV7=yCONFIG_CPU_PABRT_V7=yCONFIG_CPU_CACHE_V7=yCONFIG_CPU_CACHE_VIPT=yCONFIG_CPU_COPY_V6=yCONFIG_CPU_TLB_V7=yCONFIG_CPU_HAS_ASID=yCONFIG_CPU_CP15=yCONFIG_CPU_CP15_MMU=y
#
# Processor Features
#
# CONFIG_ARM_LPAE is not set CONFIG_ARM_THUMB=yCONFIG_ARM_THUMBEE=yCONFIG_ARM_VIRT_EXT=yCONFIG_SWP_EMULATE=y
# CONFIG_CPU_BIG_ENDIAN is not set
# CONFIG_CPU_ICACHE_DISABLE is not set
# CONFIG_CPU_ICACHE_MISMATCH_WORKAROUND is not set # CONFIG_CPU_BPREDICT_DISABLE is not set CONFIG_CPU_SPECTRE=y CONFIG_HARDEN_BRANCH_PREDICTOR=y CONFIG_KUSER_HELPERS=yCONFIG_VDSO=yCONFIG_OUTER_CACHE=y CONFIG_OUTER_CACHE_SYNC=y CONFIG_CACHE_B15_RAC=y CONFIG_CACHE_FEROCEON_L2=y
# CONFIG_CACHE_FEROCEON_L2_WRITETHROUGH is not set CONFIG_MIGHT_HAVE_CACHE_L2X0=y CONFIG_CACHE_L2X0=y
# CONFIG_CACHE_L2X0_PMU is not set CONFIG_PL310_ERRATA_588369=y CONFIG_PL310_ERRATA_727915=y CONFIG_PL310_ERRATA_753970=y CONFIG_PL310_ERRATA_769419=y CONFIG_CACHE_TAUROS2=y
# CONFIG_CACHE_UNIPHIER is not set CONFIG_ARM_L1_CACHE_SHIFT_6=y CONFIG_ARM_L1_CACHE_SHIFT=6 CONFIG_ARM_DMA_MEM_BUFFERABLE=y CONFIG_ARM_HEAVY_MB=y CONFIG_ARCH_SUPPORTS_BIG_ENDIAN=y CONFIG_DEBUG_ALIGN_RODATA=y CONFIG_IWMMXT=yCONFIG_PJ4B_ERRATA_4742=y CONFIG_ARM_ERRATA_430973=y CONFIG_ARM_ERRATA_643719=y CONFIG_ARM_ERRATA_720789=y CONFIG_ARM_ERRATA_754322=y CONFIG_ARM_ERRATA_754327=y CONFIG_ARM_ERRATA_764369=y CONFIG_ARM_ERRATA_775420=y CONFIG_ARM_ERRATA_798181=y
# CONFIG_ARM_ERRATA_773022 is not set
# CONFIG_ARM_ERRATA_818325_852422 is not set # CONFIG_ARM_ERRATA_821420 is not set
# CONFIG_ARM_ERRATA_825619 is not set
# CONFIG_ARM_ERRATA_857271 is not set
# CONFIG_ARM_ERRATA_852421 is not set
# CONFIG_ARM_ERRATA_852423 is not set
# CONFIG_ARM_ERRATA_857272 is not set
# end of System Type
#
# Bus support
#CONFIG_ARM_ERRATA_814220=y
# end of Bus support
#
# Kernel Features
#CONFIG_HAVE_SMP=yCONFIG_SMP=yCONFIG_SMP_ON_UP=yCONFIG_ARM_CPU_TOPOLOGY=y
# CONFIG_SCHED_MC is not set
# CONFIG_SCHED_SMT is not setCONFIG_HAVE_ARM_SCU=yCONFIG_HAVE_ARM_ARCH_TIMER=yCONFIG_HAVE_ARM_TWD=yCONFIG_MCPM=yCONFIG_MCPM_QUAD_CLUSTER=y
# CONFIG_BIG_LITTLE is not setCONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_3G_OPT is not set
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_1G is not setCONFIG_PAGE_OFFSET=0xC0000000CONFIG_KASAN_SHADOW_OFFSET=0x9f000000CONFIG_NR_CPUS=16CONFIG_HOTPLUG_CPU=yCONFIG_ARM_PSCI=yCONFIG_ARCH_NR_GPIO=2048CONFIG_HZ_FIXED=0CONFIG_HZ_100=y
# CONFIG_HZ_200 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_500 is not set
# CONFIG_HZ_1000 is not setCONFIG_HZ=100CONFIG_SCHED_HRTICK=y
# CONFIG_THUMB2_KERNEL is not setCONFIG_ARM_PATCH_IDIV=yCONFIG_AEABI=y
# CONFIG_OABI_COMPAT is not setCONFIG_ARCH_SELECT_MEMORY_MODEL=yCONFIG_ARCH_FLATMEM_ENABLE=yCONFIG_ARCH_SPARSEMEM_ENABLE=yCONFIG_HIGHMEM=yCONFIG_HIGHPTE=yCONFIG_CPU_SW_DOMAIN_PAN=yCONFIG_HW_PERF_EVENTS=yCONFIG_ARCH_WANT_GENERAL_HUGETLB=yCONFIG_ARM_MODULE_PLTS=yCONFIG_FORCE_MAX_ZONEORDER=12CONFIG_ALIGNMENT_TRAP=y
# CONFIG_UACCESS_WITH_MEMCPY is not set
# CONFIG_PARAVIRT is not set
# CONFIG_PARAVIRT_TIME_ACCOUNTING is not set
# CONFIG_XEN is not set
# end of Kernel Features
#
# Boot options
#CONFIG_USE_OF=yCONFIG_ATAGS=y
# CONFIG_DEPRECATED_PARAM_STRUCT is not set CONFIG_ZBOOT_ROM_TEXT=0x0 CONFIG_ZBOOT_ROM_BSS=0x0 CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y # CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND is not set CONFIG_CMDLINE=""CONFIG_KEXEC=yCONFIG_ATAGS_PROC=y
# CONFIG_CRASH_DUMP is not set CONFIG_AUTO_ZRELADDR=yCONFIG_EFI_STUB=yCONFIG_EFI=yCONFIG_DMI=y
# end of Boot options
#
# CPU Power Management
#
#
# CPU Frequency scaling
#CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_GOV_ATTR_SET=y CONFIG_CPU_FREQ_GOV_COMMON=y CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=m CONFIG_CPU_FREQ_GOV_ONDEMAND=y CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y
#
# CPU frequency scaling drivers
#CONFIG_CPUFREQ_DT=y CONFIG_CPUFREQ_DT_PLATDEV=y
# CONFIG_ARM_ALLWINNER_SUN50I_CPUFREQ_NVMEM is not set # CONFIG_ARM_ARMADA_37XX_CPUFREQ is not set
# CONFIG_ARM_ARMADA_8K_CPUFREQ is not set
# CONFIG_ARM_VEXPRESS_SPC_CPUFREQ is not set CONFIG_ARM_BRCMSTB_AVS_CPUFREQ=y CONFIG_ARM_HIGHBANK_CPUFREQ=m CONFIG_ARM_IMX6Q_CPUFREQ=y
# CONFIG_ARM_IMX_CPUFREQ_DT is not set
# CONFIG_ARM_MEDIATEK_CPUFREQ is not set CONFIG_ARM_OMAP2PLUS_CPUFREQ=y
# CONFIG_ARM_QCOM_CPUFREQ_HW is not set CONFIG_ARM_RASPBERRYPI_CPUFREQ=y CONFIG_ARM_SPEAR_CPUFREQ=y
# CONFIG_ARM_STI_CPUFREQ is not set CONFIG_ARM_TEGRA20_CPUFREQ=y CONFIG_ARM_TEGRA124_CPUFREQ=y CONFIG_ARM_TI_CPUFREQ=y CONFIG_QORIQ_CPUFREQ=y
# end of CPU Frequency scaling
#
# CPU Idle
#CONFIG_CPU_IDLE=yCONFIG_CPU_IDLE_MULTIPLE_DRIVERS=y
# CONFIG_CPU_IDLE_GOV_LADDER is not setCONFIG_CPU_IDLE_GOV_MENU=y
# CONFIG_CPU_IDLE_GOV_TEO is not setCONFIG_DT_IDLE_STATES=y
#
# ARM CPU Idle Drivers
#CONFIG_ARM_CPUIDLE=y
# CONFIG_ARM_PSCI_CPUIDLE is not set
# CONFIG_ARM_BIG_LITTLE_CPUIDLE is not set
# CONFIG_ARM_HIGHBANK_CPUIDLE is not setCONFIG_ARM_ZYNQ_CPUIDLE=y
# CONFIG_ARM_U8500_CPUIDLE is not setCONFIG_ARM_AT91_CPUIDLE=yCONFIG_ARM_EXYNOS_CPUIDLE=y
# CONFIG_ARM_MVEBU_V7_CPUIDLE is not setCONFIG_ARM_TEGRA_CPUIDLE=y
# CONFIG_ARM_QCOM_SPM_CPUIDLE is not set
# end of ARM CPU Idle Drivers
CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED=y
# end of CPU Idle # end of CPU Power Management
#
# Floating point emulation
#
#
# At least one emulation must be selected
#CONFIG_VFP=y
CONFIG_VFPv3=yCONFIG_NEON=yCONFIG_KERNEL_MODE_NEON=y
# end of Floating point emulation
#
# Power management options
#CONFIG_SUSPEND=yCONFIG_SUSPEND_FREEZER=y
# CONFIG_SUSPEND_SKIP_SYNC is not set
# CONFIG_HIBERNATION is not setCONFIG_PM_SLEEP=yCONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not setCONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_APM_EMULATION is not setCONFIG_PM_CLK=yCONFIG_PM_GENERIC_DOMAINS=y
# CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not setCONFIG_PM_GENERIC_DOMAINS_SLEEP=yCONFIG_PM_GENERIC_DOMAINS_OF=yCONFIG_CPU_PM=y
# CONFIG_ENERGY_MODEL is not setCONFIG_ARCH_SUSPEND_POSSIBLE=yCONFIG_ARM_CPU_SUSPEND=yCONFIG_ARCH_HIBERNATION_POSSIBLE=y
# end of Power management options
#
# Firmware Drivers
#
# CONFIG_ARM_SCMI_PROTOCOL is not set
# CONFIG_ARM_SCPI_PROTOCOL is not set
# CONFIG_FIRMWARE_MEMMAP is not set CONFIG_DMIID=y
# CONFIG_DMI_SYSFS is not set CONFIG_RASPBERRYPI_FIRMWARE=y CONFIG_QCOM_SCM=y
# CONFIG_QCOM_SCM_DOWNLOAD_MODE_DEFAULT is not set CONFIG_TRUSTED_FOUNDATIONS=y
# CONFIG_TURRIS_MOX_RWTM is not set CONFIG_BCM47XX_NVRAM=y CONFIG_BCM47XX_SPROM=y
# CONFIG_GOOGLE_FIRMWARE is not set
#
# EFI (Extensible Firmware Interface) Support
#CONFIG_EFI_ESRT=yCONFIG_EFI_VARS_PSTORE=y
# CONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE is not set CONFIG_EFI_PARAMS_FROM_FDT=y CONFIG_EFI_RUNTIME_WRAPPERS=y CONFIG_EFI_GENERIC_STUB=y CONFIG_EFI_ARMSTUB_DTB_LOADER=y
# CONFIG_EFI_GENERIC_STUB_INITRD_CMDLINE_LOADER is not set # CONFIG_EFI_BOOTLOADER_CONTROL is not set CONFIG_EFI_CAPSULE_LOADER=m
# CONFIG_EFI_TEST is not set
# CONFIG_RESET_ATTACK_MITIGATION is not set
# CONFIG_EFI_DISABLE_PCI_DMA is not set
# end of EFI (Extensible Firmware Interface) Support
CONFIG_ARM_PSCI_FW=y
# CONFIG_ARM_PSCI_CHECKER is not setCONFIG_HAVE_ARM_SMCCC=yCONFIG_HAVE_ARM_SMCCC_DISCOVERY=yCONFIG_ARM_SMCCC_SOC_ID=y
#
# Tegra firmware driver
#
# CONFIG_TEGRA_IVC is not set
# end of Tegra firmware driver # end of Firmware Drivers
CONFIG_ARM_CRYPTO=yCONFIG_CRYPTO_SHA1_ARM=mCONFIG_CRYPTO_SHA1_ARM_NEON=mCONFIG_CRYPTO_SHA1_ARM_CE=mCONFIG_CRYPTO_SHA2_ARM_CE=mCONFIG_CRYPTO_SHA256_ARM=mCONFIG_CRYPTO_SHA512_ARM=mCONFIG_CRYPTO_AES_ARM=mCONFIG_CRYPTO_AES_ARM_BS=mCONFIG_CRYPTO_AES_ARM_CE=mCONFIG_CRYPTO_GHASH_ARM_CE=mCONFIG_CRYPTO_CRC32_ARM_CE=mCONFIG_CRYPTO_CHACHA20_NEON=m
# CONFIG_CRYPTO_POLY1305_ARM is not set
# CONFIG_CRYPTO_NHPOLY1305_NEON is not set
# CONFIG_CRYPTO_CURVE25519_NEON is not setCONFIG_AS_VFP_VMRS_FPINST=y
#
# General architecture-dependent options
#CONFIG_CRASH_CORE=yCONFIG_KEXEC_CORE=yCONFIG_SET_FS=yCONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
# CONFIG_JUMP_LABEL is not setCONFIG_UPROBES=yCONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=yCONFIG_ARCH_USE_BUILTIN_BSWAP=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_HAVE_OPTPROBES=yCONFIG_HAVE_NMI=yCONFIG_HAVE_ARCH_TRACEHOOK=yCONFIG_HAVE_DMA_CONTIGUOUS=yCONFIG_GENERIC_SMP_IDLE_THREAD=yCONFIG_GENERIC_IDLE_POLL_SETUP=yCONFIG_ARCH_HAS_FORTIFY_SOURCE=yCONFIG_ARCH_HAS_KEEPINITRD=yCONFIG_ARCH_HAS_SET_MEMORY=yCONFIG_HAVE_ARCH_THREAD_STRUCT_WHITELIST=yCONFIG_ARCH_32BIT_OFF_T=yCONFIG_HAVE_REGS_AND_STACK_ACCESS_API=yCONFIG_HAVE_RSEQ=yCONFIG_HAVE_HW_BREAKPOINT=yCONFIG_HAVE_PERF_REGS=yCONFIG_HAVE_PERF_USER_STACK_DUMP=yCONFIG_HAVE_ARCH_JUMP_LABEL=yCONFIG_ARCH_WANT_IPC_PARSE_VERSION=yCONFIG_HAVE_ARCH_SECCOMP=yCONFIG_HAVE_ARCH_SECCOMP_FILTER=yCONFIG_SECCOMP=yCONFIG_SECCOMP_FILTER=y
# CONFIG_SECCOMP_CACHE_DEBUG is not setCONFIG_HAVE_STACKPROTECTOR=yCONFIG_STACKPROTECTOR=yCONFIG_STACKPROTECTOR_STRONG=yCONFIG_HAVE_CONTEXT_TRACKING=yCONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=yCONFIG_HAVE_IRQ_TIME_ACCOUNTING=yCONFIG_HAVE_MOD_ARCH_SPECIFIC=yCONFIG_MODULES_USE_ELF_REL=yCONFIG_ARCH_HAS_ELF_RANDOMIZE=yCONFIG_HAVE_ARCH_MMAP_RND_BITS=yCONFIG_HAVE_EXIT_THREAD=yCONFIG_ARCH_MMAP_RND_BITS=8CONFIG_ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT=yCONFIG_CLONE_BACKWARDS=yCONFIG_OLD_SIGSUSPEND3=yCONFIG_OLD_SIGACTION=yCONFIG_COMPAT_32BIT_TIME=yCONFIG_ARCH_OPTIONAL_KERNEL_RWX=yCONFIG_ARCH_OPTIONAL_KERNEL_RWX_DEFAULT=yCONFIG_ARCH_HAS_STRICT_KERNEL_RWX=yCONFIG_STRICT_KERNEL_RWX=yCONFIG_ARCH_HAS_STRICT_MODULE_RWX=yCONFIG_STRICT_MODULE_RWX=yCONFIG_ARCH_HAS_PHYS_TO_DMA=y
# CONFIG_LOCK_EVENT_COUNTS is not setCONFIG_ARCH_WANT_LD_ORPHAN_WARN=yCONFIG_HAVE_ARCH_PFN_VALID=y
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not setCONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
# end of GCOV-based kernel profiling
CONFIG_HAVE_GCC_PLUGINS=y
# end of General architecture-dependent options
CONFIG_RT_MUTEXES=yCONFIG_BASE_SMALL=0CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_MODULE_SIG is not set
# CONFIG_MODULE_COMPRESS is not set
# CONFIG_MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS is not set # CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_TRIM_UNUSED_KSYMS is not set CONFIG_MODULES_TREE_LOOKUP=yCONFIG_BLOCK=yCONFIG_BLK_SCSI_REQUEST=yCONFIG_BLK_DEV_BSG=y
# CONFIG_BLK_DEV_BSGLIB is not set
# CONFIG_BLK_DEV_INTEGRITY is not set
# CONFIG_BLK_DEV_ZONED is not set CONFIG_BLK_CMDLINE_PARSER=y
# CONFIG_BLK_WBT is not setCONFIG_BLK_DEBUG_FS=y
# CONFIG_BLK_SED_OPAL is not set
# CONFIG_BLK_INLINE_ENCRYPTION is not set
#
# Partition Types
#CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_AIX_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not setCONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not setCONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not setCONFIG_CMDLINE_PARTITION=y
# end of Partition Types
CONFIG_BLK_MQ_PCI=yCONFIG_BLK_MQ_VIRTIO=yCONFIG_BLK_PM=y
#
# IO Schedulers
#CONFIG_MQ_IOSCHED_DEADLINE=yCONFIG_MQ_IOSCHED_KYBER=y
# CONFIG_IOSCHED_BFQ is not set
# end of IO Schedulers
CONFIG_ASN1=yCONFIG_UNINLINE_SPIN_UNLOCK=yCONFIG_ARCH_SUPPORTS_ATOMIC_RMW=yCONFIG_MUTEX_SPIN_ON_OWNER=yCONFIG_RWSEM_SPIN_ON_OWNER=yCONFIG_LOCK_SPIN_ON_OWNER=yCONFIG_ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE=yCONFIG_FREEZER=y
#
# Executable file formats
#CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_ELF_FDPIC is not setCONFIG_ELFCORE=yCONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=yCONFIG_BINFMT_SCRIPT=yCONFIG_ARCH_HAS_BINFMT_FLAT=y
# CONFIG_BINFMT_FLAT is not setCONFIG_BINFMT_FLAT_ARGVP_ENVP_ON_STACK=y
# CONFIG_BINFMT_MISC is not setCONFIG_COREDUMP=y
# end of Executable file formats
#
# Memory Management options
#CONFIG_SELECT_MEMORY_MODEL=yCONFIG_FLATMEM_MANUAL=y
# CONFIG_SPARSEMEM_MANUAL is not setCONFIG_FLATMEM=yCONFIG_FLAT_NODE_MEM_MAP=yCONFIG_ARCH_KEEP_MEMBLOCK=yCONFIG_MEMORY_ISOLATION=yCONFIG_SPLIT_PTLOCK_CPUS=4CONFIG_COMPACTION=y
# CONFIG_PAGE_REPORTING is not setCONFIG_MIGRATION=yCONFIG_CONTIG_ALLOC=yCONFIG_BOUNCE=y
# CONFIG_KSM is not setCONFIG_DEFAULT_MMAP_MIN_ADDR=4096
# CONFIG_CLEANCACHE is not set
# CONFIG_FRONTSWAP is not setCONFIG_CMA=y
# CONFIG_CMA_DEBUG is not set
# CONFIG_CMA_DEBUGFS is not setCONFIG_CMA_AREAS=7
# CONFIG_ZPOOL is not set
# CONFIG_ZBUD is not set
# CONFIG_ZSMALLOC is not setCONFIG_GENERIC_EARLY_IOREMAP=y
# CONFIG_IDLE_PAGE_TRACKING is not setCONFIG_FRAME_VECTOR=y
# CONFIG_PERCPU_STATS is not set
# CONFIG_GUP_TEST is not setCONFIG_KMAP_LOCAL=y
# end of Memory Management options
CONFIG_NET=yCONFIG_SKB_EXTENSIONS=y
#
# Networking options
#CONFIG_PACKET=y
# CONFIG_PACKET_DIAG is not setCONFIG_UNIX=yCONFIG_UNIX_SCM=y
# CONFIG_UNIX_DIAG is not set
# CONFIG_TLS is not setCONFIG_XFRM=yCONFIG_XFRM_ALGO=m
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_INTERFACE is not set
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not setCONFIG_XFRM_AH=mCONFIG_XFRM_ESP=mCONFIG_XFRM_IPCOMP=m
# CONFIG_NET_KEY is not setCONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not setCONFIG_IP_PNP=yCONFIG_IP_PNP_DHCP=yCONFIG_IP_PNP_BOOTP=yCONFIG_IP_PNP_RARP=y
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE_DEMUX is not setCONFIG_NET_IP_TUNNEL=y
# CONFIG_SYN_COOKIES is not set
# CONFIG_NET_IPVTI is not set
# CONFIG_NET_FOU is not set
# CONFIG_NET_FOU_IP_TUNNELS is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not setCONFIG_INET_TUNNEL=yCONFIG_INET_DIAG=yCONFIG_INET_TCP_DIAG=y
# CONFIG_INET_UDP_DIAG is not set
# CONFIG_INET_RAW_DIAG is not set
# CONFIG_INET_DIAG_DESTROY is not set
# CONFIG_TCP_CONG_ADVANCED is not setCONFIG_TCP_CONG_CUBIC=yCONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not setCONFIG_IPV6=yCONFIG_IPV6_ROUTER_PREF=y
# CONFIG_IPV6_ROUTE_INFO is not setCONFIG_IPV6_OPTIMISTIC_DAD=yCONFIG_INET6_AH=mCONFIG_INET6_ESP=m
# CONFIG_INET6_ESP_OFFLOAD is not set
# CONFIG_INET6_ESPINTCP is not setCONFIG_INET6_IPCOMP=mCONFIG_IPV6_MIP6=mCONFIG_INET6_XFRM_TUNNEL=mCONFIG_INET6_TUNNEL=m
# CONFIG_IPV6_VTI is not setCONFIG_IPV6_SIT=y
# CONFIG_IPV6_SIT_6RD is not setCONFIG_IPV6_NDISC_NODETYPE=yCONFIG_IPV6_TUNNEL=mCONFIG_IPV6_MULTIPLE_TABLES=y
# CONFIG_IPV6_SUBTREES is not set
# CONFIG_IPV6_MROUTE is not set
# CONFIG_IPV6_SEG6_LWTUNNEL is not set
# CONFIG_IPV6_SEG6_HMAC is not set
# CONFIG_IPV6_RPL_LWTUNNEL is not set
# CONFIG_MPTCP is not set
# CONFIG_NETWORK_SECMARK is not setCONFIG_NET_PTP_CLASSIFY=y
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
# CONFIG_NETFILTER is not set
# CONFIG_BPFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_L2TP is not set
# CONFIG_BRIDGE is not setCONFIG_HAVE_NET_DSA=yCONFIG_NET_DSA=m
# CONFIG_NET_DSA_TAG_AR9331 is not setCONFIG_NET_DSA_TAG_BRCM_COMMON=mCONFIG_NET_DSA_TAG_BRCM=mCONFIG_NET_DSA_TAG_BRCM_PREPEND=m
# CONFIG_NET_DSA_TAG_HELLCREEK is not set
# CONFIG_NET_DSA_TAG_GSWIP is not set
# CONFIG_NET_DSA_TAG_DSA is not set
# CONFIG_NET_DSA_TAG_EDSA is not set
# CONFIG_NET_DSA_TAG_MTK is not set
# CONFIG_NET_DSA_TAG_KSZ is not set
# CONFIG_NET_DSA_TAG_RTL4_A is not set
# CONFIG_NET_DSA_TAG_OCELOT is not set
# CONFIG_NET_DSA_TAG_QCA is not set
# CONFIG_NET_DSA_TAG_LAN9303 is not set
# CONFIG_NET_DSA_TAG_SJA1105 is not set
# CONFIG_NET_DSA_TAG_TRAILER is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_PHONET is not set
# CONFIG_6LOWPAN is not set
# CONFIG_IEEE802154 is not set
# CONFIG_NET_SCHED is not set
# CONFIG_DCB is not setCONFIG_DNS_RESOLVER=y
# CONFIG_BATMAN_ADV is not set
# CONFIG_OPENVSWITCH is not set
# CONFIG_VSOCKETS is not set
# CONFIG_NETLINK_DIAG is not set
# CONFIG_MPLS is not set
# CONFIG_NET_NSH is not set
# CONFIG_HSR is not setCONFIG_NET_SWITCHDEV=y
# CONFIG_NET_L3_MASTER_DEV is not set
# CONFIG_QRTR is not set
# CONFIG_NET_NCSI is not setCONFIG_RPS=yCONFIG_RFS_ACCEL=yCONFIG_XPS=y
# CONFIG_CGROUP_NET_PRIO is not set
# CONFIG_CGROUP_NET_CLASSID is not setCONFIG_NET_RX_BUSY_POLL=yCONFIG_BQL=y
# CONFIG_BPF_JIT is not setCONFIG_NET_FLOW_LIMIT=y
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NET_DROP_MONITOR is not set
# end of Network testing # end of Networking options
# CONFIG_HAMRADIO is not setCONFIG_CAN=yCONFIG_CAN_RAW=yCONFIG_CAN_BCM=yCONFIG_CAN_GW=y
# CONFIG_CAN_J1939 is not set
# CONFIG_CAN_ISOTP is not set
#
# CAN Device Drivers
#
# CONFIG_CAN_VCAN is not set
# CONFIG_CAN_VXCAN is not set
# CONFIG_CAN_SLCAN is not setCONFIG_CAN_DEV=yCONFIG_CAN_CALC_BITTIMING=yCONFIG_CAN_AT91=mCONFIG_CAN_FLEXCAN=m
# CONFIG_CAN_GRCAN is not set
# CONFIG_CAN_KVASER_PCIEFD is not setCONFIG_CAN_SUN4I=y
# CONFIG_CAN_TI_HECC is not setCONFIG_CAN_XILINXCAN=y
# CONFIG_CAN_C_CAN is not set
# CONFIG_CAN_CC770 is not set
# CONFIG_CAN_IFI_CANFD is not set
# CONFIG_CAN_M_CAN is not set
# CONFIG_CAN_PEAK_PCIEFD is not setCONFIG_CAN_RCAR=m
# CONFIG_CAN_RCAR_CANFD is not set
# CONFIG_CAN_SJA1000 is not set
# CONFIG_CAN_SOFTING is not set
#
# CAN SPI interfaces
#
# CONFIG_CAN_HI311X is not setCONFIG_CAN_MCP251X=y
# CONFIG_CAN_MCP251XFD is not set
# end of CAN SPI interfaces
#
# CAN USB interfaces
#
# CONFIG_CAN_8DEV_USB is not set
# CONFIG_CAN_EMS_USB is not set
# CONFIG_CAN_ESD_USB2 is not set
# CONFIG_CAN_GS_USB is not set
# CONFIG_CAN_KVASER_USB is not set
# CONFIG_CAN_MCBA_USB is not set
# CONFIG_CAN_PEAK_USB is not set
# CONFIG_CAN_UCAN is not set
# end of CAN USB interfaces
# CONFIG_CAN_DEBUG_DEVICES is not set
# end of CAN Device Drivers
CONFIG_BT=mCONFIG_BT_BREDR=y
# CONFIG_BT_RFCOMM is not set
# CONFIG_BT_BNEP is not set
# CONFIG_BT_HIDP is not set
# CONFIG_BT_HS is not setCONFIG_BT_LE=y
# CONFIG_BT_LEDS is not set
# CONFIG_BT_MSFTEXT is not setCONFIG_BT_DEBUGFS=y
# CONFIG_BT_SELFTEST is not set
# CONFIG_BT_FEATURE_DEBUG is not set
#
# Bluetooth device drivers
#CONFIG_BT_BCM=m
# CONFIG_BT_HCIBTUSB is not set
# CONFIG_BT_HCIBTSDIO is not setCONFIG_BT_HCIUART=mCONFIG_BT_HCIUART_SERDEV=yCONFIG_BT_HCIUART_H4=y
# CONFIG_BT_HCIUART_NOKIA is not set
# CONFIG_BT_HCIUART_BCSP is not set
# CONFIG_BT_HCIUART_ATH3K is not set
# CONFIG_BT_HCIUART_LL is not set
# CONFIG_BT_HCIUART_3WIRE is not set
# CONFIG_BT_HCIUART_INTEL is not setCONFIG_BT_HCIUART_BCM=y
# CONFIG_BT_HCIUART_RTL is not set
# CONFIG_BT_HCIUART_QCA is not set
# CONFIG_BT_HCIUART_AG6XX is not set
# CONFIG_BT_HCIUART_MRVL is not set
# CONFIG_BT_HCIBCM203X is not set
# CONFIG_BT_HCIBPA10X is not set
# CONFIG_BT_HCIBFUSB is not set
# CONFIG_BT_HCIVHCI is not setCONFIG_BT_MRVL=mCONFIG_BT_MRVL_SDIO=m
# CONFIG_BT_MTKSDIO is not set
# CONFIG_BT_MTKUART is not set
# CONFIG_BT_QCOMSMD is not set
# end of Bluetooth device drivers
# CONFIG_AF_RXRPC is not set
# CONFIG_AF_KCM is not setCONFIG_FIB_RULES=yCONFIG_WIRELESS=yCONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_CERTIFICATION_ONUS is not setCONFIG_CFG80211_REQUIRE_SIGNED_REGDB=yCONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=yCONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not setCONFIG_CFG80211_CRDA_SUPPORT=y
# CONFIG_CFG80211_WEXT is not setCONFIG_MAC80211=mCONFIG_MAC80211_HAS_RC=yCONFIG_MAC80211_RC_MINSTREL=yCONFIG_MAC80211_RC_DEFAULT_MINSTREL=yCONFIG_MAC80211_RC_DEFAULT="minstrel_ht"
# CONFIG_MAC80211_MESH is not set
# CONFIG_MAC80211_LEDS is not set
# CONFIG_MAC80211_DEBUGFS is not set
# CONFIG_MAC80211_MESSAGE_TRACING is not set
# CONFIG_MAC80211_DEBUG_MENU is not setCONFIG_MAC80211_STA_HASH_MAX_SIZE=0CONFIG_RFKILL=yCONFIG_RFKILL_LEDS=yCONFIG_RFKILL_INPUT=yCONFIG_RFKILL_GPIO=yCONFIG_NET_9P=yCONFIG_NET_9P_VIRTIO=y
# CONFIG_NET_9P_DEBUG is not set
# CONFIG_CAIF is not set
# CONFIG_CEPH_LIB is not setCONFIG_NFC=mCONFIG_NFC_DIGITAL=mCONFIG_NFC_NCI=mCONFIG_NFC_NCI_SPI=mCONFIG_NFC_NCI_UART=mCONFIG_NFC_HCI=mCONFIG_NFC_SHDLC=y
#
# Near Field Communication (NFC) devices
#
# CONFIG_NFC_TRF7970A is not set
# CONFIG_NFC_SIM is not set
# CONFIG_NFC_PORT100 is not set
# CONFIG_NFC_FDP is not set
# CONFIG_NFC_PN544_I2C is not set
# CONFIG_NFC_PN533_USB is not set
# CONFIG_NFC_PN533_I2C is not set
# CONFIG_NFC_PN532_UART is not set
# CONFIG_NFC_MICROREAD_I2C is not set
# CONFIG_NFC_MRVL_USB is not set
# CONFIG_NFC_MRVL_UART is not set
# CONFIG_NFC_ST21NFCA_I2C is not set
# CONFIG_NFC_ST_NCI_I2C is not set
# CONFIG_NFC_ST_NCI_SPI is not set
# CONFIG_NFC_NXP_NCI is not setCONFIG_NFC_S3FWRN5=mCONFIG_NFC_S3FWRN5_I2C=m
# CONFIG_NFC_S3FWRN82_UART is not set
# CONFIG_NFC_ST95HF is not set
# end of Near Field Communication (NFC) devices
# CONFIG_PSAMPLE is not set
# CONFIG_NET_IFE is not set
# CONFIG_LWTUNNEL is not setCONFIG_DST_CACHE=yCONFIG_GRO_CELLS=yCONFIG_NET_DEVLINK=yCONFIG_PAGE_POOL=yCONFIG_FAILOVER=yCONFIG_ETHTOOL_NETLINK=yCONFIG_HAVE_EBPF_JIT=y
#
# Device Drivers
#CONFIG_ARM_AMBA=yCONFIG_TEGRA_AHB=yCONFIG_HAVE_PCI=yCONFIG_FORCE_PCI=yCONFIG_PCI=yCONFIG_PCI_DOMAINS=yCONFIG_PCI_DOMAINS_GENERIC=yCONFIG_PCI_SYSCALL=yCONFIG_PCIEPORTBUS=y
# CONFIG_PCIEAER is not setCONFIG_PCIEASPM=yCONFIG_PCIEASPM_DEFAULT=y
# CONFIG_PCIEASPM_POWERSAVE is not set
# CONFIG_PCIEASPM_POWER_SUPERSAVE is not set
# CONFIG_PCIEASPM_PERFORMANCE is not setCONFIG_PCIE_PME=y
# CONFIG_PCIE_PTM is not set
# CONFIG_PCIE_BW is not setCONFIG_PCI_MSI=yCONFIG_PCI_MSI_IRQ_DOMAIN=yCONFIG_PCI_MSI_ARCH_FALLBACKS=yCONFIG_PCI_QUIRKS=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_STUB is not setCONFIG_PCI_ECAM=yCONFIG_PCI_BRIDGE_EMUL=y
# CONFIG_PCI_IOV is not set
# CONFIG_PCI_PRI is not set
# CONFIG_PCI_PASID is not setCONFIG_PCI_LABEL=y
# CONFIG_PCIE_BUS_TUNE_OFF is not setCONFIG_PCIE_BUS_DEFAULT=y
# CONFIG_PCIE_BUS_SAFE is not set
# CONFIG_PCIE_BUS_PERFORMANCE is not set
# CONFIG_PCIE_BUS_PEER2PEER is not set
# CONFIG_HOTPLUG_PCI is not set
#
# PCI controller drivers
#CONFIG_PCI_MVEBU=y
# CONFIG_PCI_FTPCI100 is not setCONFIG_PCI_TEGRA=yCONFIG_PCI_RCAR_GEN2=y
# CONFIG_PCIE_RCAR is not setCONFIG_PCIE_RCAR_HOST=y
# CONFIG_PCIE_RCAR_EP is not setCONFIG_PCI_HOST_COMMON=yCONFIG_PCI_HOST_GENERIC=y
# CONFIG_PCIE_XILINX is not set
# CONFIG_PCI_V3_SEMI is not setCONFIG_PCIE_IPROC=yCONFIG_PCIE_IPROC_PLATFORM=yCONFIG_PCIE_IPROC_BCMA=yCONFIG_PCIE_IPROC_MSI=y
# CONFIG_PCIE_ALTERA is not set
# CONFIG_PCIE_ROCKCHIP_HOST is not set
# CONFIG_PCIE_ROCKCHIP_EP is not set
# CONFIG_PCIE_MEDIATEK is not setCONFIG_PCIE_BRCMSTB=y
#
# DesignWare PCI Core Support
#CONFIG_PCIE_DW=yCONFIG_PCIE_DW_HOST=yCONFIG_PCIE_DW_EP=yCONFIG_PCI_DRA7XX=yCONFIG_PCI_DRA7XX_HOST=yCONFIG_PCI_DRA7XX_EP=y
# CONFIG_PCIE_DW_PLAT_HOST is not set
# CONFIG_PCIE_DW_PLAT_EP is not set
# CONFIG_PCI_EXYNOS is not set
# CONFIG_PCI_IMX6 is not set
# CONFIG_PCIE_SPEAR13XX is not set
# CONFIG_PCI_KEYSTONE_HOST is not set
# CONFIG_PCI_KEYSTONE_EP is not set
# CONFIG_PCI_LAYERSCAPE is not set
# CONFIG_PCI_LAYERSCAPE_EP is not set
# CONFIG_PCIE_QCOM is not set
# CONFIG_PCIE_ARMADA_8K is not set
# CONFIG_PCIE_ARTPEC6_HOST is not set
# CONFIG_PCIE_ARTPEC6_EP is not set
# CONFIG_PCIE_HISI_STB is not setCONFIG_PCI_MESON=m
# CONFIG_PCIE_UNIPHIER is not set
# CONFIG_PCIE_UNIPHIER_EP is not set
# end of DesignWare PCI Core Support
#
# Mobiveil PCIe Core Support
#
# end of Mobiveil PCIe Core Support
#
# Cadence PCIe controllers support
#
# CONFIG_PCIE_CADENCE_PLAT_HOST is not set
# CONFIG_PCIE_CADENCE_PLAT_EP is not set
# CONFIG_PCI_J721E_HOST is not set
# CONFIG_PCI_J721E_EP is not set
# end of Cadence PCIe controllers support # end of PCI controller drivers
#
# PCI Endpoint
#CONFIG_PCI_ENDPOINT=yCONFIG_PCI_ENDPOINT_CONFIGFS=yCONFIG_PCI_EPF_TEST=m
# end of PCI Endpoint
#
# PCI switch controller drivers
#
# CONFIG_PCI_SW_SWITCHTEC is not set
# end of PCI switch controller drivers
# CONFIG_PCCARD is not set
# CONFIG_RAPIDIO is not set
#
# Generic Driver Options
#
# CONFIG_UEVENT_HELPER is not setCONFIG_DEVTMPFS=yCONFIG_DEVTMPFS_MOUNT=yCONFIG_STANDALONE=yCONFIG_PREVENT_FIRMWARE_BUILD=y
#
# Firmware loader
#CONFIG_FW_LOADER=yCONFIG_EXTRA_FIRMWARE=""
# CONFIG_FW_LOADER_USER_HELPER is not set
# CONFIG_FW_LOADER_COMPRESS is not setCONFIG_FW_CACHE=y
# end of Firmware loader
CONFIG_WANT_DEV_COREDUMP=yCONFIG_ALLOW_DEV_COREDUMP=yCONFIG_DEV_COREDUMP=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_DEBUG_TEST_DRIVER_REMOVE is not set
# CONFIG_PM_QOS_KUNIT_TEST is not setCONFIG_TEST_ASYNC_DRIVER_PROBE=m
# CONFIG_KUNIT_DRIVER_PE_TEST is not setCONFIG_GENERIC_CPU_AUTOPROBE=yCONFIG_SOC_BUS=yCONFIG_REGMAP=yCONFIG_REGMAP_AC97=mCONFIG_REGMAP_I2C=yCONFIG_REGMAP_SPI=yCONFIG_REGMAP_SPMI=yCONFIG_REGMAP_MMIO=yCONFIG_REGMAP_IRQ=yCONFIG_DMA_SHARED_BUFFER=y
# CONFIG_DMA_FENCE_TRACE is not setCONFIG_GENERIC_ARCH_TOPOLOGY=y
# end of Generic Driver Options
#
# Bus devices
#CONFIG_ARM_CCI=yCONFIG_ARM_CCI400_COMMON=yCONFIG_ARM_CCI400_PORT_CTRL=yCONFIG_BRCMSTB_GISB_ARB=y
# CONFIG_MOXTET is not set
# CONFIG_IMX_WEIM is not setCONFIG_MVEBU_MBUS=yCONFIG_OMAP_INTERCONNECT=yCONFIG_OMAP_OCP2SCP=yCONFIG_QCOM_EBI2=yCONFIG_SIMPLE_PM_BUS=y
# CONFIG_SUN50I_DE2_BUS is not setCONFIG_SUNXI_RSB=y
# CONFIG_TEGRA_GMI is not setCONFIG_TI_SYSC=yCONFIG_UNIPHIER_SYSTEM_BUS=yCONFIG_VEXPRESS_CONFIG=y
# CONFIG_FSL_MC_BUS is not set
# CONFIG_MHI_BUS is not set
# end of Bus devices
# CONFIG_CONNECTOR is not set
# CONFIG_GNSS is not setCONFIG_MTD=y
# CONFIG_MTD_TESTS is not set
#
# Partition parsers
#
# CONFIG_MTD_AR7_PARTS is not set
# CONFIG_MTD_BCM47XX_PARTS is not setCONFIG_MTD_CMDLINE_PARTS=yCONFIG_MTD_OF_PARTS=y
# CONFIG_MTD_AFS_PARTS is not set
# CONFIG_MTD_PARSER_TRX is not set
# CONFIG_MTD_REDBOOT_PARTS is not set
# end of Partition parsers
#
# User Modules And Translation Layers
#CONFIG_MTD_BLKDEVS=yCONFIG_MTD_BLOCK=y
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_RFD_FTL is not set
# CONFIG_SSFDC is not set
# CONFIG_SM_FTL is not set
# CONFIG_MTD_OOPS is not set
# CONFIG_MTD_SWAP is not set
# CONFIG_MTD_PARTITIONED_MASTER is not set
#
# RAM/ROM/Flash chip drivers
#CONFIG_MTD_CFI=y
# CONFIG_MTD_JEDECPROBE is not setCONFIG_MTD_GEN_PROBE=y
# CONFIG_MTD_CFI_ADV_OPTIONS is not setCONFIG_MTD_MAP_BANK_WIDTH_1=yCONFIG_MTD_MAP_BANK_WIDTH_2=yCONFIG_MTD_MAP_BANK_WIDTH_4=yCONFIG_MTD_CFI_I1=yCONFIG_MTD_CFI_I2=yCONFIG_MTD_CFI_INTELEXT=y
# CONFIG_MTD_CFI_AMDSTD is not set
# CONFIG_MTD_CFI_STAA is not setCONFIG_MTD_CFI_UTIL=y
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# end of RAM/ROM/Flash chip drivers
#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not setCONFIG_MTD_PHYSMAP=y
# CONFIG_MTD_PHYSMAP_COMPAT is not setCONFIG_MTD_PHYSMAP_OF=y
# CONFIG_MTD_PHYSMAP_VERSATILE is not set
# CONFIG_MTD_PHYSMAP_GEMINI is not set
# CONFIG_MTD_PHYSMAP_IXP4XX is not set
# CONFIG_MTD_INTEL_VR_NOR is not set
# CONFIG_MTD_PLATRAM is not set
# end of Mapping drivers for chip access
#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_DATAFLASH is not set
# CONFIG_MTD_MCHP23K256 is not setCONFIG_MTD_SPEAR_SMI=y
# CONFIG_MTD_SST25L is not set
# CONFIG_MTD_BCM47XXSFLASH is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLOCK2MTD is not set
#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOCG3 is not set
# CONFIG_MTD_ST_SPI_FSM is not set
# end of Self-contained MTD device drivers
#
# NAND
#CONFIG_MTD_NAND_CORE=y
# CONFIG_MTD_ONENAND is not setCONFIG_MTD_RAW_NAND=y
#
# Raw/parallel NAND flash controllers
#CONFIG_MTD_NAND_DENALI=y
# CONFIG_MTD_NAND_DENALI_PCI is not setCONFIG_MTD_NAND_DENALI_DT=yCONFIG_MTD_NAND_OMAP2=yCONFIG_MTD_NAND_OMAP_BCH=yCONFIG_MTD_NAND_OMAP_BCH_BUILD=y
# CONFIG_MTD_NAND_CAFE is not setCONFIG_MTD_NAND_ATMEL=y
# CONFIG_MTD_NAND_ORION is not setCONFIG_MTD_NAND_MARVELL=yCONFIG_MTD_NAND_BRCMNAND=yCONFIG_MTD_NAND_GPMI_NAND=y
# CONFIG_MTD_NAND_FSL_IFC is not setCONFIG_MTD_NAND_VF610_NFC=y
# CONFIG_MTD_NAND_MXC is not setCONFIG_MTD_NAND_DAVINCI=y
# CONFIG_MTD_NAND_FSMC is not set
# CONFIG_MTD_NAND_SUNXI is not set
# CONFIG_MTD_NAND_HISI504 is not set
# CONFIG_MTD_NAND_QCOM is not set
# CONFIG_MTD_NAND_MTK is not set
# CONFIG_MTD_NAND_MXIC is not set
# CONFIG_MTD_NAND_TEGRA is not setCONFIG_MTD_NAND_STM32_FMC2=y
# CONFIG_MTD_NAND_MESON is not set
# CONFIG_MTD_NAND_GPIO is not set
# CONFIG_MTD_NAND_PLATFORM is not set
# CONFIG_MTD_NAND_CADENCE is not set
# CONFIG_MTD_NAND_ARASAN is not set
# CONFIG_MTD_NAND_INTEL_LGM is not set
# CONFIG_MTD_NAND_ROCKCHIP is not set
#
# Misc
#
# CONFIG_MTD_NAND_NANDSIM is not set
# CONFIG_MTD_NAND_RICOH is not set
# CONFIG_MTD_NAND_DISKONCHIP is not set
# CONFIG_MTD_SPI_NAND is not set
#
# ECC engine support
#CONFIG_MTD_NAND_ECC=yCONFIG_MTD_NAND_ECC_SW_HAMMING=y
# CONFIG_MTD_NAND_ECC_SW_HAMMING_SMC is not set
# CONFIG_MTD_NAND_ECC_SW_BCH is not set
# end of ECC engine support # end of NAND
#
# LPDDR & LPDDR2 PCM memory drivers
#
# CONFIG_MTD_LPDDR is not set
# CONFIG_MTD_LPDDR2_NVM is not set
# end of LPDDR & LPDDR2 PCM memory drivers
CONFIG_MTD_SPI_NOR=yCONFIG_MTD_SPI_NOR_USE_4K_SECTORS=y
# CONFIG_MTD_SPI_NOR_SWP_DISABLE is not setCONFIG_MTD_SPI_NOR_SWP_DISABLE_ON_VOLATILE=y
# CONFIG_MTD_SPI_NOR_SWP_KEEP is not setCONFIG_SPI_ASPEED_SMC=m
# CONFIG_SPI_HISI_SFC is not setCONFIG_MTD_UBI=yCONFIG_MTD_UBI_WL_THRESHOLD=4096CONFIG_MTD_UBI_BEB_LIMIT=20
# CONFIG_MTD_UBI_FASTMAP is not set
# CONFIG_MTD_UBI_GLUEBI is not set
# CONFIG_MTD_UBI_BLOCK is not set
# CONFIG_MTD_HYPERBUS is not setCONFIG_DTC=yCONFIG_OF=y
# CONFIG_OF_UNITTEST is not setCONFIG_OF_FLATTREE=yCONFIG_OF_EARLY_FLATTREE=yCONFIG_OF_KOBJ=yCONFIG_OF_DYNAMIC=yCONFIG_OF_ADDRESS=yCONFIG_OF_IRQ=yCONFIG_OF_NET=yCONFIG_OF_RESERVED_MEM=yCONFIG_OF_RESOLVE=yCONFIG_OF_OVERLAY=yCONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y
# CONFIG_PARPORT is not setCONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_NULL_BLK is not setCONFIG_CDROM=y
# CONFIG_BLK_DEV_PCIESSD_MTIP32XX is not set
# CONFIG_BLK_DEV_UMEM is not setCONFIG_BLK_DEV_LOOP=yCONFIG_BLK_DEV_LOOP_MIN_COUNT=8
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not setCONFIG_BLK_DEV_RAM=yCONFIG_BLK_DEV_RAM_COUNT=16CONFIG_BLK_DEV_RAM_SIZE=65536
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not setCONFIG_VIRTIO_BLK=y
# CONFIG_BLK_DEV_RBD is not set
# CONFIG_BLK_DEV_RSXX is not set
#
# NVME Support
#
# CONFIG_BLK_DEV_NVME is not set
# CONFIG_NVME_FC is not set
# CONFIG_NVME_TARGET is not set
# end of NVME Support
#
# Misc devices
#CONFIG_AD525X_DPOT=yCONFIG_AD525X_DPOT_I2C=y
# CONFIG_AD525X_DPOT_SPI is not setCONFIG_ATMEL_TCLIB=y
# CONFIG_DUMMY_IRQ is not set
# CONFIG_PHANTOM is not set
# CONFIG_TIFM_CORE is not setCONFIG_ICS932S401=yCONFIG_ATMEL_SSC=m
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_HP_ILO is not setCONFIG_QCOM_COINCELL=m
# CONFIG_QCOM_FASTRPC is not setCONFIG_APDS9802ALS=yCONFIG_ISL29003=y
# CONFIG_ISL29020 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_SENSORS_BH1770 is not set
# CONFIG_SENSORS_APDS990X is not set
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not set
# CONFIG_LATTICE_ECP3_CONFIG is not setCONFIG_SRAM=yCONFIG_SRAM_EXEC=yCONFIG_PCI_ENDPOINT_TEST=m
# CONFIG_XILINX_SDFEC is not set
# CONFIG_PVPANIC is not set
# CONFIG_HISI_HIKEY_USB is not set
# CONFIG_C2PORT is not set
#
# EEPROM support
#CONFIG_EEPROM_AT24=y
# CONFIG_EEPROM_AT25 is not set
# CONFIG_EEPROM_LEGACY is not set
# CONFIG_EEPROM_MAX6875 is not setCONFIG_EEPROM_93CX6=y
# CONFIG_EEPROM_93XX46 is not set
# CONFIG_EEPROM_IDT_89HPESX is not set
# CONFIG_EEPROM_EE1004 is not set
# end of EEPROM support
# CONFIG_CB710_CORE is not set
#
# Texas Instruments shared transport line discipline #
# CONFIG_TI_ST is not set
# end of Texas Instruments shared transport line discipline
# CONFIG_SENSORS_LIS3_SPI is not set
# CONFIG_SENSORS_LIS3_I2C is not set
# CONFIG_ALTERA_STAPL is not set
# CONFIG_ECHO is not set
# CONFIG_MISC_ALCOR_PCI is not set
# CONFIG_MISC_RTSX_PCI is not set
# CONFIG_MISC_RTSX_USB is not set
# CONFIG_HABANA_AI is not set
# CONFIG_UACCE is not set
# end of Misc devices
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not setCONFIG_SCSI=yCONFIG_SCSI_DMA=yCONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not setCONFIG_BLK_DEV_SR=y
# CONFIG_CHR_DEV_SG is not set
# CONFIG_CHR_DEV_SCH is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
# end of SCSI Transports
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_ISCSI_BOOT_SYSFS is not set
# CONFIG_SCSI_CXGB3_ISCSI is not set
# CONFIG_SCSI_CXGB4_ISCSI is not set
# CONFIG_SCSI_BNX2_ISCSI is not set
# CONFIG_BE2ISCSI is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_HPSA is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_3W_SAS is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_MVUMI is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_SCSI_ESAS2R is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_MPT3SAS is not set
# CONFIG_SCSI_MPT2SAS is not set
# CONFIG_SCSI_SMARTPQI is not set
# CONFIG_SCSI_UFSHCD is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_MYRB is not set
# CONFIG_SCSI_MYRS is not set
# CONFIG_SCSI_SNIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_FDOMAIN_PCI is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_WD719X is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_PMCRAID is not set
# CONFIG_SCSI_PM8001 is not setCONFIG_SCSI_VIRTIO=y
# CONFIG_SCSI_DH is not set
# end of SCSI device support
CONFIG_HAVE_PATA_PLATFORM=yCONFIG_ATA=yCONFIG_SATA_HOST=yCONFIG_ATA_VERBOSE_ERROR=yCONFIG_ATA_FORCE=yCONFIG_SATA_PMP=y
#
# Controllers with non-SFF native interface
#CONFIG_SATA_AHCI=yCONFIG_SATA_MOBILE_LPM_POLICY=0CONFIG_SATA_AHCI_PLATFORM=yCONFIG_AHCI_BRCM=yCONFIG_AHCI_DM816=yCONFIG_AHCI_ST=yCONFIG_AHCI_IMX=y
# CONFIG_AHCI_CEVA is not set
# CONFIG_AHCI_MTK is not set
# CONFIG_AHCI_MVEBU is not setCONFIG_AHCI_SUNXI=yCONFIG_AHCI_TEGRA=y
# CONFIG_AHCI_QORIQ is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_SATA_ACARD_AHCI is not set
# CONFIG_SATA_SIL24 is not setCONFIG_ATA_SFF=y
#
# SFF controllers with custom DMA interface
#
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_SX4 is not setCONFIG_ATA_BMDMA=y
#
# SATA SFF controllers with BMDMA
#
# CONFIG_ATA_PIIX is not set
# CONFIG_SATA_DWC is not setCONFIG_SATA_HIGHBANK=yCONFIG_SATA_MV=y
# CONFIG_SATA_NV is not set
# CONFIG_SATA_PROMISE is not setCONFIG_SATA_RCAR=y
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_SVW is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
#
# PATA SFF controllers with BMDMA
#
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARASAN_CF is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_ATP867X is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IMX is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RDC is not set
# CONFIG_PATA_SCH is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_TOSHIBA is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_PLATFORM is not set
# CONFIG_PATA_RZ1000 is not set
#
# Generic fallback / legacy drivers
#
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_LEGACY is not set
# CONFIG_MD is not set
# CONFIG_TARGET_CORE is not set
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
# CONFIG_FIREWIRE_NOSY is not set
# end of IEEE 1394 (FireWire) support
CONFIG_NETDEVICES=yCONFIG_MII=yCONFIG_NET_CORE=y
# CONFIG_BONDING is not set
# CONFIG_DUMMY is not set
# CONFIG_WIREGUARD is not set
# CONFIG_EQUALIZER is not set
# CONFIG_NET_FC is not set
# CONFIG_NET_TEAM is not set
# CONFIG_MACVLAN is not set
# CONFIG_IPVLAN is not set
# CONFIG_VXLAN is not set
# CONFIG_GENEVE is not set
# CONFIG_BAREUDP is not set
# CONFIG_GTP is not set
# CONFIG_MACSEC is not set
# CONFIG_NETCONSOLE is not setCONFIG_TUN=y
# CONFIG_TUN_VNET_CROSS_LE is not set
# CONFIG_VETH is not setCONFIG_VIRTIO_NET=y
# CONFIG_NLMON is not set
# CONFIG_ARCNET is not set
#
# Distributed Switch Architecture drivers
#CONFIG_B53=mCONFIG_B53_SPI_DRIVER=m CONFIG_B53_MDIO_DRIVER=m CONFIG_B53_MMAP_DRIVER=m CONFIG_B53_SRAB_DRIVER=mCONFIG_B53_SERDES=mCONFIG_NET_DSA_BCM_SF2=m
# CONFIG_NET_DSA_LOOP is not set
# CONFIG_NET_DSA_HIRSCHMANN_HELLCREEK is not set # CONFIG_NET_DSA_LANTIQ_GSWIP is not set
# CONFIG_NET_DSA_MT7530 is not set
# CONFIG_NET_DSA_MV88E6060 is not set
# CONFIG_NET_DSA_MICROCHIP_KSZ9477 is not set # CONFIG_NET_DSA_MICROCHIP_KSZ8795 is not set # CONFIG_NET_DSA_MV88E6XXX is not set
# CONFIG_NET_DSA_MSCC_FELIX is not set
# CONFIG_NET_DSA_MSCC_SEVILLE is not set
# CONFIG_NET_DSA_AR9331 is not set
# CONFIG_NET_DSA_SJA1105 is not set
# CONFIG_NET_DSA_QCA8K is not set
# CONFIG_NET_DSA_REALTEK_SMI is not set
# CONFIG_NET_DSA_SMSC_LAN9303_I2C is not set # CONFIG_NET_DSA_SMSC_LAN9303_MDIO is not set # CONFIG_NET_DSA_VITESSE_VSC73XX_SPI is not set # CONFIG_NET_DSA_VITESSE_VSC73XX_PLATFORM is not set
# end of Distributed Switch Architecture drivers
CONFIG_ETHERNET=yCONFIG_NET_VENDOR_3COM=y
# CONFIG_TYPHOON is not setCONFIG_NET_VENDOR_ADAPTEC=y
# CONFIG_ADAPTEC_STARFIRE is not setCONFIG_NET_VENDOR_AGERE=y
# CONFIG_ET131X is not setCONFIG_NET_VENDOR_ALACRITECH=y
# CONFIG_SLICOSS is not setCONFIG_NET_VENDOR_ALLWINNER=yCONFIG_SUN4I_EMAC=yCONFIG_NET_VENDOR_ALTEON=y
# CONFIG_ACENIC is not set
# CONFIG_ALTERA_TSE is not setCONFIG_NET_VENDOR_AMAZON=y
# CONFIG_ENA_ETHERNET is not setCONFIG_NET_VENDOR_AMD=y
# CONFIG_AMD8111_ETH is not set
# CONFIG_PCNET32 is not setCONFIG_NET_VENDOR_AQUANTIA=yCONFIG_NET_VENDOR_ARC=y
# CONFIG_EMAC_ROCKCHIP is not setCONFIG_NET_VENDOR_ATHEROS=y
# CONFIG_ATL2 is not set
# CONFIG_ATL1 is not set
# CONFIG_ATL1E is not set
# CONFIG_ATL1C is not set
# CONFIG_ALX is not setCONFIG_NET_VENDOR_AURORA=y
# CONFIG_AURORA_NB8800 is not setCONFIG_NET_VENDOR_BROADCOM=y
# CONFIG_B44 is not setCONFIG_BCMGENET=m
# CONFIG_BNX2 is not set
# CONFIG_CNIC is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2X is not setCONFIG_BGMAC=yCONFIG_BGMAC_BCMA=yCONFIG_BGMAC_PLATFORM=yCONFIG_SYSTEMPORT=m
# CONFIG_BNXT is not setCONFIG_NET_VENDOR_BROCADE=y
# CONFIG_BNA is not setCONFIG_NET_VENDOR_CADENCE=yCONFIG_MACB=yCONFIG_MACB_USE_HWSTAMP=y
# CONFIG_MACB_PCI is not setCONFIG_NET_CALXEDA_XGMAC=yCONFIG_NET_VENDOR_CAVIUM=yCONFIG_NET_VENDOR_CHELSIO=y
# CONFIG_CHELSIO_T1 is not set
# CONFIG_CHELSIO_T3 is not set
# CONFIG_CHELSIO_T4 is not set
# CONFIG_CHELSIO_T4VF is not setCONFIG_NET_VENDOR_CIRRUS=y
# CONFIG_CS89x0 is not setCONFIG_NET_VENDOR_CISCO=y
# CONFIG_ENIC is not setCONFIG_NET_VENDOR_CORTINA=y
# CONFIG_GEMINI_ETHERNET is not set
# CONFIG_DM9000 is not set
# CONFIG_DNET is not setCONFIG_NET_VENDOR_DEC=y
# CONFIG_NET_TULIP is not setCONFIG_NET_VENDOR_DLINK=y
# CONFIG_DL2K is not set
# CONFIG_SUNDANCE is not setCONFIG_NET_VENDOR_EMULEX=y
# CONFIG_BE2NET is not setCONFIG_NET_VENDOR_EZCHIP=y
# CONFIG_EZCHIP_NPS_MANAGEMENT_ENET is not setCONFIG_NET_VENDOR_FARADAY=y
# CONFIG_FTMAC100 is not setCONFIG_FTGMAC100=mCONFIG_NET_VENDOR_FREESCALE=yCONFIG_FEC=yCONFIG_FSL_PQ_MDIO=y
# CONFIG_FSL_XGMAC_MDIO is not setCONFIG_GIANFAR=y
# CONFIG_FSL_ENETC is not set
# CONFIG_FSL_ENETC_VF is not set
# CONFIG_FSL_ENETC_MDIO is not setCONFIG_NET_VENDOR_GOOGLE=y
# CONFIG_GVE is not setCONFIG_NET_VENDOR_HISILICON=yCONFIG_HIX5HD2_GMAC=y
# CONFIG_HISI_FEMAC is not set
# CONFIG_HIP04_ETH is not set
# CONFIG_HNS_DSAF is not set
# CONFIG_HNS_ENET is not set
# CONFIG_HNS3 is not setCONFIG_NET_VENDOR_HUAWEI=yCONFIG_NET_VENDOR_I825XX=yCONFIG_NET_VENDOR_INTEL=y
# CONFIG_E100 is not set
# CONFIG_E1000 is not setCONFIG_E1000E=yCONFIG_IGB=yCONFIG_IGB_HWMON=y
# CONFIG_IGBVF is not set
# CONFIG_IXGB is not set
# CONFIG_IXGBE is not set
# CONFIG_IXGBEVF is not set
# CONFIG_I40E is not set
# CONFIG_I40EVF is not set
# CONFIG_ICE is not set
# CONFIG_FM10K is not set
# CONFIG_IGC is not set
# CONFIG_JME is not setCONFIG_NET_VENDOR_MARVELL=yCONFIG_MV643XX_ETH=yCONFIG_MVMDIO=y
# CONFIG_MVNETA_BM_ENABLE is not setCONFIG_MVNETA=y
# CONFIG_MVPP2 is not setCONFIG_PXA168_ETH=m
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_NET_VENDOR_MEDIATEK is not setCONFIG_NET_VENDOR_MELLANOX=y
# CONFIG_MLX4_EN is not set
# CONFIG_MLX5_CORE is not set
# CONFIG_MLXSW_CORE is not set
# CONFIG_MLXFW is not setCONFIG_NET_VENDOR_MICREL=y
# CONFIG_KS8842 is not setCONFIG_KS8851=y
# CONFIG_KS8851_MLL is not set
# CONFIG_KSZ884X_PCI is not setCONFIG_NET_VENDOR_MICROCHIP=y
# CONFIG_ENC28J60 is not set
# CONFIG_ENCX24J600 is not set
# CONFIG_LAN743X is not setCONFIG_NET_VENDOR_MICROSEMI=y
# CONFIG_MSCC_OCELOT_SWITCH is not setCONFIG_NET_VENDOR_MYRI=y
# CONFIG_MYRI10GE is not set
# CONFIG_FEALNX is not setCONFIG_NET_VENDOR_NATSEMI=y
# CONFIG_NATSEMI is not set
# CONFIG_NS83820 is not setCONFIG_NET_VENDOR_NETERION=y
# CONFIG_S2IO is not set
# CONFIG_VXGE is not setCONFIG_NET_VENDOR_NETRONOME=y
# CONFIG_NFP is not setCONFIG_NET_VENDOR_NI=y
# CONFIG_NI_XGE_MANAGEMENT_ENET is not setCONFIG_NET_VENDOR_8390=y
# CONFIG_AX88796 is not set
# CONFIG_NE2K_PCI is not setCONFIG_NET_VENDOR_NVIDIA=y
# CONFIG_FORCEDETH is not setCONFIG_NET_VENDOR_OKI=y
# CONFIG_ETHOC is not setCONFIG_NET_VENDOR_PACKET_ENGINES=y
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not setCONFIG_NET_VENDOR_PENSANDO=yCONFIG_NET_VENDOR_QLOGIC=y
# CONFIG_QLA3XXX is not set
# CONFIG_QLCNIC is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_QED is not setCONFIG_NET_VENDOR_QUALCOMM=y
# CONFIG_QCA7000_SPI is not set
# CONFIG_QCA7000_UART is not set
# CONFIG_QCOM_EMAC is not set
# CONFIG_RMNET is not setCONFIG_NET_VENDOR_RDC=y
# CONFIG_R6040 is not setCONFIG_NET_VENDOR_REALTEK=y
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not setCONFIG_R8169=yCONFIG_NET_VENDOR_RENESAS=yCONFIG_SH_ETH=y
# CONFIG_RAVB is not setCONFIG_NET_VENDOR_ROCKER=yCONFIG_NET_VENDOR_SAMSUNG=y
# CONFIG_SXGBE_ETH is not setCONFIG_NET_VENDOR_SEEQ=yCONFIG_NET_VENDOR_SOLARFLARE=y
# CONFIG_SFC is not set
# CONFIG_SFC_FALCON is not setCONFIG_NET_VENDOR_SILAN=y
# CONFIG_SC92031 is not setCONFIG_NET_VENDOR_SIS=y
# CONFIG_SIS900 is not set
# CONFIG_SIS190 is not setCONFIG_NET_VENDOR_SMSC=y
# CONFIG_SMC91X is not set
# CONFIG_EPIC100 is not set
# CONFIG_SMC911X is not setCONFIG_SMSC911X=y
# CONFIG_SMSC9420 is not setCONFIG_NET_VENDOR_SOCIONEXT=yCONFIG_SNI_AVE=yCONFIG_NET_VENDOR_STMICRO=yCONFIG_STMMAC_ETH=y
# CONFIG_STMMAC_SELFTESTS is not setCONFIG_STMMAC_PLATFORM=yCONFIG_DWMAC_DWC_QOS_ETH=yCONFIG_DWMAC_GENERIC=yCONFIG_DWMAC_IPQ806X=y
# CONFIG_DWMAC_MEDIATEK is not setCONFIG_DWMAC_MESON=yCONFIG_DWMAC_QCOM_ETHQOS=yCONFIG_DWMAC_ROCKCHIP=yCONFIG_DWMAC_SOCFPGA=yCONFIG_DWMAC_STI=yCONFIG_DWMAC_STM32=yCONFIG_DWMAC_SUNXI=yCONFIG_DWMAC_SUN8I=yCONFIG_DWMAC_IMX8=y
# CONFIG_DWMAC_INTEL_PLAT is not set
# CONFIG_STMMAC_PCI is not setCONFIG_NET_VENDOR_SUN=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NIU is not setCONFIG_NET_VENDOR_SYNOPSYS=y
# CONFIG_DWC_XLGMAC is not setCONFIG_NET_VENDOR_TEHUTI=y
# CONFIG_TEHUTI is not setCONFIG_NET_VENDOR_TI=y
# CONFIG_TI_DAVINCI_EMAC is not setCONFIG_TI_DAVINCI_MDIO=y
# CONFIG_TI_CPSW_PHY_SEL is not setCONFIG_TI_CPSW=yCONFIG_TI_CPSW_SWITCHDEV=yCONFIG_TI_CPTS=y
# CONFIG_TLAN is not setCONFIG_NET_VENDOR_VIA=y
# CONFIG_VIA_RHINE is not set
# CONFIG_VIA_VELOCITY is not setCONFIG_NET_VENDOR_WIZNET=y
# CONFIG_WIZNET_W5100 is not set
# CONFIG_WIZNET_W5300 is not setCONFIG_NET_VENDOR_XILINX=yCONFIG_XILINX_EMACLITE=y
# CONFIG_XILINX_AXI_EMAC is not set
# CONFIG_XILINX_LL_TEMAC is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not setCONFIG_PHYLINK=yCONFIG_PHYLIB=yCONFIG_SWPHY=y
# CONFIG_LED_TRIGGER_PHY is not setCONFIG_FIXED_PHY=y
# CONFIG_SFP is not set
#
# MII PHY device drivers
#
# CONFIG_AMD_PHY is not set
# CONFIG_MESON_GXL_PHY is not set
# CONFIG_ADIN_PHY is not set
# CONFIG_AQUANTIA_PHY is not set
# CONFIG_AX88796B_PHY is not setCONFIG_BROADCOM_PHY=y
# CONFIG_BCM54140_PHY is not setCONFIG_BCM7XXX_PHY=m
# CONFIG_BCM84881_PHY is not set
# CONFIG_BCM87XX_PHY is not set
# CONFIG_BCM_CYGNUS_PHY is not setCONFIG_BCM_NET_PHYLIB=y
# CONFIG_CICADA_PHY is not set
# CONFIG_CORTINA_PHY is not set
# CONFIG_DAVICOM_PHY is not setCONFIG_ICPLUS_PHY=y
# CONFIG_LXT_PHY is not set
# CONFIG_INTEL_XWAY_PHY is not set
# CONFIG_LSI_ET1011C_PHY is not setCONFIG_MARVELL_PHY=y
# CONFIG_MARVELL_10G_PHY is not setCONFIG_MICREL_PHY=yCONFIG_MICROCHIP_PHY=m
# CONFIG_MICROCHIP_T1_PHY is not set
# CONFIG_MICROSEMI_PHY is not set
# CONFIG_NATIONAL_PHY is not set
# CONFIG_NXP_TJA11XX_PHY is not setCONFIG_AT803X_PHY=y
# CONFIG_QSEMI_PHY is not setCONFIG_REALTEK_PHY=y
# CONFIG_RENESAS_PHY is not setCONFIG_ROCKCHIP_PHY=yCONFIG_SMSC_PHY=y
# CONFIG_STE10XP is not set
# CONFIG_TERANETICS_PHY is not set
# CONFIG_DP83822_PHY is not set
# CONFIG_DP83TC811_PHY is not set
# CONFIG_DP83848_PHY is not setCONFIG_DP83867_PHY=y
# CONFIG_DP83869_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_XILINX_GMII2RGMII is not set
# CONFIG_MICREL_KS8995MA is not setCONFIG_MDIO_DEVICE=yCONFIG_MDIO_BUS=yCONFIG_OF_MDIO=yCONFIG_MDIO_DEVRES=yCONFIG_MDIO_SUN4I=yCONFIG_MDIO_ASPEED=mCONFIG_MDIO_BITBANG=yCONFIG_MDIO_BCM_IPROC=yCONFIG_MDIO_BCM_UNIMAC=m
# CONFIG_MDIO_GPIO is not set
# CONFIG_MDIO_HISI_FEMAC is not set
# CONFIG_MDIO_MVUSB is not set
# CONFIG_MDIO_MSCC_MIIM is not set
# CONFIG_MDIO_IPQ4019 is not set
# CONFIG_MDIO_IPQ8064 is not set
#
# MDIO Multiplexers
#CONFIG_MDIO_BUS_MUX=yCONFIG_MDIO_BUS_MUX_MESON_G12A=mCONFIG_MDIO_BUS_MUX_BCM_IPROC=y
# CONFIG_MDIO_BUS_MUX_GPIO is not set
# CONFIG_MDIO_BUS_MUX_MULTIPLEXER is not set
# CONFIG_MDIO_BUS_MUX_MMIOREG is not set
#
# PCS device drivers
#CONFIG_PCS_XPCS=y
# end of PCS device drivers
# CONFIG_PPP is not set
# CONFIG_SLIP is not setCONFIG_USB_NET_DRIVERS=y
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not setCONFIG_USB_PEGASUS=y
# CONFIG_USB_RTL8150 is not setCONFIG_USB_RTL8152=mCONFIG_USB_LAN78XX=mCONFIG_USB_USBNET=yCONFIG_USB_NET_AX8817X=yCONFIG_USB_NET_AX88179_178A=yCONFIG_USB_NET_CDCETHER=y
# CONFIG_USB_NET_CDC_EEM is not setCONFIG_USB_NET_CDC_NCM=y
# CONFIG_USB_NET_HUAWEI_CDC_NCM is not set
# CONFIG_USB_NET_CDC_MBIM is not set
# CONFIG_USB_NET_DM9601 is not set
# CONFIG_USB_NET_SR9700 is not set
# CONFIG_USB_NET_SR9800 is not setCONFIG_USB_NET_SMSC75XX=yCONFIG_USB_NET_SMSC95XX=y
# CONFIG_USB_NET_GL620A is not setCONFIG_USB_NET_NET1080=y
# CONFIG_USB_NET_PLUSB is not set
# CONFIG_USB_NET_MCS7830 is not set
# CONFIG_USB_NET_RNDIS_HOST is not setCONFIG_USB_NET_CDC_SUBSET_ENABLE=yCONFIG_USB_NET_CDC_SUBSET=y
# CONFIG_USB_ALI_M5632 is not set
# CONFIG_USB_AN2720 is not setCONFIG_USB_BELKIN=yCONFIG_USB_ARMLINUX=y
# CONFIG_USB_EPSON2888 is not set
# CONFIG_USB_KC2190 is not setCONFIG_USB_NET_ZAURUS=y
# CONFIG_USB_NET_CX82310_ETH is not set
# CONFIG_USB_NET_KALMIA is not set
# CONFIG_USB_NET_QMI_WWAN is not set
# CONFIG_USB_HSO is not set
# CONFIG_USB_NET_INT51X1 is not set
# CONFIG_USB_IPHETH is not set
# CONFIG_USB_SIERRA_NET is not set
# CONFIG_USB_VL600 is not set
# CONFIG_USB_NET_CH9200 is not set
# CONFIG_USB_NET_AQC111 is not setCONFIG_USB_RTL8153_ECM=mCONFIG_WLAN=yCONFIG_WLAN_VENDOR_ADMTEK=y
# CONFIG_ADM8211 is not setCONFIG_WLAN_VENDOR_ATH=y
# CONFIG_ATH_DEBUG is not set
# CONFIG_ATH5K is not set
# CONFIG_ATH5K_PCI is not set
# CONFIG_ATH9K is not set
# CONFIG_ATH9K_HTC is not set
# CONFIG_CARL9170 is not set
# CONFIG_ATH6KL is not set
# CONFIG_AR5523 is not set
# CONFIG_WIL6210 is not set
# CONFIG_ATH10K is not set
# CONFIG_WCN36XX is not setCONFIG_WLAN_VENDOR_ATMEL=y
# CONFIG_ATMEL is not set
# CONFIG_AT76C50X_USB is not setCONFIG_WLAN_VENDOR_BROADCOM=y
# CONFIG_B43 is not set
# CONFIG_B43LEGACY is not setCONFIG_BRCMUTIL=m
# CONFIG_BRCMSMAC is not setCONFIG_BRCMFMAC=mCONFIG_BRCMFMAC_PROTO_BCDC=yCONFIG_BRCMFMAC_SDIO=y
# CONFIG_BRCMFMAC_USB is not set
# CONFIG_BRCMFMAC_PCIE is not set
# CONFIG_BRCM_TRACING is not set
# CONFIG_BRCMDBG is not setCONFIG_WLAN_VENDOR_CISCO=yCONFIG_WLAN_VENDOR_INTEL=y
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not set
# CONFIG_IWL4965 is not set
# CONFIG_IWL3945 is not set
# CONFIG_IWLWIFI is not setCONFIG_WLAN_VENDOR_INTERSIL=y
# CONFIG_HOSTAP is not set
# CONFIG_HERMES is not set
# CONFIG_P54_COMMON is not set
# CONFIG_PRISM54 is not setCONFIG_WLAN_VENDOR_MARVELL=y
# CONFIG_LIBERTAS is not set
# CONFIG_LIBERTAS_THINFIRM is not setCONFIG_MWIFIEX=mCONFIG_MWIFIEX_SDIO=m
# CONFIG_MWIFIEX_PCIE is not set
# CONFIG_MWIFIEX_USB is not set
# CONFIG_MWL8K is not setCONFIG_WLAN_VENDOR_MEDIATEK=y
# CONFIG_MT7601U is not set
# CONFIG_MT76x0U is not set
# CONFIG_MT76x0E is not set
# CONFIG_MT76x2E is not set
# CONFIG_MT76x2U is not set
# CONFIG_MT7603E is not set
# CONFIG_MT7615E is not set
# CONFIG_MT7663U is not set
# CONFIG_MT7663S is not set
# CONFIG_MT7915E is not setCONFIG_WLAN_VENDOR_MICROCHIP=y
# CONFIG_WILC1000_SDIO is not set
# CONFIG_WILC1000_SPI is not setCONFIG_WLAN_VENDOR_RALINK=yCONFIG_RT2X00=m
# CONFIG_RT2400PCI is not set
# CONFIG_RT2500PCI is not set
# CONFIG_RT61PCI is not set
# CONFIG_RT2800PCI is not set
# CONFIG_RT2500USB is not set
# CONFIG_RT73USB is not setCONFIG_RT2800USB=mCONFIG_RT2800USB_RT33XX=yCONFIG_RT2800USB_RT35XX=y
# CONFIG_RT2800USB_RT3573 is not set
# CONFIG_RT2800USB_RT53XX is not set
# CONFIG_RT2800USB_RT55XX is not set
# CONFIG_RT2800USB_UNKNOWN is not setCONFIG_RT2800_LIB=mCONFIG_RT2X00_LIB_USB=mCONFIG_RT2X00_LIB=mCONFIG_RT2X00_LIB_FIRMWARE=yCONFIG_RT2X00_LIB_CRYPTO=yCONFIG_RT2X00_LIB_LEDS=y
# CONFIG_RT2X00_DEBUG is not setCONFIG_WLAN_VENDOR_REALTEK=y
# CONFIG_RTL8180 is not set
# CONFIG_RTL8187 is not setCONFIG_RTL_CARDS=m
# CONFIG_RTL8192CE is not set
# CONFIG_RTL8192SE is not set
# CONFIG_RTL8192DE is not set
# CONFIG_RTL8723AE is not set
# CONFIG_RTL8723BE is not set
# CONFIG_RTL8188EE is not set
# CONFIG_RTL8192EE is not set
# CONFIG_RTL8821AE is not set
# CONFIG_RTL8192CU is not set
# CONFIG_RTL8XXXU is not set
# CONFIG_RTW88 is not setCONFIG_WLAN_VENDOR_RSI=y
# CONFIG_RSI_91X is not setCONFIG_WLAN_VENDOR_ST=y
# CONFIG_CW1200 is not setCONFIG_WLAN_VENDOR_TI=y
# CONFIG_WL1251 is not set
# CONFIG_WL12XX is not set
# CONFIG_WL18XX is not set
# CONFIG_WLCORE is not setCONFIG_WLAN_VENDOR_ZYDAS=y
# CONFIG_USB_ZD1201 is not set
# CONFIG_ZD1211RW is not setCONFIG_WLAN_VENDOR_QUANTENNA=y
# CONFIG_QTNFMAC_PCIE is not set
# CONFIG_MAC80211_HWSIM is not set
# CONFIG_USB_NET_RNDIS_WLAN is not set
# CONFIG_VIRT_WIFI is not set
# CONFIG_WAN is not set
# CONFIG_VMXNET3 is not set
# CONFIG_NETDEVSIM is not setCONFIG_NET_FAILOVER=y
# CONFIG_ISDN is not set
# CONFIG_NVM is not set
#
# Input device support
#CONFIG_INPUT=yCONFIG_INPUT_LEDS=yCONFIG_INPUT_FF_MEMLESS=m
# CONFIG_INPUT_SPARSEKMAP is not setCONFIG_INPUT_MATRIXKMAP=y
#
# Userland interfaces
#
# CONFIG_INPUT_MOUSEDEV is not setCONFIG_INPUT_JOYDEV=yCONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADC is not set
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not setCONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT1050 is not setCONFIG_KEYBOARD_QT1070=m
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_DLINK_DIR685 is not set
# CONFIG_KEYBOARD_LKKBD is not setCONFIG_KEYBOARD_GPIO=y
# CONFIG_KEYBOARD_GPIO_POLLED is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_TCA8418 is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_LM8333 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_SNVS_PWRKEY is not set
# CONFIG_KEYBOARD_IMX is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_NOMADIK is not setCONFIG_KEYBOARD_TEGRA=y
# CONFIG_KEYBOARD_OPENCORES is not set
CONFIG_KEYBOARD_PXA27x=m
# CONFIG_KEYBOARD_PMIC8XXX is not setCONFIG_KEYBOARD_SAMSUNG=m
# CONFIG_KEYBOARD_STOWAWAY is not setCONFIG_KEYBOARD_ST_KEYSCAN=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_STMPE is not set
# CONFIG_KEYBOARD_SUN4I_LRADC is not set
# CONFIG_KEYBOARD_OMAP4 is not setCONFIG_KEYBOARD_SPEAR=y
# CONFIG_KEYBOARD_TM2_TOUCHKEY is not set
# CONFIG_KEYBOARD_TWL4030 is not set
# CONFIG_KEYBOARD_XTKBD is not setCONFIG_KEYBOARD_CROS_EC=m
# CONFIG_KEYBOARD_CAP11XX is not setCONFIG_KEYBOARD_BCM=yCONFIG_INPUT_MOUSE=yCONFIG_MOUSE_PS2=yCONFIG_MOUSE_PS2_ALPS=yCONFIG_MOUSE_PS2_BYD=yCONFIG_MOUSE_PS2_LOGIPS2PP=yCONFIG_MOUSE_PS2_SYNAPTICS=yCONFIG_MOUSE_PS2_SYNAPTICS_SMBUS=yCONFIG_MOUSE_PS2_CYPRESS=yCONFIG_MOUSE_PS2_TRACKPOINT=yCONFIG_MOUSE_PS2_ELANTECH=yCONFIG_MOUSE_PS2_ELANTECH_SMBUS=y
# CONFIG_MOUSE_PS2_SENTELIC is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not setCONFIG_MOUSE_PS2_FOCALTECH=yCONFIG_MOUSE_PS2_SMBUS=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not setCONFIG_MOUSE_CYAPA=mCONFIG_MOUSE_ELAN_I2C=yCONFIG_MOUSE_ELAN_I2C_I2C=y
# CONFIG_MOUSE_ELAN_I2C_SMBUS is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_GPIO is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
# CONFIG_MOUSE_SYNAPTICS_USB is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not setCONFIG_INPUT_TOUCHSCREEN=yCONFIG_TOUCHSCREEN_PROPERTIES=y
# CONFIG_TOUCHSCREEN_ADS7846 is not set
# CONFIG_TOUCHSCREEN_AD7877 is not set
# CONFIG_TOUCHSCREEN_AD7879 is not setCONFIG_TOUCHSCREEN_ADC=m
# CONFIG_TOUCHSCREEN_AR1021_I2C is not setCONFIG_TOUCHSCREEN_ATMEL_MXT=m
# CONFIG_TOUCHSCREEN_ATMEL_MXT_T37 is not set
# CONFIG_TOUCHSCREEN_AUO_PIXCIR is not set
# CONFIG_TOUCHSCREEN_BU21013 is not set
# CONFIG_TOUCHSCREEN_BU21029 is not set
# CONFIG_TOUCHSCREEN_CHIPONE_ICN8318 is not set
# CONFIG_TOUCHSCREEN_CY8CTMA140 is not set
# CONFIG_TOUCHSCREEN_CY8CTMG110 is not set
# CONFIG_TOUCHSCREEN_CYTTSP_CORE is not set
# CONFIG_TOUCHSCREEN_CYTTSP4_CORE is not set
# CONFIG_TOUCHSCREEN_DYNAPRO is not set
# CONFIG_TOUCHSCREEN_HAMPSHIRE is not set
# CONFIG_TOUCHSCREEN_EETI is not set
# CONFIG_TOUCHSCREEN_EGALAX is not set
# CONFIG_TOUCHSCREEN_EGALAX_SERIAL is not set
# CONFIG_TOUCHSCREEN_EXC3000 is not set
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_GOODIX is not set
# CONFIG_TOUCHSCREEN_HIDEEP is not set
# CONFIG_TOUCHSCREEN_ILI210X is not set
# CONFIG_TOUCHSCREEN_IPROC is not set
# CONFIG_TOUCHSCREEN_S6SY761 is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
# CONFIG_TOUCHSCREEN_EKTF2127 is not setCONFIG_TOUCHSCREEN_ELAN=m
# CONFIG_TOUCHSCREEN_ELO is not set
# CONFIG_TOUCHSCREEN_WACOM_W8001 is not set
# CONFIG_TOUCHSCREEN_WACOM_I2C is not set
# CONFIG_TOUCHSCREEN_MAX11801 is not set
# CONFIG_TOUCHSCREEN_MCS5000 is not setCONFIG_TOUCHSCREEN_MMS114=m
# CONFIG_TOUCHSCREEN_MELFAS_MIP4 is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_IMX6UL_TSC is not set
# CONFIG_TOUCHSCREEN_INEXIO is not set
# CONFIG_TOUCHSCREEN_MK712 is not set
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_EDT_FT5X06 is not set
# CONFIG_TOUCHSCREEN_RASPBERRYPI_FW is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_PIXCIR is not set
# CONFIG_TOUCHSCREEN_WDT87XX_I2C is not setCONFIG_TOUCHSCREEN_WM97XX=mCONFIG_TOUCHSCREEN_WM9705=yCONFIG_TOUCHSCREEN_WM9712=yCONFIG_TOUCHSCREEN_WM9713=y
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
# CONFIG_TOUCHSCREEN_TS4800 is not set
# CONFIG_TOUCHSCREEN_TSC_SERIO is not set
# CONFIG_TOUCHSCREEN_TSC2004 is not set
# CONFIG_TOUCHSCREEN_TSC2005 is not set
# CONFIG_TOUCHSCREEN_TSC2007 is not set
# CONFIG_TOUCHSCREEN_RM_TS is not set
# CONFIG_TOUCHSCREEN_SILEAD is not set
# CONFIG_TOUCHSCREEN_SIS_I2C is not setCONFIG_TOUCHSCREEN_ST1232=m
# CONFIG_TOUCHSCREEN_STMFTS is not setCONFIG_TOUCHSCREEN_STMPE=yCONFIG_TOUCHSCREEN_SUN4I=y
# CONFIG_TOUCHSCREEN_SUR40 is not set
# CONFIG_TOUCHSCREEN_SURFACE3_SPI is not set
# CONFIG_TOUCHSCREEN_SX8654 is not set
# CONFIG_TOUCHSCREEN_TPS6507X is not set
# CONFIG_TOUCHSCREEN_ZET6223 is not set
# CONFIG_TOUCHSCREEN_ZFORCE is not set
# CONFIG_TOUCHSCREEN_COLIBRI_VF50 is not set
# CONFIG_TOUCHSCREEN_ROHM_BU21023 is not set
# CONFIG_TOUCHSCREEN_IQS5XX is not set
# CONFIG_TOUCHSCREEN_ZINITIX is not setCONFIG_INPUT_MISC=y
# CONFIG_INPUT_AB8500_PONKEY is not set
# CONFIG_INPUT_AD714X is not set
# CONFIG_INPUT_ARIEL_PWRBUTTON is not set
# CONFIG_INPUT_ATMEL_CAPTOUCH is not set
# CONFIG_INPUT_BMA150 is not set
# CONFIG_INPUT_E3X0_BUTTON is not set
# CONFIG_INPUT_PM8941_PWRKEY is not set
# CONFIG_INPUT_PM8XXX_VIBRATOR is not set
# CONFIG_INPUT_PMIC8XXX_PWRKEY is not setCONFIG_INPUT_MAX77693_HAPTIC=mCONFIG_INPUT_MAX8997_HAPTIC=m
# CONFIG_INPUT_MMA8450 is not set
# CONFIG_INPUT_GPIO_BEEPER is not set
# CONFIG_INPUT_GPIO_DECODER is not set
# CONFIG_INPUT_GPIO_VIBRA is not setCONFIG_INPUT_CPCAP_PWRBUTTON=m
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_KXTJ9 is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
# CONFIG_INPUT_CM109 is not set
# CONFIG_INPUT_REGULATOR_HAPTIC is not set
# CONFIG_INPUT_TPS65218_PWRBUTTON is not setCONFIG_INPUT_AXP20X_PEK=m
# CONFIG_INPUT_TWL4030_PWRBUTTON is not set
# CONFIG_INPUT_TWL4030_VIBRA is not set
# CONFIG_INPUT_UINPUT is not set
# CONFIG_INPUT_PALMAS_PWRBUTTON is not set
# CONFIG_INPUT_PCF8574 is not set
# CONFIG_INPUT_PWM_BEEPER is not set
# CONFIG_INPUT_PWM_VIBRA is not set
# CONFIG_INPUT_RK805_PWRKEY is not set
# CONFIG_INPUT_GPIO_ROTARY_ENCODER is not setCONFIG_INPUT_DA9063_ONKEY=mCONFIG_INPUT_ADXL34X=mCONFIG_INPUT_ADXL34X_I2C=mCONFIG_INPUT_ADXL34X_SPI=m
# CONFIG_INPUT_IMS_PCU is not set
# CONFIG_INPUT_IQS269A is not set
# CONFIG_INPUT_CMA3000 is not setCONFIG_INPUT_SIRFSOC_ONKEY=y
# CONFIG_INPUT_DRV260X_HAPTICS is not set
# CONFIG_INPUT_DRV2665_HAPTICS is not set
# CONFIG_INPUT_DRV2667_HAPTICS is not set
# CONFIG_INPUT_HISI_POWERKEY is not setCONFIG_INPUT_STPMIC1_ONKEY=y
# CONFIG_RMI4_CORE is not set
#
# Hardware I/O ports
#CONFIG_SERIO=yCONFIG_SERIO_SERPORT=yCONFIG_SERIO_AMBAKMI=y
# CONFIG_SERIO_PCIPS2 is not setCONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_SERIO_ALTERA_PS2 is not set
# CONFIG_SERIO_PS2MULT is not set
# CONFIG_SERIO_ARC_PS2 is not set
# CONFIG_SERIO_APBPS2 is not set
# CONFIG_SERIO_OLPC_APSP is not set
# CONFIG_SERIO_SUN4I_PS2 is not set
# CONFIG_SERIO_GPIO_PS2 is not set
# CONFIG_USERIO is not set
# CONFIG_GAMEPORT is not set
# end of Hardware I/O ports # end of Input device support
#
# Character devices
#CONFIG_TTY=yCONFIG_VT=yCONFIG_CONSOLE_TRANSLATIONS=yCONFIG_VT_CONSOLE=yCONFIG_VT_CONSOLE_SLEEP=yCONFIG_HW_CONSOLE=yCONFIG_VT_HW_CONSOLE_BINDING=yCONFIG_UNIX98_PTYS=yCONFIG_LEGACY_PTYS=yCONFIG_LEGACY_PTY_COUNT=256CONFIG_LDISC_AUTOLOAD=y
#
# Serial drivers
#CONFIG_SERIAL_EARLYCON=yCONFIG_SERIAL_8250=yCONFIG_SERIAL_8250_DEPRECATED_OPTIONS=yCONFIG_SERIAL_8250_16550A_VARIANTS=y
# CONFIG_SERIAL_8250_FINTEK is not setCONFIG_SERIAL_8250_CONSOLE=yCONFIG_SERIAL_8250_DMA=yCONFIG_SERIAL_8250_PCI=yCONFIG_SERIAL_8250_EXAR=yCONFIG_SERIAL_8250_NR_UARTS=5CONFIG_SERIAL_8250_RUNTIME_UARTS=5CONFIG_SERIAL_8250_EXTENDED=yCONFIG_SERIAL_8250_MANY_PORTS=yCONFIG_SERIAL_8250_ASPEED_VUART=mCONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
# CONFIG_SERIAL_8250_RSA is not setCONFIG_SERIAL_8250_DWLIB=yCONFIG_SERIAL_8250_BCM2835AUX=yCONFIG_SERIAL_8250_FSL=yCONFIG_SERIAL_8250_DW=yCONFIG_SERIAL_8250_EM=y
# CONFIG_SERIAL_8250_RT288X is not setCONFIG_SERIAL_8250_OMAP=yCONFIG_SERIAL_8250_OMAP_TTYO_FIXUP=yCONFIG_SERIAL_8250_MT6577=yCONFIG_SERIAL_8250_UNIPHIER=y
# CONFIG_SERIAL_8250_PXA is not setCONFIG_SERIAL_8250_TEGRA=yCONFIG_SERIAL_OF_PLATFORM=y
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_AMBA_PL010 is not setCONFIG_SERIAL_AMBA_PL011=yCONFIG_SERIAL_AMBA_PL011_CONSOLE=y
# CONFIG_SERIAL_EARLYCON_ARM_SEMIHOST is not setCONFIG_SERIAL_ATMEL=yCONFIG_SERIAL_ATMEL_CONSOLE=yCONFIG_SERIAL_ATMEL_PDC=yCONFIG_SERIAL_ATMEL_TTYAT=yCONFIG_SERIAL_MESON=yCONFIG_SERIAL_MESON_CONSOLE=yCONFIG_SERIAL_SAMSUNG=yCONFIG_SERIAL_SAMSUNG_UARTS_4=yCONFIG_SERIAL_SAMSUNG_UARTS=4CONFIG_SERIAL_SAMSUNG_CONSOLE=yCONFIG_SERIAL_SIRFSOC=yCONFIG_SERIAL_SIRFSOC_CONSOLE=yCONFIG_SERIAL_TEGRA=y
# CONFIG_SERIAL_MAX3100 is not set
# CONFIG_SERIAL_MAX310X is not set
# CONFIG_SERIAL_PXA is not setCONFIG_SERIAL_IMX=yCONFIG_SERIAL_IMX_CONSOLE=yCONFIG_SERIAL_IMX_EARLYCON=y
# CONFIG_SERIAL_UARTLITE is not setCONFIG_SERIAL_SH_SCI=yCONFIG_SERIAL_SH_SCI_NR_UARTS=20CONFIG_SERIAL_SH_SCI_CONSOLE=yCONFIG_SERIAL_SH_SCI_EARLYCON=yCONFIG_SERIAL_SH_SCI_DMA=yCONFIG_SERIAL_CORE=yCONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not setCONFIG_SERIAL_MSM=yCONFIG_SERIAL_MSM_CONSOLE=yCONFIG_SERIAL_VT8500=yCONFIG_SERIAL_VT8500_CONSOLE=yCONFIG_SERIAL_OMAP=yCONFIG_SERIAL_OMAP_CONSOLE=y
# CONFIG_SERIAL_SIFIVE is not set
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_SC16IS7XX is not setCONFIG_SERIAL_BCM63XX=yCONFIG_SERIAL_BCM63XX_CONSOLE=y
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_IFX6X60 is not setCONFIG_SERIAL_XILINX_PS_UART=yCONFIG_SERIAL_XILINX_PS_UART_CONSOLE=y
# CONFIG_SERIAL_ARC is not set
# CONFIG_SERIAL_RP2 is not setCONFIG_SERIAL_FSL_LPUART=yCONFIG_SERIAL_FSL_LPUART_CONSOLE=y
# CONFIG_SERIAL_FSL_LINFLEXUART is not setCONFIG_SERIAL_CONEXANT_DIGICOLOR=yCONFIG_SERIAL_CONEXANT_DIGICOLOR_CONSOLE=yCONFIG_SERIAL_ST_ASC=yCONFIG_SERIAL_ST_ASC_CONSOLE=y
# CONFIG_SERIAL_SPRD is not setCONFIG_SERIAL_STM32=yCONFIG_SERIAL_STM32_CONSOLE=y
# CONFIG_SERIAL_MVEBU_UART is not setCONFIG_SERIAL_MILBEAUT_USIO=yCONFIG_SERIAL_MILBEAUT_USIO_PORTS=4CONFIG_SERIAL_MILBEAUT_USIO_CONSOLE=y
# end of Serial drivers
CONFIG_SERIAL_MCTRL_GPIO=y
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_N_GSM is not set
# CONFIG_NOZOMI is not set
# CONFIG_TRACE_SINK is not setCONFIG_HVC_DRIVER=y
# CONFIG_HVC_DCC is not setCONFIG_SERIAL_DEV_BUS=yCONFIG_SERIAL_DEV_CTRL_TTYPORT=y
# CONFIG_TTY_PRINTK is not setCONFIG_VIRTIO_CONSOLE=y
# CONFIG_IPMI_HANDLER is not setCONFIG_IPMI_KCS_BMC=mCONFIG_ASPEED_KCS_IPMI_BMC=mCONFIG_ASPEED_BT_IPMI_BMC=m
# CONFIG_IPMB_DEVICE_INTERFACE is not setCONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_TIMERIOMEM is not setCONFIG_HW_RANDOM_ATMEL=y
# CONFIG_HW_RANDOM_BA431 is not setCONFIG_HW_RANDOM_BCM2835=yCONFIG_HW_RANDOM_IPROC_RNG200=yCONFIG_HW_RANDOM_OMAP=yCONFIG_HW_RANDOM_OMAP3_ROM=y
# CONFIG_HW_RANDOM_VIRTIO is not setCONFIG_HW_RANDOM_IMX_RNGC=yCONFIG_HW_RANDOM_HISI=yCONFIG_HW_RANDOM_ST=yCONFIG_HW_RANDOM_STM32=yCONFIG_HW_RANDOM_MESON=yCONFIG_HW_RANDOM_MTK=yCONFIG_HW_RANDOM_EXYNOS=yCONFIG_HW_RANDOM_KEYSTONE=y
# CONFIG_HW_RANDOM_CCTRNG is not set
# CONFIG_HW_RANDOM_XIPHERA is not set
# CONFIG_APPLICOM is not setCONFIG_DEVMEM=y
# CONFIG_DEVKMEM is not set
# CONFIG_RAW_DRIVER is not setCONFIG_DEVPORT=yCONFIG_TCG_TPM=mCONFIG_HW_RANDOM_TPM=y
# CONFIG_TCG_TIS is not set
# CONFIG_TCG_TIS_SPI is not set
# CONFIG_TCG_TIS_I2C_ATMEL is not setCONFIG_TCG_TIS_I2C_INFINEON=m
# CONFIG_TCG_TIS_I2C_NUVOTON is not set
# CONFIG_TCG_VTPM_PROXY is not set
# CONFIG_TCG_TIS_ST33ZP24_I2C is not set
# CONFIG_TCG_TIS_ST33ZP24_SPI is not set
# CONFIG_XILLYBUS is not set
# end of Character devices
# CONFIG_RANDOM_TRUST_BOOTLOADER is not set
#
# I2C support
#CONFIG_I2C=yCONFIG_I2C_BOARDINFO=yCONFIG_I2C_COMPAT=yCONFIG_I2C_CHARDEV=yCONFIG_I2C_MUX=y
#
# Multiplexer I2C Chip support
#CONFIG_I2C_ARB_GPIO_CHALLENGE=m
# CONFIG_I2C_MUX_GPIO is not set
# CONFIG_I2C_MUX_GPMUX is not set
# CONFIG_I2C_MUX_LTC4306 is not set
# CONFIG_I2C_MUX_PCA9541 is not set
CONFIG_I2C_MUX_PCA954x=yCONFIG_I2C_MUX_PINCTRL=y
# CONFIG_I2C_MUX_REG is not setCONFIG_I2C_DEMUX_PINCTRL=y
# CONFIG_I2C_MUX_MLXCPLD is not set
# end of Multiplexer I2C Chip support
CONFIG_I2C_HELPER_AUTO=yCONFIG_I2C_SMBUS=yCONFIG_I2C_ALGOBIT=y
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_HIX5HD2 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_ISCH is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_NVIDIA_GPU is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
#
# I2C system bus drivers (mostly embedded / system-on-chip) #
# CONFIG_I2C_ALTERA is not setCONFIG_I2C_ASPEED=mCONFIG_I2C_AT91=m
# CONFIG_I2C_AT91_SLAVE_EXPERIMENTAL is not set CONFIG_I2C_BCM2835=yCONFIG_I2C_BCM_IPROC=yCONFIG_I2C_BCM_KONA=yCONFIG_I2C_BRCMSTB=yCONFIG_I2C_CADENCE=y
# CONFIG_I2C_CBUS_GPIO is not set CONFIG_I2C_DAVINCI=yCONFIG_I2C_DESIGNWARE_CORE=y
# CONFIG_I2C_DESIGNWARE_SLAVE is not set CONFIG_I2C_DESIGNWARE_PLATFORM=y
# CONFIG_I2C_DESIGNWARE_PCI is not set CONFIG_I2C_DIGICOLOR=mCONFIG_I2C_EMEV2=mCONFIG_I2C_EXYNOS5=yCONFIG_I2C_GPIO=m
# CONFIG_I2C_GPIO_FAULT_INJECTOR is not set CONFIG_I2C_IMX=y
# CONFIG_I2C_IMX_LPI2C is not set CONFIG_I2C_MESON=y
# CONFIG_I2C_MT65XX is not set CONFIG_I2C_MV64XXX=yCONFIG_I2C_NOMADIK=y
# CONFIG_I2C_OCORES is not setCONFIG_I2C_OMAP=y
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_PXA is not set
# CONFIG_I2C_QCOM_CCI is not set
# CONFIG_I2C_QUP is not setCONFIG_I2C_RIIC=yCONFIG_I2C_RK3X=yCONFIG_HAVE_S3C2410_I2C=yCONFIG_I2C_S3C2410=yCONFIG_I2C_SH_MOBILE=y
# CONFIG_I2C_SIMTEC is not setCONFIG_I2C_SIRF=yCONFIG_I2C_ST=y
# CONFIG_I2C_STM32F4 is not set CONFIG_I2C_STM32F7=yCONFIG_I2C_SUN6I_P2WI=yCONFIG_I2C_TEGRA=yCONFIG_I2C_UNIPHIER=yCONFIG_I2C_UNIPHIER_F=y
# CONFIG_I2C_VERSATILE is not set
# CONFIG_I2C_WMT is not setCONFIG_I2C_XILINX=yCONFIG_I2C_RCAR=y
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_DIOLAN_U2C is not set
# CONFIG_I2C_ROBOTFUZZ_OSIF is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set
#
# Other I2C/SMBus bus drivers
#CONFIG_I2C_CROS_EC_TUNNEL=m
# CONFIG_I2C_FSI is not set
# end of I2C Hardware Bus support
# CONFIG_I2C_STUB is not setCONFIG_I2C_SLAVE=yCONFIG_I2C_SLAVE_EEPROM=y
# CONFIG_I2C_SLAVE_TESTUNIT is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# end of I2C support
# CONFIG_I3C is not setCONFIG_SPI=y
# CONFIG_SPI_DEBUG is not setCONFIG_SPI_MASTER=yCONFIG_SPI_MEM=y
#
# SPI Master Controller Drivers
#
# CONFIG_SPI_ALTERA is not set
# CONFIG_SPI_ARMADA_3700 is not setCONFIG_SPI_ATMEL=m
# CONFIG_SPI_AT91_USART is not set
# CONFIG_SPI_ATMEL_QUADSPI is not set
# CONFIG_SPI_AXI_SPI_ENGINE is not setCONFIG_SPI_BCM2835=yCONFIG_SPI_BCM2835AUX=y
# CONFIG_SPI_BCM63XX_HSSPI is not setCONFIG_SPI_BCM_QSPI=yCONFIG_SPI_BITBANG=yCONFIG_SPI_CADENCE=y
# CONFIG_SPI_CADENCE_QUADSPI is not setCONFIG_SPI_DAVINCI=y
# CONFIG_SPI_DESIGNWARE is not set
# CONFIG_SPI_FSI is not set
# CONFIG_SPI_FSL_LPSPI is not setCONFIG_SPI_FSL_QUADSPI=m
# CONFIG_SPI_NXP_FLEXSPI is not setCONFIG_SPI_GPIO=m
# CONFIG_SPI_IMX is not set
# CONFIG_SPI_FSL_SPI is not setCONFIG_SPI_FSL_DSPI=m
# CONFIG_SPI_MESON_SPICC is not set
# CONFIG_SPI_MESON_SPIFC is not set
# CONFIG_SPI_MT65XX is not set
# CONFIG_SPI_MTK_NOR is not set
# CONFIG_SPI_OC_TINY is not setCONFIG_SPI_OMAP24XX=y
# CONFIG_SPI_TI_QSPI is not setCONFIG_SPI_ORION=yCONFIG_SPI_PL022=y
# CONFIG_SPI_PXA2XX is not setCONFIG_SPI_ROCKCHIP=mCONFIG_SPI_RSPI=y
# CONFIG_SPI_QCOM_QSPI is not set
# CONFIG_SPI_QUP is not setCONFIG_SPI_S3C64XX=m
# CONFIG_SPI_SC18IS602 is not setCONFIG_SPI_SH_MSIOF=mCONFIG_SPI_SH_HSPI=y
# CONFIG_SPI_SIFIVE is not setCONFIG_SPI_SIRF=yCONFIG_SPI_STM32=mCONFIG_SPI_STM32_QSPI=y
# CONFIG_SPI_ST_SSC4 is not setCONFIG_SPI_SUN4I=yCONFIG_SPI_SUN6I=y
# CONFIG_SPI_MXIC is not setCONFIG_SPI_TEGRA114=yCONFIG_SPI_TEGRA20_SFLASH=yCONFIG_SPI_TEGRA20_SLINK=y
# CONFIG_SPI_UNIPHIER is not set
# CONFIG_SPI_XCOMM is not setCONFIG_SPI_XILINX=y
# CONFIG_SPI_ZYNQ_QSPI is not set
# CONFIG_SPI_ZYNQMP_GQSPI is not set
# CONFIG_SPI_AMD is not set
#
# SPI Multiplexer support
#
# CONFIG_SPI_MUX is not set
#
# SPI Protocol Masters
#CONFIG_SPI_SPIDEV=y
# CONFIG_SPI_LOOPBACK_TEST is not set
# CONFIG_SPI_TLE62X0 is not set
# CONFIG_SPI_SLAVE is not setCONFIG_SPI_DYNAMIC=yCONFIG_SPMI=yCONFIG_SPMI_MSM_PMIC_ARB=y
# CONFIG_HSI is not setCONFIG_PPS=y
# CONFIG_PPS_DEBUG is not set
#
# PPS clients support
#
# CONFIG_PPS_CLIENT_KTIMER is not set
# CONFIG_PPS_CLIENT_LDISC is not set
# CONFIG_PPS_CLIENT_GPIO is not set
#
# PPS generators support
#
#
# PTP clock support
#CONFIG_PTP_1588_CLOCK=yCONFIG_PTP_1588_CLOCK_DTE=yCONFIG_PTP_1588_CLOCK_QORIQ=y
#
# Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks. #
# CONFIG_PTP_1588_CLOCK_IDT82P33 is not set
# CONFIG_PTP_1588_CLOCK_IDTCM is not set
# CONFIG_PTP_1588_CLOCK_OCP is not set
# end of PTP clock support
CONFIG_PINCTRL=yCONFIG_GENERIC_PINCTRL_GROUPS=yCONFIG_PINMUX=yCONFIG_GENERIC_PINMUX_FUNCTIONS=yCONFIG_PINCONF=yCONFIG_GENERIC_PINCONF=y
# CONFIG_DEBUG_PINCTRL is not set
# CONFIG_PINCTRL_ARTPEC6 is not setCONFIG_PINCTRL_AS3722=y
# CONFIG_PINCTRL_AXP209 is not setCONFIG_PINCTRL_AT91=yCONFIG_PINCTRL_AT91PIO4=yCONFIG_PINCTRL_DIGICOLOR=y
# CONFIG_PINCTRL_MCP23S08 is not setCONFIG_PINCTRL_ROCKCHIP=yCONFIG_PINCTRL_SINGLE=yCONFIG_PINCTRL_SIRF=y
# CONFIG_PINCTRL_SX150X is not setCONFIG_PINCTRL_ST=yCONFIG_PINCTRL_STMFX=yCONFIG_PINCTRL_PALMAS=yCONFIG_PINCTRL_ZYNQ=y
# CONFIG_PINCTRL_RK805 is not set
# CONFIG_PINCTRL_OCELOT is not set
# CONFIG_PINCTRL_MICROCHIP_SGPIO is not setCONFIG_PINCTRL_ASPEED=yCONFIG_PINCTRL_ASPEED_G6=yCONFIG_PINCTRL_BCM281XX=yCONFIG_PINCTRL_BCM2835=yCONFIG_PINCTRL_IPROC_GPIO=yCONFIG_PINCTRL_CYGNUS_MUX=yCONFIG_PINCTRL_NS=yCONFIG_PINCTRL_NSP_GPIO=y
# CONFIG_PINCTRL_NS2_MUX is not setCONFIG_PINCTRL_NSP_MUX=yCONFIG_PINCTRL_BERLIN=y
# CONFIG_PINCTRL_AS370 is not setCONFIG_PINCTRL_BERLIN_BG2=yCONFIG_PINCTRL_BERLIN_BG2CD=yCONFIG_PINCTRL_BERLIN_BG2Q=y
# CONFIG_PINCTRL_BERLIN_BG4CT is not setCONFIG_PINCTRL_IMX=yCONFIG_PINCTRL_IMX50=yCONFIG_PINCTRL_IMX51=yCONFIG_PINCTRL_IMX53=yCONFIG_PINCTRL_IMX6Q=yCONFIG_PINCTRL_IMX6SL=yCONFIG_PINCTRL_IMX6SLL=yCONFIG_PINCTRL_IMX6SX=yCONFIG_PINCTRL_IMX6UL=yCONFIG_PINCTRL_IMX7D=yCONFIG_PINCTRL_IMX7ULP=y
# CONFIG_PINCTRL_IMX8MM is not set
# CONFIG_PINCTRL_IMX8MN is not set
# CONFIG_PINCTRL_IMX8MP is not set
# CONFIG_PINCTRL_IMX8MQ is not setCONFIG_PINCTRL_VF610=yCONFIG_PINCTRL_MVEBU=yCONFIG_PINCTRL_DOVE=yCONFIG_PINCTRL_ARMADA_370=yCONFIG_PINCTRL_ARMADA_375=yCONFIG_PINCTRL_ARMADA_38X=yCONFIG_PINCTRL_ARMADA_39X=yCONFIG_PINCTRL_ARMADA_XP=yCONFIG_PINCTRL_ABX500=yCONFIG_PINCTRL_AB8500=yCONFIG_PINCTRL_AB8505=yCONFIG_PINCTRL_NOMADIK=yCONFIG_PINCTRL_DB8500=y
# CONFIG_PINCTRL_MSM is not setCONFIG_PINCTRL_QCOM_SPMI_PMIC=yCONFIG_PINCTRL_QCOM_SSBI_PMIC=y
# CONFIG_PINCTRL_LPASS_LPI is not set
#
# Renesas pinctrl drivers
#CONFIG_PINCTRL_RENESAS=yCONFIG_PINCTRL_SH_PFC=yCONFIG_PINCTRL_SH_PFC_GPIO=yCONFIG_PINCTRL_PFC_EMEV2=yCONFIG_PINCTRL_PFC_R8A7794=yCONFIG_PINCTRL_PFC_R8A7779=yCONFIG_PINCTRL_PFC_R8A7790=yCONFIG_PINCTRL_PFC_R8A7778=yCONFIG_PINCTRL_PFC_R8A7793=yCONFIG_PINCTRL_PFC_R8A7791=yCONFIG_PINCTRL_PFC_R8A7792=yCONFIG_PINCTRL_PFC_R8A7740=yCONFIG_PINCTRL_PFC_R8A73A4=y
# CONFIG_PINCTRL_RZA1 is not setCONFIG_PINCTRL_RZA2=yCONFIG_PINCTRL_PFC_R8A77470=yCONFIG_PINCTRL_PFC_R8A7745=yCONFIG_PINCTRL_PFC_R8A7742=yCONFIG_PINCTRL_PFC_R8A7743=yCONFIG_PINCTRL_PFC_R8A7744=y
# CONFIG_PINCTRL_RZN1 is not setCONFIG_PINCTRL_PFC_SH73A0=y
# end of Renesas pinctrl drivers
CONFIG_PINCTRL_SAMSUNG=yCONFIG_PINCTRL_EXYNOS=yCONFIG_PINCTRL_EXYNOS_ARM=yCONFIG_PINCTRL_SPEAR=yCONFIG_PINCTRL_SPEAR1310=yCONFIG_PINCTRL_SPEAR1340=yCONFIG_PINCTRL_SPEAR_PLGPIO=yCONFIG_PINCTRL_STM32=yCONFIG_PINCTRL_STM32MP157=yCONFIG_PINCTRL_SUNXI=yCONFIG_PINCTRL_SUN4I_A10=yCONFIG_PINCTRL_SUN5I=yCONFIG_PINCTRL_SUN6I_A31=yCONFIG_PINCTRL_SUN6I_A31_R=yCONFIG_PINCTRL_SUN8I_A23=yCONFIG_PINCTRL_SUN8I_A33=yCONFIG_PINCTRL_SUN8I_A83T=yCONFIG_PINCTRL_SUN8I_A83T_R=yCONFIG_PINCTRL_SUN8I_A23_R=yCONFIG_PINCTRL_SUN8I_H3=yCONFIG_PINCTRL_SUN8I_H3_R=yCONFIG_PINCTRL_SUN8I_V3S=yCONFIG_PINCTRL_SUN9I_A80=yCONFIG_PINCTRL_SUN9I_A80_R=y
# CONFIG_PINCTRL_SUN50I_A64 is not set
# CONFIG_PINCTRL_SUN50I_A64_R is not set
# CONFIG_PINCTRL_SUN50I_A100 is not set
# CONFIG_PINCTRL_SUN50I_A100_R is not set
# CONFIG_PINCTRL_SUN50I_H5 is not set
# CONFIG_PINCTRL_SUN50I_H6 is not set
# CONFIG_PINCTRL_SUN50I_H6_R is not setCONFIG_PINCTRL_TEGRA=yCONFIG_PINCTRL_TEGRA20=yCONFIG_PINCTRL_TEGRA30=yCONFIG_PINCTRL_TEGRA114=yCONFIG_PINCTRL_TEGRA124=yCONFIG_PINCTRL_TEGRA_XUSB=yCONFIG_PINCTRL_TI_IODELAY=yCONFIG_PINCTRL_UNIPHIER=yCONFIG_PINCTRL_UNIPHIER_LD4=yCONFIG_PINCTRL_UNIPHIER_PRO4=yCONFIG_PINCTRL_UNIPHIER_SLD8=yCONFIG_PINCTRL_UNIPHIER_PRO5=yCONFIG_PINCTRL_UNIPHIER_PXS2=yCONFIG_PINCTRL_UNIPHIER_LD6B=y
# CONFIG_PINCTRL_UNIPHIER_LD11 is not set
# CONFIG_PINCTRL_UNIPHIER_LD20 is not set
# CONFIG_PINCTRL_UNIPHIER_PXS3 is not set
# CONFIG_PINCTRL_WM8850 is not set
#
# MediaTek pinctrl drivers
#CONFIG_EINT_MTK=yCONFIG_PINCTRL_MTK=yCONFIG_PINCTRL_MTK_V2=yCONFIG_PINCTRL_MTK_MOORE=yCONFIG_PINCTRL_MT2701=yCONFIG_PINCTRL_MT7623=yCONFIG_PINCTRL_MT7629=yCONFIG_PINCTRL_MT8135=yCONFIG_PINCTRL_MT8127=y
# end of MediaTek pinctrl drivers
CONFIG_PINCTRL_MESON=yCONFIG_PINCTRL_MESON8=yCONFIG_PINCTRL_MESON8B=yCONFIG_PINCTRL_MESON8_PMX=yCONFIG_ARCH_HAVE_CUSTOM_GPIO_H=yCONFIG_GPIOLIB=yCONFIG_GPIOLIB_FASTPATH_LIMIT=512CONFIG_OF_GPIO=yCONFIG_GPIOLIB_IRQCHIP=y
# CONFIG_DEBUG_GPIO is not set
# CONFIG_GPIO_SYSFS is not setCONFIG_GPIO_CDEV=yCONFIG_GPIO_CDEV_V1=yCONFIG_GPIO_GENERIC=y
#
# Memory mapped GPIO drivers
#
# CONFIG_GPIO_74XX_MMIO is not set
# CONFIG_GPIO_ALTERA is not set
# CONFIG_GPIO_ASPEED is not setCONFIG_GPIO_ASPEED_SGPIO=yCONFIG_GPIO_RASPBERRYPI_EXP=yCONFIG_GPIO_BCM_KONA=yCONFIG_GPIO_BCM_XGS_IPROC=yCONFIG_GPIO_BRCMSTB=y
# CONFIG_GPIO_CADENCE is not setCONFIG_GPIO_DAVINCI=yCONFIG_GPIO_DWAPB=yCONFIG_GPIO_EM=y
# CONFIG_GPIO_EXAR is not set
# CONFIG_GPIO_FTGPIO010 is not setCONFIG_GPIO_GENERIC_PLATFORM=y
# CONFIG_GPIO_GRGPIO is not set
# CONFIG_GPIO_HLWD is not set
# CONFIG_GPIO_LOGICVC is not set
# CONFIG_GPIO_MB86S7X is not set
# CONFIG_GPIO_MPC8XXX is not setCONFIG_GPIO_MVEBU=yCONFIG_GPIO_MXC=yCONFIG_GPIO_OMAP=yCONFIG_GPIO_PL061=yCONFIG_GPIO_PXA=yCONFIG_GPIO_RCAR=y
# CONFIG_GPIO_SAMA5D2_PIOBU is not set
# CONFIG_GPIO_SIFIVE is not setCONFIG_GPIO_SPEAR_SPICS=yCONFIG_GPIO_SYSCON=yCONFIG_GPIO_TEGRA=y
# CONFIG_GPIO_TS4800 is not setCONFIG_GPIO_UNIPHIER=yCONFIG_GPIO_VF610=yCONFIG_GPIO_XILINX=y
# CONFIG_GPIO_ZEVIO is not setCONFIG_GPIO_ZYNQ=y
# CONFIG_GPIO_AMD_FCH is not set
# end of Memory mapped GPIO drivers
#
# I2C GPIO expanders
#
# CONFIG_GPIO_ADP5588 is not set
# CONFIG_GPIO_ADNP is not set
# CONFIG_GPIO_GW_PLD is not set
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not setCONFIG_GPIO_PCA953X=yCONFIG_GPIO_PCA953X_IRQ=y
# CONFIG_GPIO_PCA9570 is not setCONFIG_GPIO_PCF857X=y
# CONFIG_GPIO_TPIC2810 is not set
# CONFIG_GPIO_TS4900 is not set
# end of I2C GPIO expanders
#
# MFD GPIO expanders
#
# CONFIG_HTC_EGPIO is not setCONFIG_GPIO_PALMAS=y
# CONFIG_GPIO_STMPE is not set
# CONFIG_GPIO_TPS65218 is not setCONFIG_GPIO_TPS6586X=yCONFIG_GPIO_TPS65910=yCONFIG_GPIO_TWL4030=y
# CONFIG_GPIO_WM8994 is not set
# end of MFD GPIO expanders
#
# PCI GPIO expanders
#
# CONFIG_GPIO_BT8XX is not set
# CONFIG_GPIO_PCI_IDIO_16 is not set
# CONFIG_GPIO_PCIE_IDIO_24 is not set
# CONFIG_GPIO_RDC321X is not set
# end of PCI GPIO expanders
#
# SPI GPIO expanders
#
# CONFIG_GPIO_74X164 is not set
# CONFIG_GPIO_MAX3191X is not set
# CONFIG_GPIO_MAX7301 is not set
# CONFIG_GPIO_MC33880 is not set
# CONFIG_GPIO_PISOSR is not set
# CONFIG_GPIO_XRA1403 is not set
# end of SPI GPIO expanders
#
# USB GPIO expanders
#
# end of USB GPIO expanders
#
# Virtual GPIO drivers
#
# CONFIG_GPIO_AGGREGATOR is not set
# CONFIG_GPIO_MOCKUP is not set
# end of Virtual GPIO drivers
# CONFIG_W1 is not set CONFIG_POWER_RESET=y CONFIG_POWER_RESET_AS3722=y CONFIG_POWER_RESET_AT91_POWEROFF=y CONFIG_POWER_RESET_AT91_RESET=y CONFIG_POWER_RESET_AT91_SAMA5D2_SHDWC=y CONFIG_POWER_RESET_BRCMKONA=y CONFIG_POWER_RESET_BRCMSTB=y CONFIG_POWER_RESET_GPIO=y CONFIG_POWER_RESET_GPIO_RESTART=y CONFIG_POWER_RESET_HISI=y
# CONFIG_POWER_RESET_LINKSTATION is not set # CONFIG_POWER_RESET_MSM is not set
# CONFIG_POWER_RESET_QCOM_PON is not set
# CONFIG_POWER_RESET_LTC2952 is not set
# CONFIG_POWER_RESET_QNAP is not set
# CONFIG_POWER_RESET_RESTART is not set CONFIG_POWER_RESET_ST=y
# CONFIG_POWER_RESET_VERSATILE is not set CONFIG_POWER_RESET_VEXPRESS=y CONFIG_POWER_RESET_KEYSTONE=y CONFIG_POWER_RESET_SYSCON=y CONFIG_POWER_RESET_SYSCON_POWEROFF=y CONFIG_POWER_RESET_RMOBILE=y
# CONFIG_SYSCON_REBOOT_MODE is not set
# CONFIG_NVMEM_REBOOT_MODE is not set CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set CONFIG_POWER_SUPPLY_HWMON=y
# CONFIG_PDA_POWER is not set
# CONFIG_GENERIC_ADC_BATTERY is not set CONFIG_TEST_POWER=m
# CONFIG_CHARGER_ADP5061 is not set CONFIG_BATTERY_ACT8945A=y CONFIG_BATTERY_CPCAP=m
# CONFIG_BATTERY_CW2015 is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2781 is not set
# CONFIG_BATTERY_DS2782 is not set CONFIG_BATTERY_SBS=y
# CONFIG_CHARGER_SBS is not set
# CONFIG_MANAGER_SBS is not set CONFIG_BATTERY_BQ27XXX=m CONFIG_BATTERY_BQ27XXX_I2C=m
# CONFIG_BATTERY_BQ27XXX_DT_UPDATES_NVM is not set CONFIG_AXP20X_POWER=m
# CONFIG_AXP288_FUEL_GAUGE is not set CONFIG_BATTERY_MAX17040=m CONFIG_BATTERY_MAX17042=m CONFIG_CHARGER_CPCAP=m
# CONFIG_CHARGER_ISP1704 is not set
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_TWL4030 is not set
# CONFIG_CHARGER_LP8727 is not set CONFIG_CHARGER_GPIO=m
# CONFIG_CHARGER_MANAGER is not set
# CONFIG_CHARGER_LT3651 is not set CONFIG_CHARGER_MAX14577=m
# CONFIG_CHARGER_DETECTOR_MAX14656 is not set CONFIG_CHARGER_MAX77693=m CONFIG_CHARGER_MAX8997=m CONFIG_CHARGER_MAX8998=m
# CONFIG_CHARGER_QCOM_SMBB is not set
# CONFIG_CHARGER_BQ2415X is not set
# CONFIG_CHARGER_BQ24190 is not set
# CONFIG_CHARGER_BQ24257 is not set
# CONFIG_CHARGER_BQ24735 is not set
# CONFIG_CHARGER_BQ2515X is not set
# CONFIG_CHARGER_BQ25890 is not set
# CONFIG_CHARGER_BQ25980 is not set
# CONFIG_CHARGER_SMB347 is not set CONFIG_CHARGER_TPS65090=y
# CONFIG_CHARGER_TPS65217 is not set
# CONFIG_BATTERY_GAUGE_LTC2941 is not set # CONFIG_AB8500_BM is not set
# CONFIG_CHARGER_RT9455 is not set
# CONFIG_CHARGER_CROS_USBPD is not set
# CONFIG_CHARGER_UCS1002 is not set
# CONFIG_CHARGER_BD99954 is not set
# CONFIG_RN5T618_POWER is not set CONFIG_HWMON=y
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#
# CONFIG_SENSORS_AD7314 is not set
# CONFIG_SENSORS_AD7414 is not set
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM1177 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7310 is not set
# CONFIG_SENSORS_ADT7410 is not set
# CONFIG_SENSORS_ADT7411 is not set
# CONFIG_SENSORS_ADT7462 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7475 is not set
# CONFIG_SENSORS_AS370 is not set
# CONFIG_SENSORS_ASC7621 is not set
# CONFIG_SENSORS_AXI_FAN_CONTROL is not set CONFIG_SENSORS_ASPEED=m
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_CORSAIR_CPRO is not set
# CONFIG_SENSORS_CORSAIR_PSU is not set
# CONFIG_SENSORS_DRIVETEMP is not set
# CONFIG_SENSORS_DS620 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_FTSTEUTATES is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_G760A is not set
# CONFIG_SENSORS_G762 is not set
# CONFIG_SENSORS_GPIO_FAN is not set
# CONFIG_SENSORS_HIH6130 is not set CONFIG_SENSORS_IIO_HWMON=y
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_JC42 is not set
# CONFIG_SENSORS_POWR1220 is not set
# CONFIG_SENSORS_LINEAGE is not set
# CONFIG_SENSORS_LTC2945 is not set
# CONFIG_SENSORS_LTC2947_I2C is not set
# CONFIG_SENSORS_LTC2947_SPI is not set
# CONFIG_SENSORS_LTC2990 is not set
# CONFIG_SENSORS_LTC2992 is not set
# CONFIG_SENSORS_LTC4151 is not set
# CONFIG_SENSORS_LTC4215 is not set
# CONFIG_SENSORS_LTC4222 is not set
# CONFIG_SENSORS_LTC4245 is not set
# CONFIG_SENSORS_LTC4260 is not set
# CONFIG_SENSORS_LTC4261 is not set
# CONFIG_SENSORS_MAX1111 is not set
# CONFIG_SENSORS_MAX127 is not set
# CONFIG_SENSORS_MAX16065 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX1668 is not set
# CONFIG_SENSORS_MAX197 is not set
# CONFIG_SENSORS_MAX31722 is not set
# CONFIG_SENSORS_MAX31730 is not set
# CONFIG_SENSORS_MAX6621 is not set
# CONFIG_SENSORS_MAX6639 is not set
# CONFIG_SENSORS_MAX6642 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_MAX6697 is not set
# CONFIG_SENSORS_MAX31790 is not set
# CONFIG_SENSORS_MCP3021 is not set
# CONFIG_SENSORS_TC654 is not set
# CONFIG_SENSORS_MR75203 is not set
# CONFIG_SENSORS_ADCXX is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM70 is not set
# CONFIG_SENSORS_LM73 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set CONFIG_SENSORS_LM90=y
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_LM95234 is not set
# CONFIG_SENSORS_LM95241 is not set CONFIG_SENSORS_LM95245=y
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set CONFIG_SENSORS_NTC_THERMISTOR=m
# CONFIG_SENSORS_NCT6683 is not set
# CONFIG_SENSORS_NCT6775 is not set
# CONFIG_SENSORS_NCT7802 is not set
# CONFIG_SENSORS_NCT7904 is not set
# CONFIG_SENSORS_NPCM7XX is not set
# CONFIG_SENSORS_OCC_P8_I2C is not set
# CONFIG_SENSORS_OCC_P9_SBE is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_PMBUS is not set CONFIG_SENSORS_PWM_FAN=m CONFIG_SENSORS_RASPBERRYPI_HWMON=m
# CONFIG_SENSORS_SHT15 is not set
# CONFIG_SENSORS_SHT21 is not set
# CONFIG_SENSORS_SHT3x is not set
# CONFIG_SENSORS_SHTC1 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_EMC1403 is not set
# CONFIG_SENSORS_EMC2103 is not set
# CONFIG_SENSORS_EMC6W201 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_SCH5627 is not set
# CONFIG_SENSORS_SCH5636 is not set
# CONFIG_SENSORS_STTS751 is not set
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_ADC128D818 is not set
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_ADS7871 is not set
# CONFIG_SENSORS_AMC6821 is not set
# CONFIG_SENSORS_INA209 is not set CONFIG_SENSORS_INA2XX=m
# CONFIG_SENSORS_INA3221 is not set
# CONFIG_SENSORS_TC74 is not set
# CONFIG_SENSORS_THMC50 is not set
# CONFIG_SENSORS_TMP102 is not set
# CONFIG_SENSORS_TMP103 is not set
# CONFIG_SENSORS_TMP108 is not set
# CONFIG_SENSORS_TMP401 is not set
# CONFIG_SENSORS_TMP421 is not set
# CONFIG_SENSORS_TMP513 is not set
# CONFIG_SENSORS_VEXPRESS is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83773G is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83795 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83L786NG is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set CONFIG_THERMAL=y
# CONFIG_THERMAL_NETLINK is not set
# CONFIG_THERMAL_STATISTICS is not set CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS=0 CONFIG_THERMAL_HWMON=yCONFIG_THERMAL_OF=y
# CONFIG_THERMAL_WRITABLE_TRIPS is not set CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y
# CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set # CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set # CONFIG_THERMAL_GOV_FAIR_SHARE is not set CONFIG_THERMAL_GOV_STEP_WISE=y
# CONFIG_THERMAL_GOV_BANG_BANG is not set # CONFIG_THERMAL_GOV_USER_SPACE is not set CONFIG_CPU_THERMAL=y CONFIG_CPU_FREQ_THERMAL=y CONFIG_DEVFREQ_THERMAL=y
# CONFIG_THERMAL_EMULATION is not set
# CONFIG_THERMAL_MMIO is not set CONFIG_HISI_THERMAL=yCONFIG_IMX_THERMAL=y
# CONFIG_IMX8MM_THERMAL is not set
# CONFIG_QORIQ_THERMAL is not set
# CONFIG_SPEAR_THERMAL is not set
# CONFIG_SUN8I_THERMAL is not set CONFIG_ROCKCHIP_THERMAL=y CONFIG_RCAR_THERMAL=y
# CONFIG_RCAR_GEN3_THERMAL is not set
# CONFIG_DOVE_THERMAL is not set CONFIG_DB8500_THERMAL=y CONFIG_ARMADA_THERMAL=y CONFIG_MTK_THERMAL=y CONFIG_AMLOGIC_THERMAL=y
#
# Broadcom thermal drivers
#CONFIG_BCM2711_THERMAL=mCONFIG_BCM2835_THERMAL=mCONFIG_BRCMSTB_THERMAL=mCONFIG_BCM_NS_THERMAL=yCONFIG_BCM_SR_THERMAL=y
# end of Broadcom thermal drivers
#
# Texas Instruments thermal drivers
#CONFIG_TI_SOC_THERMAL=y
# CONFIG_TI_THERMAL is not set
# CONFIG_OMAP3_THERMAL is not set
# CONFIG_OMAP4_THERMAL is not set
# CONFIG_OMAP5_THERMAL is not set
# CONFIG_DRA752_THERMAL is not set
# end of Texas Instruments thermal drivers
#
# Samsung thermal drivers
#CONFIG_EXYNOS_THERMAL=y
# end of Samsung thermal drivers
#
# STMicroelectronics thermal drivers
#CONFIG_ST_THERMAL=y
# CONFIG_ST_THERMAL_SYSCFG is not setCONFIG_ST_THERMAL_MEMMAP=yCONFIG_STM32_THERMAL=y
# end of STMicroelectronics thermal drivers
#
# NVIDIA Tegra thermal drivers
#
# CONFIG_TEGRA_SOCTHERM is not set
# end of NVIDIA Tegra thermal drivers
# CONFIG_GENERIC_ADC_THERMAL is not set
#
# Qualcomm thermal drivers
#
# CONFIG_QCOM_SPMI_TEMP_ALARM is not set
# end of Qualcomm thermal drivers
CONFIG_UNIPHIER_THERMAL=yCONFIG_WATCHDOG=yCONFIG_WATCHDOG_CORE=y
# CONFIG_WATCHDOG_NOWAYOUT is not setCONFIG_WATCHDOG_HANDLE_BOOT_ENABLED=yCONFIG_WATCHDOG_OPEN_TIMEOUT=0
# CONFIG_WATCHDOG_SYSFS is not set
#
# Watchdog Pretimeout Governors
#
# CONFIG_WATCHDOG_PRETIMEOUT_GOV is not set
#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not setCONFIG_DA9063_WATCHDOG=m
# CONFIG_GPIO_WATCHDOG is not setCONFIG_XILINX_WATCHDOG=y
# CONFIG_ZIIRAVE_WATCHDOG is not setCONFIG_ARM_SP805_WATCHDOG=y
# CONFIG_ARMADA_37XX_WATCHDOG is not setCONFIG_AT91SAM9X_WATCHDOG=yCONFIG_SAMA5D4_WATCHDOG=y
# CONFIG_CADENCE_WATCHDOG is not set
# CONFIG_FTWDT010_WATCHDOG is not setCONFIG_S3C2410_WATCHDOG=mCONFIG_DW_WATCHDOG=y
# CONFIG_OMAP_WATCHDOG is not setCONFIG_DAVINCI_WATCHDOG=mCONFIG_ORION_WATCHDOG=yCONFIG_RN5T618_WATCHDOG=yCONFIG_SUNXI_WATCHDOG=y
# CONFIG_TWL4030_WATCHDOG is not set
# CONFIG_TS4800_WATCHDOG is not set
# CONFIG_MAX63XX_WATCHDOG is not setCONFIG_IMX2_WDT=y
# CONFIG_IMX7ULP_WDT is not setCONFIG_UX500_WATCHDOG=yCONFIG_SIRFSOC_WATCHDOG=yCONFIG_ST_LPC_WATCHDOG=yCONFIG_TEGRA_WATCHDOG=m
# CONFIG_QCOM_WDT is not set
# CONFIG_MESON_GXBB_WATCHDOG is not setCONFIG_MESON_WATCHDOG=y
# CONFIG_MEDIATEK_WATCHDOG is not setCONFIG_DIGICOLOR_WATCHDOG=y
# CONFIG_ARM_SMC_WATCHDOG is not set
# CONFIG_ATLAS7_WATCHDOG is not setCONFIG_RENESAS_WDT=mCONFIG_RENESAS_RZAWDT=mCONFIG_ASPEED_WATCHDOG=yCONFIG_STM32_WATCHDOG=yCONFIG_STPMIC1_WATCHDOG=y
# CONFIG_UNIPHIER_WATCHDOG is not set
# CONFIG_PM8916_WATCHDOG is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_I6300ESB_WDT is not setCONFIG_BCM47XX_WDT=yCONFIG_BCM2835_WDT=yCONFIG_BCM_KONA_WDT=y
# CONFIG_BCM_KONA_WDT_DEBUG is not setCONFIG_BCM7038_WDT=m
# CONFIG_MEN_A21_WDT is not set
#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set
#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not setCONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not setCONFIG_BCMA_POSSIBLE=yCONFIG_BCMA=yCONFIG_BCMA_HOST_PCI_POSSIBLE=yCONFIG_BCMA_HOST_PCI=yCONFIG_BCMA_HOST_SOC=yCONFIG_BCMA_DRIVER_PCI=yCONFIG_BCMA_SFLASH=yCONFIG_BCMA_DRIVER_GMAC_CMN=yCONFIG_BCMA_DRIVER_GPIO=y
# CONFIG_BCMA_DEBUG is not set
#
# Multifunction device drivers
#CONFIG_MFD_CORE=y
# CONFIG_MFD_ALTERA_A10SR is not set
# CONFIG_MFD_ALTERA_SYSMGR is not setCONFIG_MFD_ACT8945A=yCONFIG_MFD_AS3711=yCONFIG_MFD_AS3722=y
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_AAT2870_CORE is not setCONFIG_MFD_AT91_USART=yCONFIG_MFD_ATMEL_FLEXCOM=yCONFIG_MFD_ATMEL_HLCDC=mCONFIG_MFD_ATMEL_SMC=yCONFIG_MFD_BCM590XX=y
# CONFIG_MFD_BD9571MWV is not setCONFIG_MFD_AC100=yCONFIG_MFD_AXP20X=yCONFIG_MFD_AXP20X_I2C=yCONFIG_MFD_AXP20X_RSB=yCONFIG_MFD_CROS_EC_DEV=m
# CONFIG_MFD_MADERA is not set
# CONFIG_MFD_ASIC3 is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_MFD_DA9052_SPI is not set
# CONFIG_MFD_DA9052_I2C is not set
# CONFIG_MFD_DA9055 is not set
# CONFIG_MFD_DA9062 is not setCONFIG_MFD_DA9063=m
# CONFIG_MFD_DA9150 is not set
# CONFIG_MFD_DLN2 is not set
# CONFIG_MFD_ENE_KB3930 is not set
# CONFIG_MFD_EXYNOS_LPASS is not set
# CONFIG_MFD_GATEWORKS_GSC is not set
# CONFIG_MFD_MC13XXX_SPI is not set
# CONFIG_MFD_MC13XXX_I2C is not set
# CONFIG_MFD_MP2629 is not set
# CONFIG_MFD_HI6421_PMIC is not set
# CONFIG_MFD_HI655X_PMIC is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_HTC_I2CPLD is not set
# CONFIG_LPC_ICH is not set
# CONFIG_LPC_SCH is not set
# CONFIG_MFD_INTEL_PMT is not set
# CONFIG_MFD_IQS62X is not set
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not set
# CONFIG_MFD_88PM805 is not set
# CONFIG_MFD_88PM860X is not setCONFIG_MFD_MAX14577=y
# CONFIG_MFD_MAX77620 is not set
# CONFIG_MFD_MAX77650 is not setCONFIG_MFD_MAX77686=yCONFIG_MFD_MAX77693=m
# CONFIG_MFD_MAX77843 is not setCONFIG_MFD_MAX8907=y
# CONFIG_MFD_MAX8925 is not setCONFIG_MFD_MAX8997=yCONFIG_MFD_MAX8998=y
# CONFIG_MFD_MT6360 is not set
# CONFIG_MFD_MT6397 is not set
# CONFIG_MFD_MENF21BMC is not set
# CONFIG_EZX_PCAP is not setCONFIG_MFD_CPCAP=y
# CONFIG_MFD_VIPERBOARD is not set
# CONFIG_MFD_RETU is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_UCB1400_CORE is not setCONFIG_MFD_PM8XXX=yCONFIG_MFD_QCOM_RPM=yCONFIG_MFD_SPMI_PMIC=y
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_RT5033 is not set
# CONFIG_MFD_RC5T583 is not setCONFIG_MFD_RK808=yCONFIG_MFD_RN5T618=yCONFIG_MFD_SEC_CORE=y
# CONFIG_MFD_SI476X_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_MFD_SKY81452 is not setCONFIG_ABX500_CORE=y
# CONFIG_AB3100_CORE is not setCONFIG_AB8500_CORE=yCONFIG_AB8500_DEBUG=yCONFIG_MFD_DB8500_PRCMU=yCONFIG_MFD_STMPE=y
#
# STMicroelectronics STMPE Interface Drivers
#CONFIG_STMPE_I2C=y
# CONFIG_STMPE_SPI is not set
# end of STMicroelectronics STMPE Interface Drivers
CONFIG_MFD_SUN6I_PRCM=yCONFIG_MFD_SYSCON=y
# CONFIG_MFD_TI_AM335X_TSCADC is not set
# CONFIG_MFD_LP3943 is not set
# CONFIG_MFD_LP8788 is not set
# CONFIG_MFD_TI_LMU is not setCONFIG_MFD_OMAP_USB_HOST=yCONFIG_MFD_PALMAS=y
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
# CONFIG_MFD_TPS65086 is not setCONFIG_MFD_TPS65090=yCONFIG_MFD_TPS65217=y
# CONFIG_MFD_TI_LP873X is not set
# CONFIG_MFD_TI_LP87565 is not setCONFIG_MFD_TPS65218=yCONFIG_MFD_TPS6586X=yCONFIG_MFD_TPS65910=y
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_MFD_TPS65912_SPI is not set
# CONFIG_MFD_TPS80031 is not setCONFIG_TWL4030_CORE=yCONFIG_TWL4030_POWER=y
# CONFIG_MFD_TWL4030_AUDIO is not set
# CONFIG_TWL6040_CORE is not set
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_MFD_LM3533 is not set
# CONFIG_MFD_TC3589X is not set
# CONFIG_MFD_T7L66XB is not set
# CONFIG_MFD_TC6387XB is not set
# CONFIG_MFD_TC6393XB is not set
# CONFIG_MFD_TQMX86 is not set
# CONFIG_MFD_VX855 is not set
# CONFIG_MFD_LOCHNAGAR is not set
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_ARIZONA_SPI is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM831X_SPI is not set
# CONFIG_MFD_WM8350_I2C is not setCONFIG_MFD_WM8994=m
# CONFIG_MFD_ROHM_BD718XX is not set
# CONFIG_MFD_ROHM_BD70528 is not set
# CONFIG_MFD_ROHM_BD71828 is not setCONFIG_MFD_STM32_LPTIMER=mCONFIG_MFD_STM32_TIMERS=mCONFIG_MFD_STPMIC1=yCONFIG_MFD_STMFX=y
# CONFIG_MFD_KHADAS_MCU is not setCONFIG_MFD_VEXPRESS_SYSREG=y
# CONFIG_RAVE_SP_CORE is not set
# CONFIG_MFD_INTEL_M10_BMC is not set
# end of Multifunction device drivers
CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not set CONFIG_REGULATOR_FIXED_VOLTAGE=y
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
# CONFIG_REGULATOR_USERSPACE_CONSUMER is not set
# CONFIG_REGULATOR_88PG86X is not set CONFIG_REGULATOR_ACT8865=y CONFIG_REGULATOR_ACT8945A=y
# CONFIG_REGULATOR_AD5398 is not set CONFIG_REGULATOR_ANATOP=y CONFIG_REGULATOR_AB8500=y CONFIG_REGULATOR_AS3711=y CONFIG_REGULATOR_AS3722=y CONFIG_REGULATOR_AXP20X=y CONFIG_REGULATOR_BCM590XX=y CONFIG_REGULATOR_CPCAP=y
# CONFIG_REGULATOR_CROS_EC is not set
# CONFIG_REGULATOR_DA9063 is not set
# CONFIG_REGULATOR_DA9121 is not set CONFIG_REGULATOR_DA9210=y
# CONFIG_REGULATOR_DA9211 is not set CONFIG_REGULATOR_DBX500_PRCMU=y CONFIG_REGULATOR_DB8500_PRCMU=y CONFIG_REGULATOR_FAN53555=y
# CONFIG_REGULATOR_FAN53880 is not set CONFIG_REGULATOR_GPIO=y
# CONFIG_REGULATOR_ISL9305 is not set
# CONFIG_REGULATOR_ISL6271A is not set
# CONFIG_REGULATOR_LP3971 is not set
# CONFIG_REGULATOR_LP3972 is not set CONFIG_REGULATOR_LP872X=y
# CONFIG_REGULATOR_LP8755 is not set
# CONFIG_REGULATOR_LTC3589 is not set
# CONFIG_REGULATOR_LTC3676 is not set CONFIG_REGULATOR_MAX14577=m
# CONFIG_REGULATOR_MAX1586 is not set
# CONFIG_REGULATOR_MAX8649 is not set
# CONFIG_REGULATOR_MAX8660 is not set CONFIG_REGULATOR_MAX8907=y CONFIG_REGULATOR_MAX8952=m CONFIG_REGULATOR_MAX8973=y CONFIG_REGULATOR_MAX8997=m CONFIG_REGULATOR_MAX8998=m CONFIG_REGULATOR_MAX77686=y CONFIG_REGULATOR_MAX77693=m CONFIG_REGULATOR_MAX77802=y
# CONFIG_REGULATOR_MAX77826 is not set
# CONFIG_REGULATOR_MCP16502 is not set
# CONFIG_REGULATOR_MP5416 is not set
# CONFIG_REGULATOR_MP8859 is not set
# CONFIG_REGULATOR_MP886X is not set
# CONFIG_REGULATOR_MPQ7920 is not set
# CONFIG_REGULATOR_MT6311 is not set CONFIG_REGULATOR_PALMAS=yCONFIG_REGULATOR_PBIAS=y
# CONFIG_REGULATOR_PCA9450 is not set
# CONFIG_REGULATOR_PF8X00 is not set
# CONFIG_REGULATOR_PFUZE100 is not set
# CONFIG_REGULATOR_PV88060 is not set
# CONFIG_REGULATOR_PV88080 is not set
# CONFIG_REGULATOR_PV88090 is not set CONFIG_REGULATOR_PWM=yCONFIG_REGULATOR_QCOM_RPM=y CONFIG_REGULATOR_QCOM_SMD_RPM=m
# CONFIG_REGULATOR_QCOM_SPMI is not set
# CONFIG_REGULATOR_QCOM_USB_VBUS is not set
# CONFIG_REGULATOR_RASPBERRYPI_TOUCHSCREEN_ATTINY is not set CONFIG_REGULATOR_RK808=y CONFIG_REGULATOR_RN5T618=y
# CONFIG_REGULATOR_RT4801 is not set
# CONFIG_REGULATOR_RTMV20 is not set CONFIG_REGULATOR_S2MPA01=m CONFIG_REGULATOR_S2MPS11=y CONFIG_REGULATOR_S5M8767=y
# CONFIG_REGULATOR_SLG51000 is not set CONFIG_REGULATOR_STM32_BOOSTER=m CONFIG_REGULATOR_STM32_VREFBUF=m CONFIG_REGULATOR_STM32_PWR=y CONFIG_REGULATOR_STPMIC1=y CONFIG_REGULATOR_TI_ABB=y
# CONFIG_REGULATOR_SY8106A is not set
# CONFIG_REGULATOR_SY8824X is not set
# CONFIG_REGULATOR_SY8827N is not set CONFIG_REGULATOR_TPS51632=y CONFIG_REGULATOR_TPS62360=y
# CONFIG_REGULATOR_TPS65023 is not set
# CONFIG_REGULATOR_TPS6507X is not set CONFIG_REGULATOR_TPS65090=y
# CONFIG_REGULATOR_TPS65132 is not set CONFIG_REGULATOR_TPS65217=y CONFIG_REGULATOR_TPS65218=y
# CONFIG_REGULATOR_TPS6524X is not set CONFIG_REGULATOR_TPS6586X=y CONFIG_REGULATOR_TPS65910=y CONFIG_REGULATOR_TWL4030=y CONFIG_REGULATOR_UNIPHIER=y
# CONFIG_REGULATOR_VCTRL is not set CONFIG_REGULATOR_VEXPRESS=y
# CONFIG_REGULATOR_VQMMC_IPQ4019 is not set CONFIG_REGULATOR_WM8994=m
# CONFIG_REGULATOR_QCOM_LABIBB is not set
# CONFIG_RC_CORE is not setCONFIG_CEC_CORE=yCONFIG_CEC_NOTIFIER=yCONFIG_MEDIA_CEC_SUPPORT=y
# CONFIG_CEC_CH7322 is not set
# CONFIG_CEC_CROS_EC is not set
# CONFIG_CEC_MESON_AO is not set
# CONFIG_CEC_MESON_G12A_AO is not set
# CONFIG_CEC_GPIO is not set CONFIG_CEC_SAMSUNG_S5P=m
# CONFIG_CEC_STI is not set
# CONFIG_CEC_STM32 is not set
# CONFIG_CEC_TEGRA is not set
# CONFIG_USB_PULSE8_CEC is not set
# CONFIG_USB_RAINSHADOW_CEC is not set CONFIG_MEDIA_SUPPORT=m
# CONFIG_MEDIA_SUPPORT_FILTER is not set
# CONFIG_MEDIA_SUBDRV_AUTOSELECT is not set
#
# Media device types
#CONFIG_MEDIA_CAMERA_SUPPORT=yCONFIG_MEDIA_ANALOG_TV_SUPPORT=yCONFIG_MEDIA_DIGITAL_TV_SUPPORT=yCONFIG_MEDIA_RADIO_SUPPORT=yCONFIG_MEDIA_SDR_SUPPORT=yCONFIG_MEDIA_PLATFORM_SUPPORT=yCONFIG_MEDIA_TEST_SUPPORT=y
# end of Media device types
#
# Media core support
#CONFIG_VIDEO_DEV=mCONFIG_MEDIA_CONTROLLER=yCONFIG_DVB_CORE=m
# end of Media core support
#
# Video4Linux options
#CONFIG_VIDEO_V4L2=mCONFIG_VIDEO_V4L2_I2C=yCONFIG_VIDEO_V4L2_SUBDEV_API=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not setCONFIG_V4L2_MEM2MEM_DEV=m
# CONFIG_V4L2_FLASH_LED_CLASS is not setCONFIG_V4L2_FWNODE=m
# end of Video4Linux options
#
# Media controller options
#
# CONFIG_MEDIA_CONTROLLER_DVB is not setCONFIG_MEDIA_CONTROLLER_REQUEST_API=y
#
# Please notice that the enabled Media controller Request API is EXPERIMENTAL #
# end of Media controller options
#
# Digital TV options
#
# CONFIG_DVB_MMAP is not setCONFIG_DVB_NET=yCONFIG_DVB_MAX_ADAPTERS=16CONFIG_DVB_DYNAMIC_MINORS=y
# CONFIG_DVB_DEMUX_SECTION_LOSS_LOG is not set
# CONFIG_DVB_ULE_DEBUG is not set
# end of Digital TV options
#
# Media drivers
#CONFIG_MEDIA_USB_SUPPORT=y
#
# Webcam devices
#CONFIG_USB_VIDEO_CLASS=mCONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=yCONFIG_USB_GSPCA=m
# CONFIG_USB_M5602 is not set
# CONFIG_USB_STV06XX is not set
# CONFIG_USB_GL860 is not set
# CONFIG_USB_GSPCA_BENQ is not set
# CONFIG_USB_GSPCA_CONEX is not set
# CONFIG_USB_GSPCA_CPIA1 is not set
# CONFIG_USB_GSPCA_DTCS033 is not set
# CONFIG_USB_GSPCA_ETOMS is not set
# CONFIG_USB_GSPCA_FINEPIX is not set
# CONFIG_USB_GSPCA_JEILINJ is not set
# CONFIG_USB_GSPCA_JL2005BCD is not set
# CONFIG_USB_GSPCA_KINECT is not set
# CONFIG_USB_GSPCA_KONICA is not set
# CONFIG_USB_GSPCA_MARS is not set
# CONFIG_USB_GSPCA_MR97310A is not set
# CONFIG_USB_GSPCA_NW80X is not set
# CONFIG_USB_GSPCA_OV519 is not set
# CONFIG_USB_GSPCA_OV534 is not set
# CONFIG_USB_GSPCA_OV534_9 is not set
# CONFIG_USB_GSPCA_PAC207 is not set
# CONFIG_USB_GSPCA_PAC7302 is not set
# CONFIG_USB_GSPCA_PAC7311 is not set
# CONFIG_USB_GSPCA_SE401 is not set
# CONFIG_USB_GSPCA_SN9C2028 is not set
# CONFIG_USB_GSPCA_SN9C20X is not set
# CONFIG_USB_GSPCA_SONIXB is not set
# CONFIG_USB_GSPCA_SONIXJ is not set
# CONFIG_USB_GSPCA_SPCA500 is not set
# CONFIG_USB_GSPCA_SPCA501 is not set
# CONFIG_USB_GSPCA_SPCA505 is not set
# CONFIG_USB_GSPCA_SPCA506 is not set
# CONFIG_USB_GSPCA_SPCA508 is not set
# CONFIG_USB_GSPCA_SPCA561 is not set
# CONFIG_USB_GSPCA_SPCA1528 is not set
# CONFIG_USB_GSPCA_SQ905 is not set
# CONFIG_USB_GSPCA_SQ905C is not set
# CONFIG_USB_GSPCA_SQ930X is not set
# CONFIG_USB_GSPCA_STK014 is not set
# CONFIG_USB_GSPCA_STK1135 is not set
# CONFIG_USB_GSPCA_STV0680 is not set
# CONFIG_USB_GSPCA_SUNPLUS is not set
# CONFIG_USB_GSPCA_T613 is not set
# CONFIG_USB_GSPCA_TOPRO is not set
# CONFIG_USB_GSPCA_TOUPTEK is not set
# CONFIG_USB_GSPCA_TV8532 is not set
# CONFIG_USB_GSPCA_VC032X is not set
# CONFIG_USB_GSPCA_VICAM is not set
# CONFIG_USB_GSPCA_XIRLINK_CIT is not set
# CONFIG_USB_GSPCA_ZC3XX is not set
# CONFIG_USB_PWC is not set
# CONFIG_VIDEO_CPIA2 is not set
# CONFIG_USB_ZR364XX is not set
# CONFIG_USB_STKWEBCAM is not set
# CONFIG_USB_S2255 is not set
# CONFIG_VIDEO_USBTV is not set
#
# Analog TV USB devices
#
# CONFIG_VIDEO_PVRUSB2 is not set
# CONFIG_VIDEO_HDPVR is not set
# CONFIG_VIDEO_STK1160_COMMON is not set
# CONFIG_VIDEO_GO7007 is not set
#
# Analog/digital TV USB devices
#
# CONFIG_VIDEO_AU0828 is not set
# CONFIG_VIDEO_CX231XX is not set
#
# Digital TV USB devices
#
# CONFIG_DVB_USB_V2 is not set
# CONFIG_DVB_TTUSB_BUDGET is not set
# CONFIG_DVB_TTUSB_DEC is not set
# CONFIG_SMS_USB_DRV is not set
# CONFIG_DVB_B2C2_FLEXCOP_USB is not set
# CONFIG_DVB_AS102 is not set
#
# Webcam, TV (analog/digital) USB devices
#
# CONFIG_VIDEO_EM28XX is not set
#
# Software defined radio USB devices
#
# CONFIG_USB_AIRSPY is not set
# CONFIG_USB_HACKRF is not set
# CONFIG_USB_MSI2500 is not set
# CONFIG_MEDIA_PCI_SUPPORT is not setCONFIG_RADIO_ADAPTERS=y
# CONFIG_RADIO_SI470X is not set
# CONFIG_RADIO_SI4713 is not set
# CONFIG_USB_MR800 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_SHARK is not set
# CONFIG_RADIO_SHARK2 is not set
# CONFIG_USB_KEENE is not set
# CONFIG_USB_RAREMONO is not set
# CONFIG_USB_MA901 is not set
# CONFIG_RADIO_TEA5764 is not set
# CONFIG_RADIO_SAA7706H is not set
# CONFIG_RADIO_TEF6862 is not set
# CONFIG_RADIO_WL1273 is not setCONFIG_VIDEOBUF2_CORE=mCONFIG_VIDEOBUF2_V4L2=mCONFIG_VIDEOBUF2_MEMOPS=mCONFIG_VIDEOBUF2_DMA_CONTIG=mCONFIG_VIDEOBUF2_VMALLOC=mCONFIG_VIDEOBUF2_DMA_SG=mCONFIG_VIDEO_V4L2_TPG=mCONFIG_V4L_PLATFORM_DRIVERS=y
# CONFIG_VIDEO_CAFE_CCIC is not setCONFIG_VIDEO_MMP_CAMERA=m
# CONFIG_VIDEO_CADENCE is not setCONFIG_VIDEO_ASPEED=m
# CONFIG_VIDEO_MUX is not setCONFIG_VIDEO_STM32_DCMI=mCONFIG_VIDEO_RENESAS_CEU=m
# CONFIG_VIDEO_ROCKCHIP_ISP1 is not setCONFIG_VIDEO_SAMSUNG_EXYNOS4_IS=mCONFIG_VIDEO_EXYNOS4_IS_COMMON=mCONFIG_VIDEO_S5P_FIMC=mCONFIG_VIDEO_S5P_MIPI_CSIS=mCONFIG_VIDEO_EXYNOS_FIMC_LITE=mCONFIG_VIDEO_EXYNOS4_FIMC_IS=mCONFIG_VIDEO_EXYNOS4_ISP_DMA_CAPTURE=y
# CONFIG_VIDEO_AM437X_VPFE is not set
# CONFIG_VIDEO_XILINX is not set
# CONFIG_VIDEO_RCAR_CSI2 is not setCONFIG_VIDEO_RCAR_VIN=m
# CONFIG_VIDEO_ATMEL_ISC is not setCONFIG_VIDEO_ATMEL_ISI=m
# CONFIG_VIDEO_SUN4I_CSI is not set
# CONFIG_VIDEO_SUN6I_CSI is not set
# CONFIG_VIDEO_TI_CAL is not setCONFIG_V4L_MEM2MEM_DRIVERS=y
# CONFIG_VIDEO_CODA is not set
# CONFIG_VIDEO_IMX_PXP is not set
# CONFIG_VIDEO_MEDIATEK_VPU is not set
# CONFIG_VIDEO_MEM2MEM_DEINTERLACE is not set
# CONFIG_VIDEO_MESON_GE2D is not set
# CONFIG_VIDEO_SAMSUNG_S5P_G2D is not setCONFIG_VIDEO_SAMSUNG_S5P_JPEG=mCONFIG_VIDEO_SAMSUNG_S5P_MFC=mCONFIG_VIDEO_SAMSUNG_EXYNOS_GSC=mCONFIG_VIDEO_STI_BDISP=mCONFIG_VIDEO_STI_HVA=m
# CONFIG_VIDEO_STI_HVA_DEBUGFS is not setCONFIG_VIDEO_STI_DELTA=mCONFIG_VIDEO_STI_DELTA_MJPEG=yCONFIG_VIDEO_STI_DELTA_DRIVER=mCONFIG_VIDEO_RENESAS_FDP1=mCONFIG_VIDEO_RENESAS_JPU=m
# CONFIG_VIDEO_RENESAS_FCP is not setCONFIG_VIDEO_RENESAS_VSP1=m
# CONFIG_VIDEO_ROCKCHIP_RGA is not set
# CONFIG_VIDEO_TI_VPE is not set
# CONFIG_VIDEO_SUN8I_DEINTERLACE is not set
# CONFIG_VIDEO_SUN8I_ROTATE is not set
# CONFIG_DVB_PLATFORM_DRIVERS is not set
# CONFIG_SDR_PLATFORM_DRIVERS is not set
#
# MMC/SDIO DVB adapters
#
# CONFIG_SMS_SDIO_DRV is not setCONFIG_V4L_TEST_DRIVERS=y
# CONFIG_VIDEO_VIMC is not setCONFIG_VIDEO_VIVID=m
# CONFIG_VIDEO_VIVID_CEC is not setCONFIG_VIDEO_VIVID_MAX_DEVS=64
# CONFIG_VIDEO_VIM2M is not set
# CONFIG_VIDEO_VICODEC is not set
# CONFIG_DVB_TEST_DRIVERS is not set
# end of Media drivers
#
# Media ancillary drivers
#CONFIG_MEDIA_ATTACH=y
#
# Audio decoders, processors and mixers
#
# CONFIG_VIDEO_TVAUDIO is not set
# CONFIG_VIDEO_TDA7432 is not set
# CONFIG_VIDEO_TDA9840 is not set
# CONFIG_VIDEO_TDA1997X is not set
# CONFIG_VIDEO_TEA6415C is not set
# CONFIG_VIDEO_TEA6420 is not set
# CONFIG_VIDEO_MSP3400 is not set
# CONFIG_VIDEO_CS3308 is not set
# CONFIG_VIDEO_CS5345 is not set
# CONFIG_VIDEO_CS53L32A is not set
# CONFIG_VIDEO_TLV320AIC23B is not set
# CONFIG_VIDEO_UDA1342 is not set
# CONFIG_VIDEO_WM8775 is not set
# CONFIG_VIDEO_WM8739 is not set
# CONFIG_VIDEO_VP27SMPX is not set
# CONFIG_VIDEO_SONY_BTF_MPX is not set
# end of Audio decoders, processors and mixers
#
# RDS decoders
#
# CONFIG_VIDEO_SAA6588 is not set
# end of RDS decoders
#
# Video decoders
#CONFIG_VIDEO_ADV7180=m
# CONFIG_VIDEO_ADV7183 is not set
# CONFIG_VIDEO_ADV748X is not setCONFIG_VIDEO_ADV7604=mCONFIG_VIDEO_ADV7604_CEC=y
# CONFIG_VIDEO_ADV7842 is not set
# CONFIG_VIDEO_BT819 is not set
# CONFIG_VIDEO_BT856 is not set
# CONFIG_VIDEO_BT866 is not set
# CONFIG_VIDEO_KS0127 is not setCONFIG_VIDEO_ML86V7667=m
# CONFIG_VIDEO_SAA7110 is not set
# CONFIG_VIDEO_SAA711X is not set
# CONFIG_VIDEO_TC358743 is not set
# CONFIG_VIDEO_TVP514X is not set
# CONFIG_VIDEO_TVP5150 is not set
# CONFIG_VIDEO_TVP7002 is not set
# CONFIG_VIDEO_TW2804 is not set
# CONFIG_VIDEO_TW9903 is not set
# CONFIG_VIDEO_TW9906 is not set
# CONFIG_VIDEO_TW9910 is not set
# CONFIG_VIDEO_VPX3220 is not set
# CONFIG_VIDEO_MAX9286 is not set
#
# Video and audio decoders
#
# CONFIG_VIDEO_SAA717X is not set
# CONFIG_VIDEO_CX25840 is not set
# end of Video decoders
#
# Video encoders
#
# CONFIG_VIDEO_SAA7127 is not set
# CONFIG_VIDEO_SAA7185 is not set
# CONFIG_VIDEO_ADV7170 is not set
# CONFIG_VIDEO_ADV7175 is not set
# CONFIG_VIDEO_ADV7343 is not set
# CONFIG_VIDEO_ADV7393 is not set
# CONFIG_VIDEO_AD9389B is not set
# CONFIG_VIDEO_AK881X is not set
# CONFIG_VIDEO_THS8200 is not set
# end of Video encoders
#
# Video improvement chips
#
# CONFIG_VIDEO_UPD64031A is not set
# CONFIG_VIDEO_UPD64083 is not set
# end of Video improvement chips
#
# Audio/Video compression chips
#
# CONFIG_VIDEO_SAA6752HS is not set
# end of Audio/Video compression chips
#
# SDR tuner chips
#
# CONFIG_SDR_MAX2175 is not set
# end of SDR tuner chips
#
# Miscellaneous helper chips
#
# CONFIG_VIDEO_THS7303 is not set
# CONFIG_VIDEO_M52790 is not set
# CONFIG_VIDEO_I2C is not set
# CONFIG_VIDEO_ST_MIPID02 is not set
# end of Miscellaneous helper chips
#
# Camera sensor devices
#
# CONFIG_VIDEO_HI556 is not set
# CONFIG_VIDEO_IMX214 is not set
# CONFIG_VIDEO_IMX219 is not set
# CONFIG_VIDEO_IMX258 is not set
# CONFIG_VIDEO_IMX274 is not set
# CONFIG_VIDEO_IMX290 is not set
# CONFIG_VIDEO_IMX319 is not set
# CONFIG_VIDEO_IMX355 is not set
# CONFIG_VIDEO_OV02A10 is not set
# CONFIG_VIDEO_OV2640 is not set
# CONFIG_VIDEO_OV2659 is not set
# CONFIG_VIDEO_OV2680 is not set
# CONFIG_VIDEO_OV2685 is not set
# CONFIG_VIDEO_OV5640 is not set
# CONFIG_VIDEO_OV5645 is not set
# CONFIG_VIDEO_OV5647 is not set
# CONFIG_VIDEO_OV6650 is not set
# CONFIG_VIDEO_OV5670 is not set
# CONFIG_VIDEO_OV5675 is not set
# CONFIG_VIDEO_OV5695 is not set
# CONFIG_VIDEO_OV7251 is not set
# CONFIG_VIDEO_OV772X is not set
# CONFIG_VIDEO_OV7640 is not setCONFIG_VIDEO_OV7670=m
# CONFIG_VIDEO_OV7740 is not set
# CONFIG_VIDEO_OV8856 is not set
# CONFIG_VIDEO_OV9640 is not set
# CONFIG_VIDEO_OV9650 is not set
# CONFIG_VIDEO_OV13858 is not set
# CONFIG_VIDEO_VS6624 is not set
# CONFIG_VIDEO_MT9M001 is not set
# CONFIG_VIDEO_MT9M032 is not set
# CONFIG_VIDEO_MT9M111 is not set
# CONFIG_VIDEO_MT9P031 is not set
# CONFIG_VIDEO_MT9T001 is not set
# CONFIG_VIDEO_MT9T112 is not set
# CONFIG_VIDEO_MT9V011 is not set
# CONFIG_VIDEO_MT9V032 is not set
# CONFIG_VIDEO_MT9V111 is not set
# CONFIG_VIDEO_SR030PC30 is not set
# CONFIG_VIDEO_NOON010PC30 is not set
# CONFIG_VIDEO_M5MOLS is not set
# CONFIG_VIDEO_RDACM20 is not set
# CONFIG_VIDEO_RJ54N1 is not set
# CONFIG_VIDEO_S5K6AA is not set
# CONFIG_VIDEO_S5K6A3 is not set
# CONFIG_VIDEO_S5K4ECGX is not set
# CONFIG_VIDEO_S5K5BAF is not set
# CONFIG_VIDEO_CCS is not set
# CONFIG_VIDEO_ET8EK8 is not set
# CONFIG_VIDEO_S5C73M3 is not set
# end of Camera sensor devices
#
# Lens drivers
#
# CONFIG_VIDEO_AD5820 is not set
# CONFIG_VIDEO_AK7375 is not set
# CONFIG_VIDEO_DW9714 is not set
# CONFIG_VIDEO_DW9768 is not set
# CONFIG_VIDEO_DW9807_VCM is not set
# end of Lens drivers
#
# Flash devices
#
# CONFIG_VIDEO_ADP1653 is not set
# CONFIG_VIDEO_LM3560 is not set
# CONFIG_VIDEO_LM3646 is not set
# end of Flash devices
#
# SPI helper chips
#
# CONFIG_VIDEO_GS1662 is not set
# end of SPI helper chips
#
# Media SPI Adapters
#CONFIG_CXD2880_SPI_DRV=m
# end of Media SPI Adapters
CONFIG_MEDIA_TUNER=m
#
# Customize TV tuners
#CONFIG_MEDIA_TUNER_SIMPLE=mCONFIG_MEDIA_TUNER_TDA18250=mCONFIG_MEDIA_TUNER_TDA8290=mCONFIG_MEDIA_TUNER_TDA827X=mCONFIG_MEDIA_TUNER_TDA18271=mCONFIG_MEDIA_TUNER_TDA9887=mCONFIG_MEDIA_TUNER_TEA5761=mCONFIG_MEDIA_TUNER_TEA5767=mCONFIG_MEDIA_TUNER_MSI001=mCONFIG_MEDIA_TUNER_MT20XX=mCONFIG_MEDIA_TUNER_MT2060=mCONFIG_MEDIA_TUNER_MT2063=mCONFIG_MEDIA_TUNER_MT2266=mCONFIG_MEDIA_TUNER_MT2131=mCONFIG_MEDIA_TUNER_QT1010=mCONFIG_MEDIA_TUNER_XC2028=mCONFIG_MEDIA_TUNER_XC5000=mCONFIG_MEDIA_TUNER_XC4000=mCONFIG_MEDIA_TUNER_MXL5005S=mCONFIG_MEDIA_TUNER_MXL5007T=mCONFIG_MEDIA_TUNER_MC44S803=mCONFIG_MEDIA_TUNER_MAX2165=mCONFIG_MEDIA_TUNER_TDA18218=mCONFIG_MEDIA_TUNER_FC0011=mCONFIG_MEDIA_TUNER_FC0012=mCONFIG_MEDIA_TUNER_FC0013=mCONFIG_MEDIA_TUNER_TDA18212=mCONFIG_MEDIA_TUNER_E4000=mCONFIG_MEDIA_TUNER_FC2580=mCONFIG_MEDIA_TUNER_M88RS6000T=mCONFIG_MEDIA_TUNER_TUA9001=mCONFIG_MEDIA_TUNER_SI2157=mCONFIG_MEDIA_TUNER_IT913X=mCONFIG_MEDIA_TUNER_R820T=mCONFIG_MEDIA_TUNER_MXL301RF=mCONFIG_MEDIA_TUNER_QM1D1C0042=mCONFIG_MEDIA_TUNER_QM1D1B0004=m
# end of Customize TV tuners
#
# Customise DVB Frontends
#
#
# Multistandard (satellite) frontends
#CONFIG_DVB_STB0899=mCONFIG_DVB_STB6100=m
CONFIG_DVB_STV090x=mCONFIG_DVB_STV0910=m
CONFIG_DVB_STV6110x=mCONFIG_DVB_STV6111=mCONFIG_DVB_MXL5XX=mCONFIG_DVB_M88DS3103=m
#
# Multistandard (cable + terrestrial) frontends
#CONFIG_DVB_DRXK=mCONFIG_DVB_TDA18271C2DD=mCONFIG_DVB_SI2165=mCONFIG_DVB_MN88472=mCONFIG_DVB_MN88473=m
#
# DVB-S (satellite) frontends
#CONFIG_DVB_CX24110=mCONFIG_DVB_CX24123=mCONFIG_DVB_MT312=mCONFIG_DVB_ZL10036=mCONFIG_DVB_ZL10039=mCONFIG_DVB_S5H1420=mCONFIG_DVB_STV0288=mCONFIG_DVB_STB6000=mCONFIG_DVB_STV0299=mCONFIG_DVB_STV6110=mCONFIG_DVB_STV0900=mCONFIG_DVB_TDA8083=mCONFIG_DVB_TDA10086=mCONFIG_DVB_TDA8261=mCONFIG_DVB_VES1X93=mCONFIG_DVB_TUNER_ITD1000=mCONFIG_DVB_TUNER_CX24113=mCONFIG_DVB_TDA826X=mCONFIG_DVB_TUA6100=mCONFIG_DVB_CX24116=mCONFIG_DVB_CX24117=mCONFIG_DVB_CX24120=mCONFIG_DVB_SI21XX=mCONFIG_DVB_TS2020=mCONFIG_DVB_DS3000=mCONFIG_DVB_MB86A16=mCONFIG_DVB_TDA10071=m
#
# DVB-T (terrestrial) frontends
#CONFIG_DVB_SP8870=mCONFIG_DVB_SP887X=mCONFIG_DVB_CX22700=mCONFIG_DVB_CX22702=mCONFIG_DVB_S5H1432=mCONFIG_DVB_DRXD=mCONFIG_DVB_L64781=mCONFIG_DVB_TDA1004X=mCONFIG_DVB_NXT6000=mCONFIG_DVB_MT352=mCONFIG_DVB_ZL10353=mCONFIG_DVB_DIB3000MB=mCONFIG_DVB_DIB3000MC=mCONFIG_DVB_DIB7000M=mCONFIG_DVB_DIB7000P=mCONFIG_DVB_DIB9000=mCONFIG_DVB_TDA10048=mCONFIG_DVB_AF9013=mCONFIG_DVB_EC100=mCONFIG_DVB_STV0367=mCONFIG_DVB_CXD2820R=mCONFIG_DVB_CXD2841ER=mCONFIG_DVB_RTL2830=mCONFIG_DVB_RTL2832=mCONFIG_DVB_RTL2832_SDR=mCONFIG_DVB_SI2168=mCONFIG_DVB_ZD1301_DEMOD=mCONFIG_DVB_CXD2880=m
#
# DVB-C (cable) frontends
#CONFIG_DVB_VES1820=mCONFIG_DVB_TDA10021=mCONFIG_DVB_TDA10023=mCONFIG_DVB_STV0297=m
#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends #CONFIG_DVB_NXT200X=mCONFIG_DVB_OR51211=mCONFIG_DVB_OR51132=mCONFIG_DVB_BCM3510=mCONFIG_DVB_LGDT330X=mCONFIG_DVB_LGDT3305=mCONFIG_DVB_LGDT3306A=mCONFIG_DVB_LG2160=mCONFIG_DVB_S5H1409=mCONFIG_DVB_AU8522=mCONFIG_DVB_AU8522_DTV=mCONFIG_DVB_AU8522_V4L=mCONFIG_DVB_S5H1411=m
#
# ISDB-T (terrestrial) frontends
#CONFIG_DVB_S921=mCONFIG_DVB_DIB8000=mCONFIG_DVB_MB86A20S=m
#
# ISDB-S (satellite) & ISDB-T (terrestrial) frontends #CONFIG_DVB_TC90522=mCONFIG_DVB_MN88443X=m
#
# Digital terrestrial only tuners/PLL
#CONFIG_DVB_PLL=mCONFIG_DVB_TUNER_DIB0070=mCONFIG_DVB_TUNER_DIB0090=m
#
# SEC control devices for DVB-S
#CONFIG_DVB_DRX39XYJ=mCONFIG_DVB_LNBH25=mCONFIG_DVB_LNBH29=mCONFIG_DVB_LNBP21=mCONFIG_DVB_LNBP22=mCONFIG_DVB_ISL6405=mCONFIG_DVB_ISL6421=mCONFIG_DVB_ISL6423=mCONFIG_DVB_A8293=mCONFIG_DVB_LGS8GL5=mCONFIG_DVB_LGS8GXX=mCONFIG_DVB_ATBM8830=m
CONFIG_DVB_TDA665x=mCONFIG_DVB_IX2505V=mCONFIG_DVB_M88RS2000=mCONFIG_DVB_AF9033=mCONFIG_DVB_HORUS3A=mCONFIG_DVB_ASCOT2E=mCONFIG_DVB_HELENE=m
#
# Common Interface (EN50221) controller drivers
#CONFIG_DVB_CXD2099=mCONFIG_DVB_SP2=m
# end of Customise DVB Frontends
#
# Tools to develop new frontends
#
# CONFIG_DVB_DUMMY_FE is not set
# end of Media ancillary drivers
#
# Graphics support
#CONFIG_VGA_ARB=y CONFIG_VGA_ARB_MAX_GPUS=16 CONFIG_TEGRA_HOST1X=y CONFIG_TEGRA_HOST1X_FIREWALL=y CONFIG_IMX_IPUV3_CORE=mCONFIG_DRM=yCONFIG_DRM_MIPI_DSI=y
# CONFIG_DRM_DP_AUX_CHARDEV is not set
# CONFIG_DRM_DEBUG_MM is not set
# CONFIG_DRM_DEBUG_SELFTEST is not set CONFIG_DRM_KMS_HELPER=y CONFIG_DRM_KMS_FB_HELPER=y
# CONFIG_DRM_DEBUG_DP_MST_TOPOLOGY_REFS is not set CONFIG_DRM_FBDEV_EMULATION=y CONFIG_DRM_FBDEV_OVERALLOC=100
# CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM is not set # CONFIG_DRM_LOAD_EDID_FIRMWARE is not set # CONFIG_DRM_DP_CEC is not set CONFIG_DRM_TTM=mCONFIG_DRM_TTM_HELPER=m CONFIG_DRM_GEM_CMA_HELPER=y CONFIG_DRM_KMS_CMA_HELPER=y CONFIG_DRM_GEM_SHMEM_HELPER=y CONFIG_DRM_VM=yCONFIG_DRM_SCHED=m
#
# I2C encoder or helper chips
#
# CONFIG_DRM_I2C_CH7006 is not set
# CONFIG_DRM_I2C_SIL164 is not set
# CONFIG_DRM_I2C_NXP_TDA998X is not set
# CONFIG_DRM_I2C_NXP_TDA9950 is not set
# end of I2C encoder or helper chips
#
# ARM devices
#
# CONFIG_DRM_HDLCD is not set
# CONFIG_DRM_MALI_DISPLAY is not set
# CONFIG_DRM_KOMEDA is not set
# end of ARM devices
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_AMDGPU is not setCONFIG_DRM_NOUVEAU=mCONFIG_NOUVEAU_LEGACY_CTX_SUPPORT=yCONFIG_NOUVEAU_PLATFORM_DRIVER=yCONFIG_NOUVEAU_DEBUG=5CONFIG_NOUVEAU_DEBUG_DEFAULT=3
# CONFIG_NOUVEAU_DEBUG_MMU is not set
# CONFIG_NOUVEAU_DEBUG_PUSH is not setCONFIG_DRM_NOUVEAU_BACKLIGHT=y
# CONFIG_DRM_VGEM is not set
# CONFIG_DRM_VKMS is not setCONFIG_DRM_EXYNOS=m
#
# CRTCs
#CONFIG_DRM_EXYNOS_FIMD=y
# CONFIG_DRM_EXYNOS5433_DECON is not set
# CONFIG_DRM_EXYNOS7_DECON is not setCONFIG_DRM_EXYNOS_MIXER=y
# CONFIG_DRM_EXYNOS_VIDI is not set
#
# Encoders and Bridges
#CONFIG_DRM_EXYNOS_DPI=yCONFIG_DRM_EXYNOS_DSI=yCONFIG_DRM_EXYNOS_DP=yCONFIG_DRM_EXYNOS_HDMI=y
#
# Sub-drivers
#
# CONFIG_DRM_EXYNOS_G2D is not set
# CONFIG_DRM_EXYNOS_FIMC is not set
# CONFIG_DRM_EXYNOS_ROTATOR is not set
# CONFIG_DRM_EXYNOS_SCALER is not setCONFIG_DRM_ROCKCHIP=mCONFIG_ROCKCHIP_ANALOGIX_DP=y
# CONFIG_ROCKCHIP_CDN_DP is not setCONFIG_ROCKCHIP_DW_HDMI=yCONFIG_ROCKCHIP_DW_MIPI_DSI=yCONFIG_ROCKCHIP_INNO_HDMI=y
# CONFIG_ROCKCHIP_LVDS is not set
# CONFIG_ROCKCHIP_RGB is not set
# CONFIG_ROCKCHIP_RK3066_HDMI is not set
# CONFIG_DRM_UDL is not set
# CONFIG_DRM_AST is not set
# CONFIG_DRM_MGAG200 is not set
# CONFIG_DRM_ARMADA is not setCONFIG_DRM_ATMEL_HLCDC=mCONFIG_DRM_RCAR_DU=mCONFIG_DRM_RCAR_CMM=m
# CONFIG_DRM_RCAR_DW_HDMI is not setCONFIG_DRM_RCAR_LVDS=y
# CONFIG_DRM_RCAR_VSP is not setCONFIG_DRM_SUN4I=mCONFIG_DRM_SUN4I_HDMI=m
# CONFIG_DRM_SUN4I_HDMI_CEC is not setCONFIG_DRM_SUN4I_BACKEND=mCONFIG_DRM_SUN6I_DSI=m
# CONFIG_DRM_SUN8I_DW_HDMI is not setCONFIG_DRM_SUN8I_MIXER=mCONFIG_DRM_SUN8I_TCON_TOP=m
# CONFIG_DRM_OMAP is not set
# CONFIG_DRM_TILCDC is not set
# CONFIG_DRM_QXL is not set
# CONFIG_DRM_BOCHS is not setCONFIG_DRM_VIRTIO_GPU=yCONFIG_DRM_MSM=mCONFIG_DRM_MSM_GPU_STATE=y
# CONFIG_DRM_MSM_REGISTER_LOGGING is not set
# CONFIG_DRM_MSM_GPU_SUDO is not setCONFIG_DRM_MSM_HDMI_HDCP=yCONFIG_DRM_MSM_DP=yCONFIG_DRM_MSM_DSI=yCONFIG_DRM_MSM_DSI_PLL=yCONFIG_DRM_MSM_DSI_28NM_PHY=yCONFIG_DRM_MSM_DSI_20NM_PHY=yCONFIG_DRM_MSM_DSI_28NM_8960_PHY=yCONFIG_DRM_MSM_DSI_14NM_PHY=yCONFIG_DRM_MSM_DSI_10NM_PHY=yCONFIG_DRM_MSM_DSI_7NM_PHY=yCONFIG_DRM_FSL_DCU=mCONFIG_DRM_TEGRA=y
# CONFIG_DRM_TEGRA_DEBUG is not set
# CONFIG_DRM_TEGRA_STAGING is not setCONFIG_DRM_STM=mCONFIG_DRM_STM_DSI=mCONFIG_DRM_PANEL=y
#
# Display Panels
#
# CONFIG_DRM_PANEL_ABT_Y030XX067A is not set
# CONFIG_DRM_PANEL_ARM_VERSATILE is not set
# CONFIG_DRM_PANEL_ASUS_Z00T_TM5P5_NT35596 is not set # CONFIG_DRM_PANEL_BOE_HIMAX8279D is not set
# CONFIG_DRM_PANEL_BOE_TV101WUM_NL6 is not set # CONFIG_DRM_PANEL_LVDS is not set CONFIG_DRM_PANEL_SIMPLE=y
# CONFIG_DRM_PANEL_ELIDA_KD35T133 is not set
# CONFIG_DRM_PANEL_FEIXIN_K101_IM2BA02 is not set # CONFIG_DRM_PANEL_FEIYANG_FY07024DI26A30D is not set # CONFIG_DRM_PANEL_ILITEK_IL9322 is not set
# CONFIG_DRM_PANEL_ILITEK_ILI9881C is not set
# CONFIG_DRM_PANEL_INNOLUX_P079ZCA is not set
# CONFIG_DRM_PANEL_JDI_LT070ME05000 is not set # CONFIG_DRM_PANEL_KHADAS_TS050 is not set
# CONFIG_DRM_PANEL_KINGDISPLAY_KD097D04 is not set # CONFIG_DRM_PANEL_LEADTEK_LTK050H3146W is not set # CONFIG_DRM_PANEL_LEADTEK_LTK500HD1829 is not set CONFIG_DRM_PANEL_SAMSUNG_LD9040=m
# CONFIG_DRM_PANEL_LG_LB035Q02 is not set
# CONFIG_DRM_PANEL_LG_LG4573 is not set
# CONFIG_DRM_PANEL_NEC_NL8048HL11 is not set
# CONFIG_DRM_PANEL_NOVATEK_NT35510 is not set
# CONFIG_DRM_PANEL_NOVATEK_NT36672A is not set # CONFIG_DRM_PANEL_NOVATEK_NT39016 is not set
# CONFIG_DRM_PANEL_MANTIX_MLAF057WE51 is not set # CONFIG_DRM_PANEL_OLIMEX_LCD_OLINUXINO is not set CONFIG_DRM_PANEL_ORISETECH_OTM8009A=m
# CONFIG_DRM_PANEL_OSD_OSD101T2587_53TS is not set # CONFIG_DRM_PANEL_PANASONIC_VVX10F034N00 is not set # CONFIG_DRM_PANEL_RASPBERRYPI_TOUCHSCREEN is not set # CONFIG_DRM_PANEL_RAYDIUM_RM67191 is not set CONFIG_DRM_PANEL_RAYDIUM_RM68200=m
# CONFIG_DRM_PANEL_RONBO_RB070D30 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6D16D0 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E3HA2 is not set CONFIG_DRM_PANEL_SAMSUNG_S6E63J0X03=m
# CONFIG_DRM_PANEL_SAMSUNG_S6E63M0 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E88A0_AMS452EF01 is not set CONFIG_DRM_PANEL_SAMSUNG_S6E8AA0=m
# CONFIG_DRM_PANEL_SAMSUNG_SOFEF00 is not set
# CONFIG_DRM_PANEL_SEIKO_43WVF1G is not set
# CONFIG_DRM_PANEL_SHARP_LQ101R1SX01 is not set # CONFIG_DRM_PANEL_SHARP_LS037V7DW01 is not set # CONFIG_DRM_PANEL_SHARP_LS043T1LE01 is not set # CONFIG_DRM_PANEL_SITRONIX_ST7701 is not set
# CONFIG_DRM_PANEL_SITRONIX_ST7703 is not set
# CONFIG_DRM_PANEL_SITRONIX_ST7789V is not set # CONFIG_DRM_PANEL_SONY_ACX424AKP is not set
# CONFIG_DRM_PANEL_SONY_ACX565AKM is not set
# CONFIG_DRM_PANEL_TDO_TL070WSH30 is not set
# CONFIG_DRM_PANEL_TPO_TD028TTEC1 is not set
# CONFIG_DRM_PANEL_TPO_TD043MTEA1 is not set
# CONFIG_DRM_PANEL_TPO_TPG110 is not set
# CONFIG_DRM_PANEL_TRULY_NT35597_WQXGA is not set # CONFIG_DRM_PANEL_VISIONOX_RM69299 is not set # CONFIG_DRM_PANEL_XINPENG_XPP055C272 is not set
# end of Display Panels
CONFIG_DRM_BRIDGE=yCONFIG_DRM_PANEL_BRIDGE=y
#
# Display Interface Bridges
#
# CONFIG_DRM_CDNS_DSI is not set
# CONFIG_DRM_CHRONTEL_CH7033 is not set
# CONFIG_DRM_DISPLAY_CONNECTOR is not set
# CONFIG_DRM_LONTIUM_LT9611 is not set
# CONFIG_DRM_LONTIUM_LT9611UXC is not set
# CONFIG_DRM_LVDS_CODEC is not set
# CONFIG_DRM_MEGACHIPS_STDPXXXX_GE_B850V3_FW is not set # CONFIG_DRM_NWL_MIPI_DSI is not set CONFIG_DRM_NXP_PTN3460=m CONFIG_DRM_PARADE_PS8622=m
# CONFIG_DRM_PARADE_PS8640 is not set
# CONFIG_DRM_SIL_SII8620 is not set CONFIG_DRM_SII902X=mCONFIG_DRM_SII9234=m CONFIG_DRM_SIMPLE_BRIDGE=m
# CONFIG_DRM_THINE_THC63LVD1024 is not set
# CONFIG_DRM_TOSHIBA_TC358762 is not set CONFIG_DRM_TOSHIBA_TC358764=m
# CONFIG_DRM_TOSHIBA_TC358767 is not set
# CONFIG_DRM_TOSHIBA_TC358768 is not set
# CONFIG_DRM_TOSHIBA_TC358775 is not set
# CONFIG_DRM_TI_TFP410 is not set
# CONFIG_DRM_TI_SN65DSI86 is not set
# CONFIG_DRM_TI_TPD12S015 is not set
# CONFIG_DRM_ANALOGIX_ANX6345 is not set
# CONFIG_DRM_ANALOGIX_ANX78XX is not set CONFIG_DRM_ANALOGIX_DP=m
# CONFIG_DRM_ANALOGIX_ANX7625 is not set CONFIG_DRM_I2C_ADV7511=m CONFIG_DRM_I2C_ADV7511_AUDIO=y CONFIG_DRM_I2C_ADV7511_CEC=y
# CONFIG_DRM_CDNS_MHDP8546 is not set CONFIG_DRM_DW_HDMI=m
# CONFIG_DRM_DW_HDMI_AHB_AUDIO is not set
# CONFIG_DRM_DW_HDMI_I2S_AUDIO is not set
# CONFIG_DRM_DW_HDMI_CEC is not set CONFIG_DRM_DW_MIPI_DSI=m
# end of Display Interface Bridges
CONFIG_DRM_STI=mCONFIG_DRM_IMX=mCONFIG_DRM_IMX_PARALLEL_DISPLAY=mCONFIG_DRM_IMX_TVE=mCONFIG_DRM_IMX_LDB=mCONFIG_DRM_IMX_HDMI=m
# CONFIG_DRM_V3D is not setCONFIG_DRM_VC4=m
# CONFIG_DRM_VC4_HDMI_CEC is not setCONFIG_DRM_ETNAVIV=mCONFIG_DRM_ETNAVIV_THERMAL=y
# CONFIG_DRM_ARCPGU is not set
# CONFIG_DRM_MEDIATEK is not setCONFIG_DRM_MXS=yCONFIG_DRM_MXSFB=m
# CONFIG_DRM_MESON is not set
# CONFIG_DRM_CIRRUS_QEMU is not set
# CONFIG_DRM_GM12U320 is not set
# CONFIG_TINYDRM_HX8357D is not set
# CONFIG_TINYDRM_ILI9225 is not set
# CONFIG_TINYDRM_ILI9341 is not set
# CONFIG_TINYDRM_ILI9486 is not set
# CONFIG_TINYDRM_MI0283QT is not set
# CONFIG_TINYDRM_REPAPER is not set
# CONFIG_TINYDRM_ST7586 is not set
# CONFIG_TINYDRM_ST7735R is not setCONFIG_DRM_PL111=m
# CONFIG_DRM_TVE200 is not setCONFIG_DRM_LIMA=mCONFIG_DRM_PANFROST=mCONFIG_DRM_ASPEED_GFX=m
# CONFIG_DRM_MCDE is not set
# CONFIG_DRM_TIDSS is not setCONFIG_DRM_LEGACY=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not setCONFIG_DRM_PANEL_ORIENTATION_QUIRKS=y
#
# Frame buffer Devices
#CONFIG_FB_CMDLINE=yCONFIG_FB_NOTIFY=yCONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not setCONFIG_FB_CFB_FILLRECT=yCONFIG_FB_CFB_COPYAREA=yCONFIG_FB_CFB_IMAGEBLIT=yCONFIG_FB_SYS_FILLRECT=yCONFIG_FB_SYS_COPYAREA=yCONFIG_FB_SYS_IMAGEBLIT=yCONFIG_FB_PROVIDE_GET_FB_UNMAPPED_AREA=y
# CONFIG_FB_FOREIGN_ENDIAN is not setCONFIG_FB_SYS_FOPS=yCONFIG_FB_DEFERRED_IO=yCONFIG_FB_BACKLIGHT=yCONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_ARMCLCD is not set
# CONFIG_FB_IMX is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not setCONFIG_FB_EFI=y
# CONFIG_FB_OPENCORES is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I740 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_VT8500 is not setCONFIG_FB_WM8505=y
# CONFIG_FB_WMT_GE_ROPS is not setCONFIG_FB_SH_MOBILE_LCDC=y
# CONFIG_FB_SMSCUFX is not set
# CONFIG_FB_UDL is not set
# CONFIG_FB_IBM_GXT4500 is not set
# CONFIG_FB_XILINX is not set
# CONFIG_FB_DA8XX is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not setCONFIG_FB_MX3=yCONFIG_FB_SIMPLE=y
# CONFIG_FB_SSD1307 is not set
# CONFIG_FB_SM712 is not set
# CONFIG_FB_OMAP2 is not set
# end of Frame buffer Devices
#
# Backlight & LCD device support
#
# CONFIG_LCD_CLASS_DEVICE is not setCONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_KTD253 is not setCONFIG_BACKLIGHT_PWM=y
# CONFIG_BACKLIGHT_QCOM_WLED is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_LM3630A is not set
# CONFIG_BACKLIGHT_LM3639 is not set
# CONFIG_BACKLIGHT_LP855X is not set
# CONFIG_BACKLIGHT_PANDORA is not set
# CONFIG_BACKLIGHT_TPS65217 is not setCONFIG_BACKLIGHT_AS3711=yCONFIG_BACKLIGHT_GPIO=y
# CONFIG_BACKLIGHT_LV5207LP is not set
# CONFIG_BACKLIGHT_BD6107 is not set
# CONFIG_BACKLIGHT_ARCXCNN is not set
# CONFIG_BACKLIGHT_LED is not set
# end of Backlight & LCD device support
CONFIG_VIDEOMODE_HELPERS=yCONFIG_HDMI=y
#
# Console display driver support
#CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER is not set
# end of Console display driver support
# CONFIG_LOGO is not set
# end of Graphics support
CONFIG_SOUND=mCONFIG_SND=mCONFIG_SND_TIMER=mCONFIG_SND_PCM=mCONFIG_SND_PCM_ELD=yCONFIG_SND_PCM_IEC958=yCONFIG_SND_DMAENGINE_PCM=mCONFIG_SND_HWDEP=mCONFIG_SND_RAWMIDI=mCONFIG_SND_JACK=yCONFIG_SND_JACK_INPUT_DEV=y
# CONFIG_SND_OSSEMUL is not setCONFIG_SND_PCM_TIMER=y
# CONFIG_SND_HRTIMER is not setCONFIG_SND_DYNAMIC_MINORS=yCONFIG_SND_MAX_CARDS=32CONFIG_SND_SUPPORT_OLD_API=yCONFIG_SND_PROC_FS=yCONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not setCONFIG_SND_VMASTER=y
# CONFIG_SND_SEQUENCER is not setCONFIG_SND_DRIVERS=y
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_ALOOP is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not setCONFIG_SND_PCI=y
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AW2 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_OXYGEN is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CTXFI is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_INDIGOIOX is not set
# CONFIG_SND_INDIGODJX is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_LOLA is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SE6X is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VIRTUOSO is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
#
# HD-Audio
#CONFIG_SND_HDA=mCONFIG_SND_HDA_GENERIC_LEDS=y
# CONFIG_SND_HDA_INTEL is not setCONFIG_SND_HDA_TEGRA=m
# CONFIG_SND_HDA_HWDEP is not setCONFIG_SND_HDA_RECONFIG=yCONFIG_SND_HDA_INPUT_BEEP=yCONFIG_SND_HDA_INPUT_BEEP_MODE=1CONFIG_SND_HDA_PATCH_LOADER=yCONFIG_SND_HDA_CODEC_REALTEK=m
# CONFIG_SND_HDA_CODEC_ANALOG is not set
# CONFIG_SND_HDA_CODEC_SIGMATEL is not set
# CONFIG_SND_HDA_CODEC_VIA is not setCONFIG_SND_HDA_CODEC_HDMI=m
# CONFIG_SND_HDA_CODEC_CIRRUS is not set
# CONFIG_SND_HDA_CODEC_CONEXANT is not set
# CONFIG_SND_HDA_CODEC_CA0110 is not set
# CONFIG_SND_HDA_CODEC_CA0132 is not set
# CONFIG_SND_HDA_CODEC_CMEDIA is not set
# CONFIG_SND_HDA_CODEC_SI3054 is not setCONFIG_SND_HDA_GENERIC=mCONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
# end of HD-Audio
CONFIG_SND_HDA_CORE=mCONFIG_SND_HDA_ALIGNED_MMIO=yCONFIG_SND_HDA_COMPONENT=yCONFIG_SND_HDA_PREALLOC_SIZE=64CONFIG_SND_ARM=y
# CONFIG_SND_ARMAACI is not setCONFIG_SND_PXA2XX_LIB=m
#
# Atmel devices (AT91)
#
# CONFIG_SND_ATMEL_AC97C is not set
# end of Atmel devices (AT91)
CONFIG_SND_SPI=y
# CONFIG_SND_AT73C213 is not setCONFIG_SND_USB=yCONFIG_SND_USB_AUDIO=mCONFIG_SND_USB_AUDIO_USE_MEDIA_CONTROLLER=y
# CONFIG_SND_USB_UA101 is not set
# CONFIG_SND_USB_CAIAQ is not set
# CONFIG_SND_USB_6FIRE is not set
# CONFIG_SND_USB_HIFACE is not set
# CONFIG_SND_BCD2000 is not set
# CONFIG_SND_USB_POD is not set
# CONFIG_SND_USB_PODHD is not set
# CONFIG_SND_USB_TONEPORT is not set
# CONFIG_SND_USB_VARIAX is not setCONFIG_SND_SOC=mCONFIG_SND_SOC_AC97_BUS=yCONFIG_SND_SOC_GENERIC_DMAENGINE_PCM=y
# CONFIG_SND_SOC_ADI is not set
# CONFIG_SND_SOC_AMD_ACP is not setCONFIG_SND_ATMEL_SOC=mCONFIG_SND_ATMEL_SOC_PDC=yCONFIG_SND_ATMEL_SOC_DMA=yCONFIG_SND_ATMEL_SOC_SSC=m
# CONFIG_SND_ATMEL_SOC_SSC_PDC is not setCONFIG_SND_ATMEL_SOC_SSC_DMA=m
# CONFIG_SND_AT91_SOC_SAM9G20_WM8731 is not setCONFIG_SND_ATMEL_SOC_WM8904=m
# CONFIG_SND_AT91_SOC_SAM9X5_WM8731 is not set
# CONFIG_SND_ATMEL_SOC_CLASSD is not setCONFIG_SND_ATMEL_SOC_PDMIC=m
# CONFIG_SND_ATMEL_SOC_TSE850_PCM5142 is not setCONFIG_SND_ATMEL_SOC_I2S=m
# CONFIG_SND_SOC_MIKROE_PROTO is not set
# CONFIG_SND_MCHP_SOC_I2S_MCC is not set
# CONFIG_SND_MCHP_SOC_SPDIFTX is not set
# CONFIG_SND_MCHP_SOC_SPDIFRX is not setCONFIG_SND_BCM2835_SOC_I2S=m
# CONFIG_SND_SOC_CYGNUS is not set
# CONFIG_SND_BCM63XX_I2S_WHISTLER is not set
# CONFIG_SND_DESIGNWARE_I2S is not set
#
# SoC Audio for Freescale CPUs
#
#
# Common SoC Audio options for Freescale CPUs:
#
# CONFIG_SND_SOC_FSL_ASRC is not setCONFIG_SND_SOC_FSL_SAI=m
# CONFIG_SND_SOC_FSL_MQS is not set
# CONFIG_SND_SOC_FSL_AUDMIX is not set
# CONFIG_SND_SOC_FSL_SSI is not set
# CONFIG_SND_SOC_FSL_SPDIF is not set
# CONFIG_SND_SOC_FSL_ESAI is not set
# CONFIG_SND_SOC_FSL_MICFIL is not set
# CONFIG_SND_SOC_FSL_XCVR is not set
# CONFIG_SND_SOC_FSL_AUD2HTX is not set
# CONFIG_SND_SOC_IMX_AUDMUX is not set
# CONFIG_SND_IMX_SOC is not set
# end of SoC Audio for Freescale CPUs
# CONFIG_SND_I2S_HI6210_I2S is not set
# CONFIG_SND_KIRKWOOD_SOC is not set
# CONFIG_SND_SOC_IMG is not set
# CONFIG_SND_SOC_MT2701 is not set
# CONFIG_SND_SOC_MT6797 is not set
# CONFIG_SND_SOC_MT8173 is not set
# CONFIG_SND_SOC_MT8183 is not set
# CONFIG_SND_SOC_MTK_BTCVSD is not set
# CONFIG_SND_SOC_MT8192 is not set
#
# ASoC support for Amlogic platforms
#
# CONFIG_SND_MESON_AIU is not set
# CONFIG_SND_MESON_AXG_FRDDR is not set
# CONFIG_SND_MESON_AXG_TODDR is not set
# CONFIG_SND_MESON_AXG_TDMIN is not set
# CONFIG_SND_MESON_AXG_TDMOUT is not set
# CONFIG_SND_MESON_AXG_SOUND_CARD is not set
# CONFIG_SND_MESON_AXG_SPDIFOUT is not set
# CONFIG_SND_MESON_AXG_SPDIFIN is not set
# CONFIG_SND_MESON_AXG_PDM is not set
# CONFIG_SND_MESON_GX_SOUND_CARD is not set
# CONFIG_SND_MESON_G12A_TOACODEC is not set
# CONFIG_SND_MESON_G12A_TOHDMITX is not set
# CONFIG_SND_SOC_MESON_T9015 is not set
# end of ASoC support for Amlogic platforms
CONFIG_SND_PXA_SOC_SSP=m
# CONFIG_SND_MMP_SOC_SSPA is not setCONFIG_SND_PXA910_SOC=m
# CONFIG_SND_SOC_QCOM is not setCONFIG_SND_SOC_ROCKCHIP=mCONFIG_SND_SOC_ROCKCHIP_I2S=m
# CONFIG_SND_SOC_ROCKCHIP_PDM is not setCONFIG_SND_SOC_ROCKCHIP_SPDIF=mCONFIG_SND_SOC_ROCKCHIP_MAX98090=mCONFIG_SND_SOC_ROCKCHIP_RT5645=m
# CONFIG_SND_SOC_RK3288_HDMI_ANALOG is not set
# CONFIG_SND_SOC_RK3399_GRU_SOUND is not setCONFIG_SND_SOC_SAMSUNG=mCONFIG_SND_SAMSUNG_PCM=m
# CONFIG_SND_SAMSUNG_SPDIF is not setCONFIG_SND_SAMSUNG_I2S=mCONFIG_SND_SOC_SAMSUNG_SMDK_WM8994=m
# CONFIG_SND_SOC_SAMSUNG_SMDK_SPDIF is not setCONFIG_SND_SOC_SMDK_WM8994_PCM=mCONFIG_SND_SOC_SNOW=mCONFIG_SND_SOC_ODROID=mCONFIG_SND_SOC_ARNDALE=m
# CONFIG_SND_SOC_SAMSUNG_ARIES_WM8994 is not setCONFIG_SND_SOC_SAMSUNG_MIDAS_WM1811=m
#
# SoC Audio support for Renesas SoCs
#CONFIG_SND_SOC_SH4_FSI=mCONFIG_SND_SOC_RCAR=m
# end of SoC Audio support for Renesas SoCs
# CONFIG_SND_SOC_SIRF is not set
# CONFIG_SND_SOC_SOF_TOPLEVEL is not setCONFIG_SND_SOC_STI=m
#
# STMicroelectronics STM32 SOC audio support
#CONFIG_SND_SOC_STM32_SAI=mCONFIG_SND_SOC_STM32_I2S=mCONFIG_SND_SOC_STM32_SPDIFRX=mCONFIG_SND_SOC_STM32_DFSDM=m
# end of STMicroelectronics STM32 SOC audio support
#
# Allwinner SoC Audio support
#CONFIG_SND_SUN4I_CODEC=m
# CONFIG_SND_SUN8I_CODEC is not set
# CONFIG_SND_SUN8I_CODEC_ANALOG is not set
# CONFIG_SND_SUN4I_I2S is not set
# CONFIG_SND_SUN4I_SPDIF is not set
# end of Allwinner SoC Audio support
CONFIG_SND_SOC_TEGRA=mCONFIG_SND_SOC_TEGRA20_AC97=mCONFIG_SND_SOC_TEGRA20_DAS=mCONFIG_SND_SOC_TEGRA20_I2S=m
# CONFIG_SND_SOC_TEGRA20_SPDIF is not setCONFIG_SND_SOC_TEGRA30_AHUB=mCONFIG_SND_SOC_TEGRA30_I2S=m
# CONFIG_SND_SOC_TEGRA210_AHUB is not set
# CONFIG_SND_SOC_TEGRA210_DMIC is not set
# CONFIG_SND_SOC_TEGRA210_I2S is not set
# CONFIG_SND_SOC_TEGRA186_DSPK is not set
# CONFIG_SND_SOC_TEGRA210_ADMAIF is not setCONFIG_SND_SOC_TEGRA_RT5640=mCONFIG_SND_SOC_TEGRA_WM8753=mCONFIG_SND_SOC_TEGRA_WM8903=mCONFIG_SND_SOC_TEGRA_WM9712=mCONFIG_SND_SOC_TEGRA_TRIMSLICE=mCONFIG_SND_SOC_TEGRA_ALC5632=mCONFIG_SND_SOC_TEGRA_MAX98090=m
# CONFIG_SND_SOC_TEGRA_RT5677 is not set
# CONFIG_SND_SOC_TEGRA_SGTL5000 is not set
#
# Audio support for Texas Instruments SoCs
#
#
# Texas Instruments DAI support for:
#
# CONFIG_SND_SOC_DAVINCI_MCASP is not set
# CONFIG_SND_SOC_OMAP_DMIC is not set
# CONFIG_SND_SOC_OMAP_MCBSP is not set
# CONFIG_SND_SOC_OMAP_MCPDM is not set
#
# Audio support for boards with Texas Instruments SoCs #
# CONFIG_SND_SOC_NOKIA_RX51 is not set
# CONFIG_SND_SOC_OMAP3_PANDORA is not set
# CONFIG_SND_SOC_OMAP3_TWL4030 is not set
# end of Audio support for Texas Instruments SoCs
# CONFIG_SND_SOC_UNIPHIER is not set
# CONFIG_SND_SOC_UX500 is not set
# CONFIG_SND_SOC_XILINX_I2S is not set
# CONFIG_SND_SOC_XILINX_AUDIO_FORMATTER is not set # CONFIG_SND_SOC_XILINX_SPDIF is not set
# CONFIG_SND_SOC_XTFPGA_I2S is not set
# CONFIG_ZX_TDM is not set CONFIG_SND_SOC_I2C_AND_SPI=m
#
# CODEC drivers
#CONFIG_SND_SOC_WM_HUBS=m
# CONFIG_SND_SOC_AC97_CODEC is not set
# CONFIG_SND_SOC_ADAU1372_I2C is not set
# CONFIG_SND_SOC_ADAU1372_SPI is not set
# CONFIG_SND_SOC_ADAU1701 is not set
# CONFIG_SND_SOC_ADAU1761_I2C is not set
# CONFIG_SND_SOC_ADAU1761_SPI is not set
# CONFIG_SND_SOC_ADAU7002 is not set
# CONFIG_SND_SOC_ADAU7118_HW is not set
# CONFIG_SND_SOC_ADAU7118_I2C is not set
# CONFIG_SND_SOC_AK4104 is not set
# CONFIG_SND_SOC_AK4118 is not set
# CONFIG_SND_SOC_AK4458 is not set
# CONFIG_SND_SOC_AK4554 is not set
# CONFIG_SND_SOC_AK4613 is not setCONFIG_SND_SOC_AK4642=m
# CONFIG_SND_SOC_AK5386 is not set
# CONFIG_SND_SOC_AK5558 is not set
# CONFIG_SND_SOC_ALC5623 is not setCONFIG_SND_SOC_ALC5632=m
# CONFIG_SND_SOC_BD28623 is not set
# CONFIG_SND_SOC_BT_SCO is not setCONFIG_SND_SOC_CPCAP=m
# CONFIG_SND_SOC_CROS_EC_CODEC is not set
# CONFIG_SND_SOC_CS35L32 is not set
# CONFIG_SND_SOC_CS35L33 is not set
# CONFIG_SND_SOC_CS35L34 is not set
# CONFIG_SND_SOC_CS35L35 is not set
# CONFIG_SND_SOC_CS35L36 is not set
# CONFIG_SND_SOC_CS42L42 is not setCONFIG_SND_SOC_CS42L51=mCONFIG_SND_SOC_CS42L51_I2C=m
# CONFIG_SND_SOC_CS42L52 is not set
# CONFIG_SND_SOC_CS42L56 is not set
# CONFIG_SND_SOC_CS42L73 is not set
# CONFIG_SND_SOC_CS4234 is not set
# CONFIG_SND_SOC_CS4265 is not set
# CONFIG_SND_SOC_CS4270 is not set
# CONFIG_SND_SOC_CS4271_I2C is not set
# CONFIG_SND_SOC_CS4271_SPI is not set
# CONFIG_SND_SOC_CS42XX8_I2C is not set
# CONFIG_SND_SOC_CS43130 is not set
# CONFIG_SND_SOC_CS4341 is not set
# CONFIG_SND_SOC_CS4349 is not set
# CONFIG_SND_SOC_CS53L30 is not set
# CONFIG_SND_SOC_CX2072X is not set
# CONFIG_SND_SOC_DA7213 is not setCONFIG_SND_SOC_DMIC=mCONFIG_SND_SOC_HDMI_CODEC=m
# CONFIG_SND_SOC_ES7134 is not set
# CONFIG_SND_SOC_ES7241 is not set
# CONFIG_SND_SOC_ES8316 is not set
# CONFIG_SND_SOC_ES8328_I2C is not set
# CONFIG_SND_SOC_ES8328_SPI is not set
# CONFIG_SND_SOC_GTM601 is not set
# CONFIG_SND_SOC_INNO_RK3036 is not set
# CONFIG_SND_SOC_MAX98088 is not setCONFIG_SND_SOC_MAX98090=mCONFIG_SND_SOC_MAX98095=m
# CONFIG_SND_SOC_MAX98357A is not set
# CONFIG_SND_SOC_MAX98504 is not set
# CONFIG_SND_SOC_MAX9867 is not set
# CONFIG_SND_SOC_MAX98927 is not set
# CONFIG_SND_SOC_MAX98373_I2C is not set
# CONFIG_SND_SOC_MAX98390 is not set
# CONFIG_SND_SOC_MAX9860 is not set
# CONFIG_SND_SOC_MSM8916_WCD_ANALOG is not set
# CONFIG_SND_SOC_MSM8916_WCD_DIGITAL is not set
# CONFIG_SND_SOC_PCM1681 is not set
# CONFIG_SND_SOC_PCM1789_I2C is not set
# CONFIG_SND_SOC_PCM179X_I2C is not set
# CONFIG_SND_SOC_PCM179X_SPI is not set
# CONFIG_SND_SOC_PCM186X_I2C is not set
# CONFIG_SND_SOC_PCM186X_SPI is not set
# CONFIG_SND_SOC_PCM3060_I2C is not set
# CONFIG_SND_SOC_PCM3060_SPI is not set
# CONFIG_SND_SOC_PCM3168A_I2C is not set
# CONFIG_SND_SOC_PCM3168A_SPI is not set
# CONFIG_SND_SOC_PCM5102A is not set
# CONFIG_SND_SOC_PCM512x_I2C is not set
# CONFIG_SND_SOC_PCM512x_SPI is not set
# CONFIG_SND_SOC_RK3328 is not setCONFIG_SND_SOC_RL6231=m
# CONFIG_SND_SOC_RT5616 is not setCONFIG_SND_SOC_RT5631=mCONFIG_SND_SOC_RT5640=mCONFIG_SND_SOC_RT5645=mCONFIG_SND_SOC_SGTL5000=m
# CONFIG_SND_SOC_SIMPLE_AMPLIFIER is not set
# CONFIG_SND_SOC_SIMPLE_MUX is not set
# CONFIG_SND_SOC_SIRF_AUDIO_CODEC is not setCONFIG_SND_SOC_SPDIF=m
# CONFIG_SND_SOC_SSM2305 is not set
# CONFIG_SND_SOC_SSM2602_SPI is not set
# CONFIG_SND_SOC_SSM2602_I2C is not set
# CONFIG_SND_SOC_SSM4567 is not set
# CONFIG_SND_SOC_STA32X is not set
# CONFIG_SND_SOC_STA350 is not setCONFIG_SND_SOC_STI_SAS=m
# CONFIG_SND_SOC_TAS2552 is not set
# CONFIG_SND_SOC_TAS2562 is not set
# CONFIG_SND_SOC_TAS2764 is not set
# CONFIG_SND_SOC_TAS2770 is not set
# CONFIG_SND_SOC_TAS5086 is not set
# CONFIG_SND_SOC_TAS571X is not set
# CONFIG_SND_SOC_TAS5720 is not set
# CONFIG_SND_SOC_TAS6424 is not set
# CONFIG_SND_SOC_TDA7419 is not set
# CONFIG_SND_SOC_TFA9879 is not setCONFIG_SND_SOC_TLV320AIC23=mCONFIG_SND_SOC_TLV320AIC23_I2C=m
# CONFIG_SND_SOC_TLV320AIC23_SPI is not set
# CONFIG_SND_SOC_TLV320AIC31XX is not set
# CONFIG_SND_SOC_TLV320AIC32X4_I2C is not set
# CONFIG_SND_SOC_TLV320AIC32X4_SPI is not set
# CONFIG_SND_SOC_TLV320AIC3X is not set
# CONFIG_SND_SOC_TLV320ADCX140 is not setCONFIG_SND_SOC_TS3A227E=m
# CONFIG_SND_SOC_TSCS42XX is not set
# CONFIG_SND_SOC_TSCS454 is not set
# CONFIG_SND_SOC_UDA1334 is not set
# CONFIG_SND_SOC_WM8510 is not set
# CONFIG_SND_SOC_WM8523 is not set
# CONFIG_SND_SOC_WM8524 is not set
# CONFIG_SND_SOC_WM8580 is not set
# CONFIG_SND_SOC_WM8711 is not set
# CONFIG_SND_SOC_WM8728 is not set
# CONFIG_SND_SOC_WM8731 is not set
# CONFIG_SND_SOC_WM8737 is not set
# CONFIG_SND_SOC_WM8741 is not set
# CONFIG_SND_SOC_WM8750 is not setCONFIG_SND_SOC_WM8753=m
# CONFIG_SND_SOC_WM8770 is not set
# CONFIG_SND_SOC_WM8776 is not set
# CONFIG_SND_SOC_WM8782 is not set
# CONFIG_SND_SOC_WM8804_I2C is not set
# CONFIG_SND_SOC_WM8804_SPI is not setCONFIG_SND_SOC_WM8903=mCONFIG_SND_SOC_WM8904=m
# CONFIG_SND_SOC_WM8960 is not set
# CONFIG_SND_SOC_WM8962 is not set
# CONFIG_SND_SOC_WM8974 is not setCONFIG_SND_SOC_WM8978=m
# CONFIG_SND_SOC_WM8985 is not setCONFIG_SND_SOC_WM8994=mCONFIG_SND_SOC_WM9712=m
# CONFIG_SND_SOC_ZL38060 is not set
# CONFIG_SND_SOC_ZX_AUD96P22 is not set
# CONFIG_SND_SOC_MAX9759 is not set
# CONFIG_SND_SOC_MT6351 is not set
# CONFIG_SND_SOC_MT6358 is not set
# CONFIG_SND_SOC_MT6660 is not set
# CONFIG_SND_SOC_NAU8315 is not set
# CONFIG_SND_SOC_NAU8540 is not set
# CONFIG_SND_SOC_NAU8810 is not set
# CONFIG_SND_SOC_NAU8822 is not set
# CONFIG_SND_SOC_NAU8824 is not set
# CONFIG_SND_SOC_TPA6130A2 is not set
# CONFIG_SND_SOC_LPASS_WSA_MACRO is not set
# CONFIG_SND_SOC_LPASS_VA_MACRO is not set
# end of CODEC drivers
CONFIG_SND_SIMPLE_CARD_UTILS=mCONFIG_SND_SIMPLE_CARD=mCONFIG_SND_AUDIO_GRAPH_CARD=mCONFIG_AC97_BUS=m
#
# HID support
#CONFIG_HID=y
# CONFIG_HID_BATTERY_STRENGTH is not set
# CONFIG_HIDRAW is not set
# CONFIG_UHID is not setCONFIG_HID_GENERIC=y
#
# Special HID drivers
#
# CONFIG_HID_A4TECH is not set
# CONFIG_HID_ACCUTOUCH is not set
# CONFIG_HID_ACRUX is not set
# CONFIG_HID_APPLE is not set
# CONFIG_HID_APPLEIR is not set
# CONFIG_HID_ASUS is not set
# CONFIG_HID_AUREAL is not set
# CONFIG_HID_BELKIN is not set
# CONFIG_HID_BETOP_FF is not set
# CONFIG_HID_BIGBEN_FF is not set
# CONFIG_HID_CHERRY is not set
# CONFIG_HID_CHICONY is not set
# CONFIG_HID_CORSAIR is not set
# CONFIG_HID_COUGAR is not set
# CONFIG_HID_MACALLY is not set
# CONFIG_HID_PRODIKEYS is not set
# CONFIG_HID_CMEDIA is not set
# CONFIG_HID_CREATIVE_SB0540 is not set
# CONFIG_HID_CYPRESS is not set
# CONFIG_HID_DRAGONRISE is not set
# CONFIG_HID_EMS_FF is not set
# CONFIG_HID_ELAN is not set
# CONFIG_HID_ELECOM is not set
# CONFIG_HID_ELO is not set
# CONFIG_HID_EZKEY is not set
# CONFIG_HID_GEMBIRD is not set
# CONFIG_HID_GFRM is not set
# CONFIG_HID_GLORIOUS is not set
# CONFIG_HID_HOLTEK is not set
# CONFIG_HID_GOOGLE_HAMMER is not set
# CONFIG_HID_VIVALDI is not set
# CONFIG_HID_GT683R is not set
# CONFIG_HID_KEYTOUCH is not set
# CONFIG_HID_KYE is not set
# CONFIG_HID_UCLOGIC is not set
# CONFIG_HID_WALTOP is not set
# CONFIG_HID_VIEWSONIC is not set
# CONFIG_HID_GYRATION is not set
# CONFIG_HID_ICADE is not set
# CONFIG_HID_ITE is not set
# CONFIG_HID_JABRA is not set
# CONFIG_HID_TWINHAN is not set
# CONFIG_HID_KENSINGTON is not set
# CONFIG_HID_LCPOWER is not set
# CONFIG_HID_LED is not set
# CONFIG_HID_LENOVO is not set
# CONFIG_HID_LOGITECH is not set
# CONFIG_HID_MAGICMOUSE is not set
# CONFIG_HID_MALTRON is not set
# CONFIG_HID_MAYFLASH is not set
# CONFIG_HID_REDRAGON is not set
# CONFIG_HID_MICROSOFT is not set
# CONFIG_HID_MONTEREY is not set
# CONFIG_HID_MULTITOUCH is not set
# CONFIG_HID_NTI is not set
# CONFIG_HID_NTRIG is not set
# CONFIG_HID_ORTEK is not set
# CONFIG_HID_PANTHERLORD is not set
# CONFIG_HID_PENMOUNT is not set
# CONFIG_HID_PETALYNX is not set
# CONFIG_HID_PICOLCD is not set
# CONFIG_HID_PLANTRONICS is not set
# CONFIG_HID_PRIMAX is not set
# CONFIG_HID_RETRODE is not set
# CONFIG_HID_ROCCAT is not set
# CONFIG_HID_SAITEK is not set
# CONFIG_HID_SAMSUNG is not set
# CONFIG_HID_SONY is not set
# CONFIG_HID_SPEEDLINK is not set
# CONFIG_HID_STEAM is not set
# CONFIG_HID_STEELSERIES is not set
# CONFIG_HID_SUNPLUS is not set
# CONFIG_HID_RMI is not set
# CONFIG_HID_GREENASIA is not set
# CONFIG_HID_SMARTJOYPLUS is not set
# CONFIG_HID_TIVO is not set
# CONFIG_HID_TOPSEED is not set
# CONFIG_HID_THINGM is not set
# CONFIG_HID_THRUSTMASTER is not set
# CONFIG_HID_UDRAW_PS3 is not set
# CONFIG_HID_U2FZERO is not set
# CONFIG_HID_WACOM is not set
# CONFIG_HID_WIIMOTE is not set
# CONFIG_HID_XINMO is not set
# CONFIG_HID_ZEROPLUS is not set
# CONFIG_HID_ZYDACRON is not set
# CONFIG_HID_SENSOR_HUB is not set
# CONFIG_HID_ALPS is not set
# CONFIG_HID_MCP2221 is not set
# end of Special HID drivers
#
# USB HID support
#CONFIG_USB_HID=y
# CONFIG_HID_PID is not set
# CONFIG_USB_HIDDEV is not set
# end of USB HID support
#
# I2C HID support
#
# CONFIG_I2C_HID is not set
# end of I2C HID support # end of HID support
CONFIG_USB_OHCI_LITTLE_ENDIAN=yCONFIG_USB_SUPPORT=yCONFIG_USB_COMMON=y
# CONFIG_USB_LED_TRIG is not setCONFIG_USB_ULPI_BUS=yCONFIG_USB_CONN_GPIO=yCONFIG_USB_ARCH_HAS_HCD=yCONFIG_USB=yCONFIG_USB_PCI=y
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set
#
# Miscellaneous USB options
#CONFIG_USB_DEFAULT_PERSIST=y
# CONFIG_USB_FEW_INIT_RETRIES is not set
# CONFIG_USB_DYNAMIC_MINORS is not setCONFIG_USB_OTG=y
# CONFIG_USB_OTG_PRODUCTLIST is not set
# CONFIG_USB_OTG_DISABLE_EXTERNAL_HUB is not set
# CONFIG_USB_OTG_FSM is not set
# CONFIG_USB_LEDS_TRIGGER_USBPORT is not setCONFIG_USB_AUTOSUSPEND_DELAY=2
# CONFIG_USB_MON is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not setCONFIG_USB_XHCI_HCD=y
# CONFIG_USB_XHCI_DBGCAP is not setCONFIG_USB_XHCI_PCI=y
# CONFIG_USB_XHCI_PCI_RENESAS is not setCONFIG_USB_XHCI_PLATFORM=y
# CONFIG_USB_XHCI_HISTB is not set
# CONFIG_USB_XHCI_MTK is not setCONFIG_USB_XHCI_MVEBU=yCONFIG_USB_XHCI_RCAR=yCONFIG_USB_XHCI_TEGRA=m
# CONFIG_USB_BRCMSTB is not setCONFIG_USB_EHCI_HCD=yCONFIG_USB_EHCI_ROOT_HUB_TT=yCONFIG_USB_EHCI_TT_NEWSCHED=yCONFIG_USB_EHCI_PCI=y
# CONFIG_USB_EHCI_FSL is not setCONFIG_USB_EHCI_HCD_OMAP=mCONFIG_USB_EHCI_HCD_ORION=yCONFIG_USB_EHCI_HCD_SPEAR=yCONFIG_USB_EHCI_HCD_STI=yCONFIG_USB_EHCI_HCD_AT91=yCONFIG_USB_EHCI_TEGRA=yCONFIG_USB_EHCI_EXYNOS=mCONFIG_USB_EHCI_MV=mCONFIG_USB_EHCI_HCD_PLATFORM=y
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_FOTG210_HCD is not set
# CONFIG_USB_MAX3421_HCD is not setCONFIG_USB_OHCI_HCD=yCONFIG_USB_OHCI_HCD_SPEAR=yCONFIG_USB_OHCI_HCD_STI=yCONFIG_USB_OHCI_HCD_AT91=yCONFIG_USB_OHCI_HCD_OMAP3=yCONFIG_USB_OHCI_HCD_PCI=yCONFIG_USB_OHCI_EXYNOS=mCONFIG_USB_OHCI_HCD_PLATFORM=y
# CONFIG_USB_UHCI_HCD is not setCONFIG_USB_UHCI_SUPPORT_NON_PCI_HC=yCONFIG_USB_UHCI_PLATFORM=yCONFIG_USB_UHCI_ASPEED=y
# CONFIG_USB_SL811_HCD is not setCONFIG_USB_R8A66597_HCD=m
# CONFIG_USB_RENESAS_USBHS_HCD is not set
# CONFIG_USB_HCD_BCMA is not set
# CONFIG_USB_HCD_TEST_MODE is not setCONFIG_USB_RENESAS_USBHS=m
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may #
#
# also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=y # CONFIG_USB_STORAGE_DEBUG is not set # CONFIG_USB_STORAGE_REALTEK is not set # CONFIG_USB_STORAGE_DATAFAB is not set # CONFIG_USB_STORAGE_FREECOM is not set # CONFIG_USB_STORAGE_ISD200 is not set # CONFIG_USB_STORAGE_USBAT is not set # CONFIG_USB_STORAGE_SDDR09 is not set # CONFIG_USB_STORAGE_SDDR55 is not set # CONFIG_USB_STORAGE_JUMPSHOT is not set # CONFIG_USB_STORAGE_ALAUDA is not set # CONFIG_USB_STORAGE_ONETOUCH is not set # CONFIG_USB_STORAGE_KARMA is not set # CONFIG_USB_STORAGE_CYPRESS_ATACB is not set # CONFIG_USB_STORAGE_ENE_UB6250 is not set CONFIG_USB_UAS=m
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USBIP_CORE is not set
# CONFIG_USB_CDNS_SUPPORT is not set
# CONFIG_USB_MTU3 is not setCONFIG_USB_MUSB_HDRC=m
# CONFIG_USB_MUSB_HOST is not set
# CONFIG_USB_MUSB_GADGET is not setCONFIG_USB_MUSB_DUAL_ROLE=y
#
# Platform Glue Layer
#CONFIG_USB_MUSB_SUNXI=mCONFIG_USB_MUSB_TUSB6010=mCONFIG_USB_MUSB_OMAP2PLUS=mCONFIG_USB_MUSB_AM35X=mCONFIG_USB_MUSB_DSPS=mCONFIG_USB_MUSB_UX500=m
# CONFIG_USB_MUSB_MEDIATEK is not set
#
# MUSB DMA mode
#
# CONFIG_MUSB_PIO_ONLY is not setCONFIG_USB_UX500_DMA=yCONFIG_USB_INVENTRA_DMA=yCONFIG_USB_TI_CPPI41_DMA=yCONFIG_USB_TUSB_OMAP_DMA=yCONFIG_USB_DWC3=y
# CONFIG_USB_DWC3_ULPI is not set
# CONFIG_USB_DWC3_HOST is not set
# CONFIG_USB_DWC3_GADGET is not setCONFIG_USB_DWC3_DUAL_ROLE=y
#
# Platform Glue Driver Support
#CONFIG_USB_DWC3_OMAP=yCONFIG_USB_DWC3_EXYNOS=yCONFIG_USB_DWC3_HAPS=yCONFIG_USB_DWC3_KEYSTONE=yCONFIG_USB_DWC3_MESON_G12A=yCONFIG_USB_DWC3_OF_SIMPLE=yCONFIG_USB_DWC3_ST=yCONFIG_USB_DWC3_QCOM=yCONFIG_USB_DWC2=y
# CONFIG_USB_DWC2_HOST is not set
#
# Gadget/Dual-role mode requires USB Gadget support to be enabled #
# CONFIG_USB_DWC2_PERIPHERAL is not set CONFIG_USB_DWC2_DUAL_ROLE=y
# CONFIG_USB_DWC2_PCI is not set
# CONFIG_USB_DWC2_DEBUG is not set
# CONFIG_USB_DWC2_TRACK_MISSED_SOFS is not set CONFIG_USB_CHIPIDEA=yCONFIG_USB_CHIPIDEA_UDC=yCONFIG_USB_CHIPIDEA_HOST=yCONFIG_USB_CHIPIDEA_PCI=mCONFIG_USB_CHIPIDEA_MSM=yCONFIG_USB_CHIPIDEA_IMX=yCONFIG_USB_CHIPIDEA_GENERIC=y CONFIG_USB_CHIPIDEA_TEGRA=yCONFIG_USB_ISP1760=yCONFIG_USB_ISP1760_HCD=yCONFIG_USB_ISP1761_UDC=y
# CONFIG_USB_ISP1760_HOST_ROLE is not set
# CONFIG_USB_ISP1760_GADGET_ROLE is not set CONFIG_USB_ISP1760_DUAL_ROLE=y
#
# USB port drivers
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_APPLE_MFI_FASTCHARGE is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_EHSET_TEST_FIXTURE is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_YUREX is not set
# CONFIG_USB_EZUSB_FX2 is not set
# CONFIG_USB_HUB_USB251XB is not setCONFIG_USB_HSIC_USB3503=y
# CONFIG_USB_HSIC_USB4604 is not set
# CONFIG_USB_LINK_LAYER_TEST is not set
# CONFIG_USB_CHAOSKEY is not setCONFIG_BRCM_USB_PINMAP=y
#
# USB Physical Layer drivers
#CONFIG_USB_PHY=yCONFIG_AB8500_USB=yCONFIG_KEYSTONE_USB_PHY=mCONFIG_NOP_USB_XCEIV=mCONFIG_AM335X_CONTROL_USB=mCONFIG_AM335X_PHY_USB=mCONFIG_TWL6030_USB=mCONFIG_USB_GPIO_VBUS=yCONFIG_USB_ISP1301=yCONFIG_USB_MXS_PHY=yCONFIG_USB_TEGRA_PHY=yCONFIG_USB_ULPI=yCONFIG_USB_ULPI_VIEWPORT=y
# end of USB Physical Layer drivers
CONFIG_USB_GADGET=y
# CONFIG_USB_GADGET_DEBUG is not set
# CONFIG_USB_GADGET_DEBUG_FILES is not set
# CONFIG_USB_GADGET_DEBUG_FS is not setCONFIG_USB_GADGET_VBUS_DRAW=2CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2
# CONFIG_U_SERIAL_CONSOLE is not set
#
# USB Peripheral Controller
#
# CONFIG_USB_AT91 is not set
# CONFIG_USB_ATMEL_USBA is not setCONFIG_USB_FSL_USB2=y
# CONFIG_USB_FUSB300 is not set
# CONFIG_USB_FOTG210_UDC is not set
# CONFIG_USB_GR_UDC is not set
# CONFIG_USB_R8A66597 is not setCONFIG_USB_RENESAS_USBHS_UDC=m
# CONFIG_USB_RENESAS_USB3 is not set
# CONFIG_USB_PXA27X is not set
# CONFIG_USB_MV_UDC is not set
# CONFIG_USB_MV_U3D is not setCONFIG_USB_SNP_CORE=yCONFIG_USB_SNP_UDC_PLAT=y
# CONFIG_USB_M66592 is not setCONFIG_USB_BDC_UDC=y
#
# Platform Support
#CONFIG_USB_BDC_PCI=y
# CONFIG_USB_AMD5536UDC is not set
# CONFIG_USB_NET2272 is not set
# CONFIG_USB_NET2280 is not set
# CONFIG_USB_GOKU is not set
# CONFIG_USB_EG20T is not set
# CONFIG_USB_GADGET_XILINX is not set
# CONFIG_USB_MAX3420_UDC is not set
# CONFIG_USB_TEGRA_XUDC is not setCONFIG_USB_ASPEED_VHUB=m
# CONFIG_USB_DUMMY_HCD is not set
# end of USB Peripheral Controller
CONFIG_USB_LIBCOMPOSITE=mCONFIG_USB_F_ACM=mCONFIG_USB_F_SS_LB=mCONFIG_USB_U_SERIAL=mCONFIG_USB_U_ETHER=mCONFIG_USB_U_AUDIO=mCONFIG_USB_F_SERIAL=mCONFIG_USB_F_OBEX=mCONFIG_USB_F_NCM=mCONFIG_USB_F_ECM=mCONFIG_USB_F_EEM=mCONFIG_USB_F_SUBSET=mCONFIG_USB_F_RNDIS=mCONFIG_USB_F_MASS_STORAGE=mCONFIG_USB_F_FS=mCONFIG_USB_F_UAC1=mCONFIG_USB_F_UAC1_LEGACY=mCONFIG_USB_F_UAC2=mCONFIG_USB_F_UVC=mCONFIG_USB_F_MIDI=mCONFIG_USB_F_HID=mCONFIG_USB_F_PRINTER=mCONFIG_USB_CONFIGFS=mCONFIG_USB_CONFIGFS_SERIAL=yCONFIG_USB_CONFIGFS_ACM=yCONFIG_USB_CONFIGFS_OBEX=yCONFIG_USB_CONFIGFS_NCM=yCONFIG_USB_CONFIGFS_ECM=yCONFIG_USB_CONFIGFS_ECM_SUBSET=yCONFIG_USB_CONFIGFS_RNDIS=yCONFIG_USB_CONFIGFS_EEM=yCONFIG_USB_CONFIGFS_MASS_STORAGE=yCONFIG_USB_CONFIGFS_F_LB_SS=yCONFIG_USB_CONFIGFS_F_FS=yCONFIG_USB_CONFIGFS_F_UAC1=yCONFIG_USB_CONFIGFS_F_UAC1_LEGACY=yCONFIG_USB_CONFIGFS_F_UAC2=yCONFIG_USB_CONFIGFS_F_MIDI=yCONFIG_USB_CONFIGFS_F_HID=yCONFIG_USB_CONFIGFS_F_UVC=yCONFIG_USB_CONFIGFS_F_PRINTER=y
2,791 lines not shown · raw message
Part of this message is not shown here. View the raw message.
Quoted 8 lines · Marco Elver
Review
Quoted 5 lines · Arnd Bergmann
(quoted diff) +1
-1-static void __init futex_detect_cmpxchg(void) +static noinline void futex_detect_cmpxchg(void) { #ifndef CONFIG_HAVE_FUTEX_CMPXCHG u32 curval;What ever happened to this patch?
It obviously fell through the cracks.
Quoted 3 lines
I'm seeing this again with the attached config + next-20201211 (for testing https://bugs.llvm.org/show_bug.cgi?id=48492). Had to apply this patch to build the kernel.
What really bothers me is to remove the __init from a function which is clearly only used during init. And looking deeper it's simply a hack.
This function is only needed when an architecture has to runtime discover whether the CPU supports it or not. ARM has unconditional support for this, so the obvious thing to do is the below.
Thanks,
tglx
--- arch/arm/Kconfig | 1 + 1 file changed, 1 insertion(+)
arch/arm/Kconfig +1 -0
@@ -86,6 +86,7 @@ config ARM select HAVE_FTRACE_MCOUNT_RECORD if !XIP_KERNEL select HAVE_FUNCTION_GRAPH_TRACER if !THUMB2_KERNEL && !CC_IS_CLANG select HAVE_FUNCTION_TRACER if !XIP_KERNEL + select HAVE_FUTEX_CMPXCHG if FUTEX select HAVE_GCC_PLUGINS select HAVE_HW_BREAKPOINT if PERF_EVENTS && (CPU_V6 || CPU_V6K || CPU_V7) select HAVE_IDE if PCI || ISA || PCMCIA
Marco Elver
Tested-byQuoted 35 lines · Thomas Gleixner
Quoted 8 lines · Marco Elver
Review
Quoted 5 lines · Arnd Bergmann
(quoted diff) +1
-1-static void __init futex_detect_cmpxchg(void) +static noinline void futex_detect_cmpxchg(void) { #ifndef CONFIG_HAVE_FUTEX_CMPXCHG u32 curval;What ever happened to this patch?
It obviously fell through the cracks.
Quoted 3 lines
I'm seeing this again with the attached config + next-20201211 (for testing https://bugs.llvm.org/show_bug.cgi?id=48492). Had to apply this patch to build the kernel.
What really bothers me is to remove the
__initfrom a function which is clearly only used during init. And looking deeper it's simply a hack.This function is only needed when an architecture has to runtime discover whether the CPU supports it or not. ARM has unconditional support for this, so the obvious thing to do is the below.
Thanks,
tglx
--- arch/arm/Kconfig | 1 + 1 file changed, 1 insertion(+)
arch/arm/Kconfig config ARM · line 92
Quoted 7 lines
arch/arm/Kconfig +1
-0@@ -86,6 +86,7 @@ config ARM select HAVE_FTRACE_MCOUNT_RECORD if !XIP_KERNEL select HAVE_FUNCTION_GRAPH_TRACER if !THUMB2_KERNEL && !CC_IS_CLANG select HAVE_FUNCTION_TRACER if !XIP_KERNEL + select HAVE_FUTEX_CMPXCHG if FUTEX select HAVE_GCC_PLUGINS select HAVE_HW_BREAKPOINT if PERF_EVENTS && (CPU_V6 || CPU_V6K || CPU_V7) select HAVE_IDE if PCI || ISA || PCMCIA
This works, too. Thank you!
Thanks,
-- Marco
Quoted 17 lines · Thomas Gleixner
Quoted 8 lines · Marco Elver
Review
Quoted 5 lines · Arnd Bergmann
(quoted diff) +1
-1-static void __init futex_detect_cmpxchg(void) +static noinline void futex_detect_cmpxchg(void) { #ifndef CONFIG_HAVE_FUTEX_CMPXCHG u32 curval;What ever happened to this patch?
It obviously fell through the cracks.
Quoted 3 lines
I'm seeing this again with the attached config + next-20201211 (for testing https://bugs.llvm.org/show_bug.cgi?idH492). Had to apply this patch to build the kernel.
Quoted 7 lines
What really bothers me is to remove the
__initfrom a function which is clearly only used during init. And looking deeper it's simply a hack.This function is only needed when an architecture has to runtime discover whether the CPU supports it or not. ARM has unconditional support for this, so the obvious thing to do is the below.
Ah perfect, that is clearly the right solution here.
arch/arm/Kconfig config ARM · line 92
Quoted 10 lines
arch/arm/Kconfig +1
-0@@ -86,6 +86,7 @@ config ARM select HAVE_FTRACE_MCOUNT_RECORD if !XIP_KERNEL select HAVE_FUNCTION_GRAPH_TRACER if !THUMB2_KERNEL && !CC_IS_CLANG select HAVE_FUNCTION_TRACER if !XIP_KERNEL + select HAVE_FUTEX_CMPXCHG if FUTEX select HAVE_GCC_PLUGINS select HAVE_HW_BREAKPOINT if PERF_EVENTS && (CPU_V6 || CPU_V6K || CPU_V7) select HAVE_IDE if PCI || ISA || PCMCIA
I had a look at what other architectures always implement futex_atomic_cmpxchg_inatomic() or can use the asm-generic non-SMP version, and I found that it's pretty much all of them, the odd ones being just sparc32 and csky, which use asm-generic/futex.h but do have an SMP option, as well as xtensa
I would guess that for csky, this is a mistake, as the architecture is fairly new and should be able to implement it. Not sure about sparc32.
Arnd
Guo Ren
maintainerHi Arnd,
Quoted 46 lines · Arnd Bergmann
Quoted 17 lines · Thomas Gleixner
Quoted 8 lines · Marco Elver
Review
Quoted 5 lines · Arnd Bergmann
(quoted diff) +1
-1-static void __init futex_detect_cmpxchg(void) +static noinline void futex_detect_cmpxchg(void) { #ifndef CONFIG_HAVE_FUTEX_CMPXCHG u32 curval;What ever happened to this patch?
It obviously fell through the cracks.
Quoted 3 lines
I'm seeing this again with the attached config + next-20201211 (for testing https://bugs.llvm.org/show_bug.cgi?idH492). Had to apply this patch to build the kernel.
Quoted 7 lines
What really bothers me is to remove the
__initfrom a function which is clearly only used during init. And looking deeper it's simply a hack.This function is only needed when an architecture has to runtime discover whether the CPU supports it or not. ARM has unconditional support for this, so the obvious thing to do is the below.
Ah perfect, that is clearly the right solution here.
arch/arm/Kconfig config ARM · line 92
Quoted 10 lines
arch/arm/Kconfig +1
-0@@ -86,6 +86,7 @@ config ARM select HAVE_FTRACE_MCOUNT_RECORD if !XIP_KERNEL select HAVE_FUNCTION_GRAPH_TRACER if !THUMB2_KERNEL && !CC_IS_CLANG select HAVE_FUNCTION_TRACER if !XIP_KERNEL + select HAVE_FUTEX_CMPXCHG if FUTEX select HAVE_GCC_PLUGINS select HAVE_HW_BREAKPOINT if PERF_EVENTS && (CPU_V6 || CPU_V6K || CPU_V7) select HAVE_IDE if PCI || ISA || PCMCIAI had a look at what other architectures always implement
futex_atomic_cmpxchg_inatomic()or can use the asm-generic non-SMP version, and I found that it's pretty much all of them, the odd ones being just sparc32 and csky, which useasm-generic/futex.hbut do have an SMP option, as well as xtensa
Quoted 2 lines
I would guess that for csky, this is a mistake, as the architecture is fairly new and should be able to implement it. Not sure about sparc32.
The c610, c807, c810 don't support SMP, so futex_cmpxchg_enabled = 1 with asm-generic's implementation.
For c860, there is no HAVE_FUTEX_CMPXCHG and cmpxchg_inatomic/inuser implementation, so futex_cmpxchg_enabled = 0.
Thx for point it out, we'll implement cmpxchg_inatomic/inuser for C860 and still use asm-generic for non-smp CPUs:
arch/csky/Kconfig +1 -0
@@ -49,6 +49,7 @@ config CSKY select HAVE_FUNCTION_TRACER select HAVE_FUNCTION_GRAPH_TRACER select HAVE_FUNCTION_ERROR_INJECTION + select HAVE_FUTEX_CMPXCHG if FUTEX && SMP select HAVE_FTRACE_MCOUNT_RECORD select HAVE_KERNEL_GZIP select HAVE_KERNEL_LZO
arch/csky/include/asm/futex.h new file +42 -0
42 lines not on this page · raw message
Signature · 4 lines
Best Regards Guo Ren ML: https://lore.kernel.org/linux-csky/
Quoted 10 lines · Guo Ren
Quoted 8 lines · Arnd Bergmann
I had a look at what other architectures always implement
futex_atomic_cmpxchg_inatomic()or can use the asm-generic non-SMP version, and I found that it's pretty much all of them, the odd ones being just sparc32 and csky, which useasm-generic/futex.hbut do have an SMP option, as well as xtensaI would guess that for csky, this is a mistake, as the architecture is fairly new and should be able to implement it. Not sure about sparc32.
Quoted 7 lines
The c610, c807, c810 don't support SMP, so
futex_cmpxchg_enabled= 1 with asm-generic's implementation.
For c860, there is noHAVE_FUTEX_CMPXCHGand cmpxchg_inatomic/inuser implementation, sofutex_cmpxchg_enabled= 0.Thx for point it out, we'll implement cmpxchg_inatomic/inuser for C860 and still use asm-generic for non-smp CPUs.
Sounds good to me.
With that, I would suggest we actually remove the -ENOSYS fallback for arch_futex_atomic_op_inuser() and futex_atomic_cmpxchg_inatomic() in asm-generic/futex.h as well as the HAVE_FUTEX_CMPXCHG Kconfig symbol, plus these additional fixups:
- for xtensa and mips configurations without ll/sc, fall back to the asm-generic version. These are all uniprocessor, while the corresponding SMP machines have a working arch_futex_atomic_op_inuser().
- Disable SMP support for sun4m/sun4d. From the historic git tree, it's unclear how well this ever worked, and very few machines of this class ever existed
- Mark SMP for LEON as temporarily broken. As I see in the LEON patch set, they have changes to enable compare-and-swap-atomic instructions unconditionally, as all SMP Leons have those and seem to require this support already for other things.
Arnd
Hi Arnd,
Quoted 26 lines · Arnd Bergmann
Quoted 10 lines · Guo Ren
Quoted 8 lines · Arnd Bergmann
I had a look at what other architectures always implement
futex_atomic_cmpxchg_inatomic()or can use the asm-generic non-SMP version, and I found that it's pretty much all of them, the odd ones being just sparc32 and csky, which useasm-generic/futex.hbut do have an SMP option, as well as xtensaI would guess that for csky, this is a mistake, as the architecture is fairly new and should be able to implement it. Not sure about sparc32.
Quoted 7 lines
The c610, c807, c810 don't support SMP, so
futex_cmpxchg_enabled= 1 with asm-generic's implementation.
For c860, there is noHAVE_FUTEX_CMPXCHGand cmpxchg_inatomic/inuser implementation, sofutex_cmpxchg_enabled= 0.Thx for point it out, we'll implement cmpxchg_inatomic/inuser for C860 and still use asm-generic for non-smp CPUs.
Sounds good to me.
With that, I would suggest we actually remove the
-ENOSYSfallback forarch_futex_atomic_op_inuser()andfutex_atomic_cmpxchg_inatomic()inasm-generic/futex.has well as theHAVE_FUTEX_CMPXCHGKconfigsymbol, plus these additional fixups:
Quoted 8 lines
- for xtensa and mips configurations without ll/sc, fall back to the asm-generic version. These are all uniprocessor, while the corresponding SMP machines have a working
arch_futex_atomic_op_inuser().- Disable SMP support for sun4m/sun4d. From the historic git tree, it's unclear how well this ever worked, and very few machines of this class ever existed
Yeah, I have collection of sparc32 machines that I played around with once. Including one sun4d that I brought from a friendly Linux fellow in the UK. But somehow I lost interest as this is all very nice machines but not useful for anything real work.
I think we would be better served dropping support for sun4m and sun4d from the kernel.
Last I suggested deleting sun4m/sun4d the argument to keep sun4m was that QEMU supports sun4m - which is a good argument for sun4m. I dunno what would be needed to migrate QEMU to LEON, see below.
Quoted 5 lines
- Mark SMP for LEON as temporarily broken. As I see in the LEON patch set, they have changes to enable compare-and-swap-atomic instructions unconditionally, as all SMP Leons have those and seem to require this support already for other things.
LEON on the other hand could have some nice future. They are right now stuck on an older kernel and someone that was motivated should be able to get LEON4 running on latest upstream.
We had it working in the past - but is was around the time I lost my sparc interest and no-one jumped in to move it much more forward.
So in other words - no complains for the plan you outline.
Sam
Quoted 5 lines · Sam Ravnborg
Quoted 4 lines · Arnd Bergmann
- Disable SMP support for sun4m/sun4d. From the historic git tree, it's unclear how well this ever worked, and very few machines of this class ever existed
Quoted 7 lines
Yeah, I have collection of sparc32 machines that I played around with once. Including one sun4d that I brought from a friendly Linux fellow in the UK. But somehow I lost interest as this is all very nice machines but not useful for anything real work.
I think we would be better served dropping support for sun4m and sun4d from the kernel.
This seems appropriate as well to me.
Quoted 3 lines
Last I suggested deleting sun4m/sun4d the argument to keep sun4m was that QEMU supports sun4m - which is a good argument for sun4m. I dunno what would be needed to migrate QEMU to LEON, see below.
"qemu-system-sparc -M help" shows a "leon3_generic" platform, apparently added in 2013. Do you think that would be sufficient?
Quoted 9 lines
Quoted 4 lines
- Mark SMP for LEON as temporarily broken. As I see in the LEON patch set, they have changes to enable compare-and-swap-atomic instructions unconditionally, as all SMP Leons have those and seem to require this support already for other things.
LEON on the other hand could have some nice future. They are right now stuck on an older kernel and someone that was motivated should be able to get LEON4 running on latest upstream.
We had it working in the past - but is was around the time I lost my sparc interest and no-one jumped in to move it much more forward.
My best guess from the public information I could find on LEON is that it keeps shifting away from Linux on LEON to other OSs, and to and to Linux on NOEL-V.
So even though the CPU itself will likely have a long life ahead of it with LEON5 only a year old, it's unclear how many more updates we'll see to the kernel from the current 4.9 based release.
Quoted 1 line
So in other words - no complains for the plan you outline.
Thanks. I'd probably queue up a patch in my asm-generic tree for v5.12 to disable SMP on all SPARC32, add the helpers for C-Sky once Guo Ren has tested a patch, and clean up the futex code based on this. I guess we want the one-line fix for Arm that Thomas suggested for v5.10 and backports anyway, The sun4m/sun4d removal should clearly be discussed separately and go through the sparc tree, to see if anyone has objections, or if we want to remove other obsolete platforms (sun3?) along with it.
Arnd
Quoted 14 lines · Arnd Bergmann
Quoted 5 lines · Sam Ravnborg
Quoted 4 lines · Arnd Bergmann
- Disable SMP support for sun4m/sun4d. From the historic git tree, it's unclear how well this ever worked, and very few machines of this class ever existed
Quoted 7 lines
Yeah, I have collection of sparc32 machines that I played around with once. Including one sun4d that I brought from a friendly Linux fellow in the UK. But somehow I lost interest as this is all very nice machines but not useful for anything real work.
I think we would be better served dropping support for sun4m and sun4d from the kernel.
Quoted 8 lines
This seems appropriate as well to me.
Quoted 3 lines
Last I suggested deleting sun4m/sun4d the argument to keep sun4m was that QEMU supports sun4m - which is a good argument for sun4m. I dunno what would be needed to migrate QEMU to LEON, see below.
"qemu-system-sparc -M help" shows a "
leon3_generic" platform, apparently added in 2013. Do you think that would be sufficient?
We have only use QEMU for LEON3 on limited and simpler system setups. For example the Zephyr SPARC arch + LEON3 BSP port we recently submitted to the Linux Foundation Zephyr project run their test-suite successfully on QEMU+LEON3. We will have to look into the QEMU for LEON and Linux situation.
We mainly use TSIM that is our own high fidelity simulator.
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
- Mark SMP for LEON as temporarily broken. As I see in the LEON patch set, they have changes to enable compare-and-swap-atomic instructions unconditionally, as all SMP Leons have those and seem to require this support already for other things.
Regarding unconditional compare-and-swap-atomic instructions (CASA) for LEON. I tried to get those into mainline under the LEON configuration option but did not get OK for that at that time, with the feedback to do it dynamically instead. I haven't come around to try to get an updated patch doing probing instead into mainline yet. If the thought now is to drop support for SMP for sparc32, maybe we can have the CASA unconditionally on SMP configured kernels instead. Still we'd like to have CASA usage even for non-SMP kernels for LEON systems that supports it.
Quoted 5 lines
Quoted 5 lines
LEON on the other hand could have some nice future. They are right now stuck on an older kernel and someone that was motivated should be able to get LEON4 running on latest upstream.
We had it working in the past - but is was around the time I lost my sparc interest and no-one jumped in to move it much more forward.
I would not say that we are stuck on an old kernel. It is rather that for our official releases we stay on long term support kernels. We still aim for kernels based on master to work on LEON. Right now we do have a bit of backlog of things to get into upstream.
Quoted 3 lines
My best guess from the public information I could find on LEON is that it keeps shifting away from Linux on LEON to other OSs, and to and to Linux on NOEL-V.
On the contrary. Our LEON users shows an increased interest in running Linux, now that LEON-based systems gains in number of processors, processor performance and memory. We are adding NOEL as a new processor line. With NOEL we have a 64-bit architecture. We are not shifting from LEON to NOEL. LEON is not going away.
Quoted 4 lines
So even though the CPU itself will likely have a long life ahead of it with LEON5 only a year old, it's unclear how many more updates we'll see to the kernel from the current 4.9 based release.
Our latest release was indeed based on 4.9, but we have no plans to stay there forever. We just tend to select long term support kernels for our official releases. The next step will be to go to 5.4 if not 5.10.
We recently released a new Linux 4.9 toolchain where we stepped up to GLIBC 2.31 and GCC 10.2. So we do not consider us stuck at old versions of any of the involved software.
In addition, non-LTS users are running other mainline kernel versions as well.
Best regards,
Andreas Larsson
Software Engineer
Cobham Gaisler
Quoted 24 lines · Andreas Larsson
Quoted 14 lines · Arnd Bergmann
Quoted 5 lines · Sam Ravnborg
Quoted 4 lines · Arnd Bergmann
- Disable SMP support for sun4m/sun4d. From the historic git tree, it's unclear how well this ever worked, and very few machines of this class ever existed
Quoted 7 lines
Yeah, I have collection of sparc32 machines that I played around with once. Including one sun4d that I brought from a friendly Linux fellow in the UK. But somehow I lost interest as this is all very nice machines but not useful for anything real work.
I think we would be better served dropping support for sun4m and sun4d from the kernel.
Quoted 8 lines
This seems appropriate as well to me.
Quoted 3 lines
Last I suggested deleting sun4m/sun4d the argument to keep sun4m was that QEMU supports sun4m - which is a good argument for sun4m. I dunno what would be needed to migrate QEMU to LEON, see below.
"qemu-system-sparc -M help" shows a "
leon3_generic" platform, apparently added in 2013. Do you think that would be sufficient?
Quoted 7 lines
We have only use QEMU for LEON3 on limited and simpler system setups. For example the Zephyr SPARC arch + LEON3 BSP port we recently submitted to the Linux Foundation Zephyr project run their test-suite successfully on QEMU+LEON3. We will have to look into the QEMU for LEON and Linux situation.
We mainly use TSIM that is our own high fidelity simulator.
I don't think there is a need to have many features supported in qemu, as long as you have enough RAM, block and network devices (which are trivial if you have PCI or USB).
Quoted 5 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
- Mark SMP for LEON as temporarily broken. As I see in the LEON patch set, they have changes to enable compare-and-swap-atomic instructions unconditionally, as all SMP Leons have those and seem to require this support already for other things.
Quoted 9 lines
Regarding unconditional compare-and-swap-atomic instructions (CASA) for LEON. I tried to get those into mainline under the LEON configuration option but did not get OK for that at that time, with the feedback to do it dynamically instead. I haven't come around to try to get an updated patch doing probing instead into mainline yet. If the thought now is to drop support for SMP for sparc32, maybe we can have the CASA unconditionally on SMP configured kernels instead. Still we'd like to have CASA usage even for non-SMP kernels for LEON systems that supports it.
It does make sense to require that a single kernel can work on all possible hardware. So if we remove sun4m/sun4d support, all that is left is LEON, and you likely wouldn't need to worry about other CPUs any more.
However, there is still the question whether a single kernel needs to work on LEON both with and without CASA. Do you still care about Linux users on LEON cores that do not support CASA, or is widespread enough that you just make it unconditional for both SMP and non-SMP?
Quoted 10 lines
Quoted 5 lines
Quoted 5 lines
LEON on the other hand could have some nice future. They are right now stuck on an older kernel and someone that was motivated should be able to get LEON4 running on latest upstream.
We had it working in the past - but is was around the time I lost my sparc interest and no-one jumped in to move it much more forward.I would not say that we are stuck on an old kernel. It is rather that for our official releases we stay on long term support kernels. We still aim for kernels based on master to work on LEON. Right now we do have a bit of backlog of things to get into upstream.
Ok, good to hear. There were a couple of old bugs that got found on mainline that made me wonder whether mainline sparc32 was used on any hardware at all these days.
I looked at your v4.9 patches and didn't see anything too scary there, in particular once sparc32 becomes leon-only, you no longer have to worry about making it work across different CPUs.
Quoted 9 lines
Quoted 3 lines
My best guess from the public information I could find on LEON is that it keeps shifting away from Linux on LEON to other OSs, and to and to Linux on NOEL-V.
On the contrary. Our LEON users shows an increased interest in running Linux, now that LEON-based systems gains in number of processors, processor performance and memory. We are adding NOEL as a new processor line. With NOEL we have a 64-bit architecture. We are not shifting from LEON to NOEL. LEON is not going away.
Ok.
Quoted 7 lines
Quoted 3 lines
So even though the CPU itself will likely have a long life ahead of it with LEON5 only a year old, it's unclear how many more updates we'll see to the kernel from the current 4.9 based release.
Our latest release was indeed based on 4.9, but we have no plans to stay there forever. We just tend to select long term support kernels for our official releases. The next step will be to go to 5.4 if not 5.10.
I hope that you can make it to 5.10 then, as this contains the work I did for 64-bit time_t, which is required if you have users that want to run systems after 2038.
Quoted 6 lines
We recently released a new Linux 4.9 toolchain where we stepped up to GLIBC 2.31 and GCC 10.2. So we do not consider us stuck at old versions of any of the involved software.
In addition, non-LTS users are running other mainline kernel versions as well.
FWIW, glibc-2.31 does not have support for 64-bit time_t yet, but I know there was interest in adding sparc support to the musl libc, which does support 64-bit time_t.
Arnd
Quoted 10 lines · Arnd Bergmann
It does make sense to require that a single kernel can work on all possible hardware. So if we remove sun4m/sun4d support, all that is left is LEON, and you likely wouldn't need to worry about other CPUs any more.
However, there is still the question whether a single kernel needs to work on LEON both with and without CASA. Do you still care about Linux users on LEON cores that do not support CASA, or is widespread enough that you just make it unconditional for both SMP and non-SMP?
We are fine with unconditional CASA for both SMP and non-SMP for LEON.
Quoted 3 lines
I hope that you can make it to 5.10 then, as this contains the work I did for 64-bit
time_t, which is required if you have users that want to run systems after 2038.
That is a good point! Thank you!
Quoted 3 lines
FWIW, glibc-2.31 does not have support for 64-bit
time_tyet, but I know there was interest in adding sparc support to the musl libc, which does support 64-bittime_t.
Yes, we will have to follow the developments regarding 64-bit time_t in GLIBC as well.
Signature · 1 line
Andreas
Hi Arnd,
Quoted 4 lines
Quoted 2 lines
I think we would be better served dropping support for sun4m and sun4d from the kernel.
This seems appropriate as well to me.
I did a quick hack:
20 files changed, 40 insertions(+), 3051 deletions(-)
All the leon stuff is kept and there is room for more cleaning up. The kernel can build a sparc32_defconfig with the Gaisler toochain. This was a one hour quick hack that I cannot commit - it needs to be split up to allow some resemble of review.
And it touched only arch/sparc/ - no sparc32 specific drivers were dropped.
If we decide to chase this and we can drop sun4m/sun4d then maintaining leon will be simpler as a nice side effect.
Sam
From: Sam Ravnborg
Quoted 6 lines
Sent: 15 December 2020 19:38
Hi Arnd,
Quoted 1 line · Arnd Bergmann
On Tue, Dec 15, 2020 at 7:09 AM Guo Ren <[email protected]> wrote:
...
Quoted 7 lines
Quoted 3 lines
- Disable SMP support for sun4m/sun4d. From the historic git tree, it's unclear how well this ever worked, and very few machines of this class ever existed
Yeah, I have collection of sparc32 machines that I played around with once. Including one sun4d that I brought from a friendly Linux fellow in the UK. But somehow I lost interest as this is all very nice machines but not useful for anything real work.
ICL made a few SMP sparc32 systems.
I think the first ones used the original Cypress cpu running at 25MHz. (I'm fairly sure these were SMP-capable, the later 40MHz definitely were.) These were full sized VMEbus beasts.
Somewhere I've got a 32MByte memory board - over a square foot of board. The memory is all 64k by 1 with all the pins on one edge and the chips vertical. Really looks as though it should glow red and be used for cooking toast. Even with 4 of those you're not going to run anything modern!
There were also some later mbus+sbus systems with dual sbus! Designed by Fujitsu.
None of these ever ran solaris.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
Quoted 26 lines · Arnd Bergmann
Quoted 10 lines · Guo Ren
Quoted 8 lines · Arnd Bergmann
I had a look at what other architectures always implement
futex_atomic_cmpxchg_inatomic()or can use the asm-generic non-SMP version, and I found that it's pretty much all of them, the odd ones being just sparc32 and csky, which useasm-generic/futex.hbut do have an SMP option, as well as xtensaI would guess that for csky, this is a mistake, as the architecture is fairly new and should be able to implement it. Not sure about sparc32.
Quoted 7 lines
The c610, c807, c810 don't support SMP, so
futex_cmpxchg_enabled= 1 with asm-generic's implementation.
For c860, there is noHAVE_FUTEX_CMPXCHGand cmpxchg_inatomic/inuser implementation, sofutex_cmpxchg_enabled= 0.Thx for point it out, we'll implement cmpxchg_inatomic/inuser for C860 and still use asm-generic for non-smp CPUs.
Sounds good to me.
With that, I would suggest we actually remove the
-ENOSYSfallback forarch_futex_atomic_op_inuser()andfutex_atomic_cmpxchg_inatomic()inasm-generic/futex.has well as theHAVE_FUTEX_CMPXCHGKconfigsymbol, plus these additional fixups:
Quoted 8 lines
- for xtensa and mips configurations without ll/sc, fall back to the asm-generic version. These are all uniprocessor, while the corresponding SMP machines have a working
arch_futex_atomic_op_inuser().- Disable SMP support for sun4m/sun4d. From the historic git tree, it's unclear how well this ever worked, and very few machines of this class ever existed
Hooray!! what about PA-RISC ? Can we burn that too?
Guo Ren
maintainerHi Arnd,
Quoted 17 lines · Arnd Bergmann
Quoted 15 lines · Guo Ren
Quoted 8 lines · Arnd Bergmann
I had a look at what other architectures always implement
futex_atomic_cmpxchg_inatomic()or can use the asm-generic non-SMP version, and I found that it's pretty much all of them, the odd ones being just sparc32 and csky, which useasm-generic/futex.hbut do have an SMP option, as well as xtensaI would guess that for csky, this is a mistake, as the architecture is fairly new and should be able to implement it. Not sure about sparc32.
The c610, c807, c810 don't support SMP, so
futex_cmpxchg_enabled= 1 with asm-generic's implementation.
For c860, there is noHAVE_FUTEX_CMPXCHGand cmpxchg_inatomic/inuser implementation, sofutex_cmpxchg_enabled= 0.
Quoted 4 lines
Quoted 2 lines
Thx for point it out, we'll implement cmpxchg_inatomic/inuser for C860 and still use asm-generic for non-smp CPUs.
Sounds good to me.
Done: https://lore.kernel.org/linux-csky/[email protected]/T/#u
Signature · 4 lines
Best Regards Guo Ren ML: https://lore.kernel.org/linux-csky/
Quoted 18 lines · Guo Ren
Quoted 17 lines · Arnd Bergmann
Quoted 15 lines · Guo Ren
Quoted 8 lines · Arnd Bergmann
I had a look at what other architectures always implement
futex_atomic_cmpxchg_inatomic()or can use the asm-generic non-SMP version, and I found that it's pretty much all of them, the odd ones being just sparc32 and csky, which useasm-generic/futex.hbut do have an SMP option, as well as xtensaI would guess that for csky, this is a mistake, as the architecture is fairly new and should be able to implement it. Not sure about sparc32.
The c610, c807, c810 don't support SMP, so
futex_cmpxchg_enabled= 1 with asm-generic's implementation.
For c860, there is noHAVE_FUTEX_CMPXCHGand cmpxchg_inatomic/inuser implementation, sofutex_cmpxchg_enabled= 0.
Quoted 5 lines
Quoted 4 lines
Quoted 2 lines
Thx for point it out, we'll implement cmpxchg_inatomic/inuser for C860 and still use asm-generic for non-smp CPUs.
Sounds good to me.
Done: https://lore.kernel.org/linux-csky/[email protected]/T/#u
Thanks!
Can you clarify if there are any dependencies on the other patches in that series?
I'd like to take the futex patch through the asm-generic tree along with the patches for the other architectures.
Arnd
Guo Ren
maintainerHi Arnd,
Quoted 23 lines · Arnd Bergmann
Quoted 21 lines · Guo Ren
Quoted 20 lines · Arnd Bergmann
Quoted 17 lines · Guo Ren
Quoted 8 lines · Arnd Bergmann
I had a look at what other architectures always implement
futex_atomic_cmpxchg_inatomic()or can use the asm-generic non-SMP version, and I found that it's pretty much all of them, the odd ones being just sparc32 and csky, which useasm-generic/futex.hbut do have an SMP option, as well as xtensaI would guess that for csky, this is a mistake, as the architecture is fairly new and should be able to implement it. Not sure about sparc32.
The c610, c807, c810 don't support SMP, so
futex_cmpxchg_enabled= 1 with asm-generic's implementation.
For c860, there is noHAVE_FUTEX_CMPXCHGand cmpxchg_inatomic/inuser implementation, sofutex_cmpxchg_enabled= 0.Thx for point it out, we'll implement cmpxchg_inatomic/inuser for C860 and still use asm-generic for non-smp CPUs.
Quoted 7 lines
Quoted 2 lines
Quoted 1 line
Sounds good to me.
Done: https://lore.kernel.org/linux-csky/[email protected]/T/#u
Thanks!
Can you clarify if there are any dependencies on the other patches in that series?
No dependency.
Quoted 3 lines
I'd like to take the futex patch through the asm-generic tree along with the patches for the other architectures.
You take the futex patch and I'll remove it from my tree.
Signature · 4 lines
Best Regards Guo Ren ML: https://lore.kernel.org/linux-csky/
Quoted 35 lines · Thomas Gleixner
Quoted 8 lines · Marco Elver
Review
Quoted 5 lines · Arnd Bergmann
(quoted diff) +1
-1-static void __init futex_detect_cmpxchg(void) +static noinline void futex_detect_cmpxchg(void) { #ifndef CONFIG_HAVE_FUTEX_CMPXCHG u32 curval;What ever happened to this patch?
It obviously fell through the cracks.
Quoted 3 lines
I'm seeing this again with the attached config + next-20201211 (for testing https://bugs.llvm.org/show_bug.cgi?id=48492). Had to apply this patch to build the kernel.
What really bothers me is to remove the
__initfrom a function which is clearly only used during init. And looking deeper it's simply a hack.This function is only needed when an architecture has to runtime discover whether the CPU supports it or not. ARM has unconditional support for this, so the obvious thing to do is the below.
Thanks,
tglx
--- arch/arm/Kconfig | 1 + 1 file changed, 1 insertion(+)
arch/arm/Kconfig config ARM · line 92
Quoted 7 lines
arch/arm/Kconfig +1
-0@@ -86,6 +86,7 @@ config ARM select HAVE_FTRACE_MCOUNT_RECORD if !XIP_KERNEL select HAVE_FUNCTION_GRAPH_TRACER if !THUMB2_KERNEL && !CC_IS_CLANG select HAVE_FUNCTION_TRACER if !XIP_KERNEL + select HAVE_FUTEX_CMPXCHG if FUTEX select HAVE_GCC_PLUGINS select HAVE_HW_BREAKPOINT if PERF_EVENTS && (CPU_V6 || CPU_V6K || CPU_V7) select HAVE_IDE if PCI || ISA || PCMCIA
Hi Thomas,
Did this ever get sent along as a formal patch? I just ran into another issue that seems to be similar to the one Arnd sent the initial patch in this thread for and it is resolved by this change.
Cheers,
Nathan
Quoted 15 lines · Nathan Chancellor
arch/arm/Kconfig config ARM · line 92
Quoted 10 lines · Thomas Gleixner
arch/arm/Kconfig +1
-0@@ -86,6 +86,7 @@ config ARM select HAVE_FTRACE_MCOUNT_RECORD if !XIP_KERNEL select HAVE_FUNCTION_GRAPH_TRACER if !THUMB2_KERNEL && !CC_IS_CLANG select HAVE_FUNCTION_TRACER if !XIP_KERNEL + select HAVE_FUTEX_CMPXCHG if FUTEX select HAVE_GCC_PLUGINS select HAVE_HW_BREAKPOINT if PERF_EVENTS && (CPU_V6 || CPU_V6K || CPU_V7) select HAVE_IDE if PCI || ISA || PCMCIADid this ever get sent along as a formal patch? I just ran into another issue that seems to be similar to the one Arnd sent the initial patch in this thread for and it is resolved by this change.
Nick sent this patch in September, and Russell applied it as commit 9d417cbe36ee ("ARM: 9122/1: select HAVE_FUTEX_CMPXCHG"). This addresses the problem for arm, but I think we should really just remove HAVE_FUTEX_CMPXCHG entirely and require it to be there for SMP.
I have a patch for that, but that needs a separate fix for sparc32, which I think nobody is interested in working on. I can post it anyway to get discussion moving again.
Arnd