lkml.org 
[lkml]   [2022]   [Jun]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: Kconfig rules (depends, imply)
Thank you for the clarification.

On Wed, Jun 1, 2022 at 1:55 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> Hi--
>
> On 5/31/22 05:14, Muni Sekhar wrote:
> > Hi all,
> >
> > menuconfig SOUNDWIRE
> > tristate "SoundWire support"
> > depends on ACPI || OF
> >
> > "depends on ACPI || OF" mean, SOUNDWIRE depends on both ACPI and OF modules?
> >
>
> "||" is logical OR, so SOUNDWIRE depends on either ACPI or OF (or both
> of them can be enabled).
>
>
> >
> > config SOUNDWIRE_QCOM
> > tristate "Qualcomm SoundWire Master driver"
> > imply SLIMBUS
> >
> > What does "imply SLIMBUS" mean?
>
> See Documentation/kbuild/kconfig-language.rst:
>
> - weak reverse dependencies: "imply" <symbol> ["if" <expr>]
>
> This is similar to "select" as it enforces a lower limit on another
> symbol except that the "implied" symbol's value may still be set to n
> from a direct dependency or with a visible prompt.
>
> So (in your example) SLIMBUS is desired but not required.
> That means that the code that is built for SOUNDWIRE_QCOM
> probably needs to use IS_REACHABLE(CONFIG_SLIMBUS) to
> see if that SLIMBUS code is available at build time.
>
> HTH.
> --
> ~Randy



--
Thanks,
Sekhar

\
 
 \ /
  Last update: 2022-06-01 08:34    [W:2.208 / U:0.548 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site