[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VcF2Xg4dz7Ea1L653wRqAgSJZvbwua1oWzw-Lsqttxvng@mail.gmail.com>
Date:   Mon, 10 Jan 2022 13:05:47 +0200
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Nikita Yushchenko <nikita.yoush@...entembedded.com>
Cc:     Jonathan Cameron <jic23@...nel.org>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        Alexandru Ardelean <aardelean@...iqon.com>,
        Cai Huoqing <caihuoqing@...du.com>,
        linux-iio <linux-iio@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] iio: stm: don't always auto-enable I2C and SPI
 interface drivers
On Mon, Jan 10, 2022 at 9:30 AM Nikita Yushchenko
<nikita.yoush@...entembedded.com> wrote:
>
> This patch makes I2C and SPI interface drivers for STMicroelectronics
> sensor chips individually selectable via Kconfig.
>
> The default is kept unchanged - I2C and SPI interface drivers are still
> selected by default if the corresponding bus support is available.
>
> However, the patch makes it is possible to explicitly disable drivers
it possible
> that are not needed for particular target.
a particular
...
>  config IIO_ST_LSM9DS0_I2C
> +       tristate "STMicroelectronics LSM9DS0 IMU I2C interface"
> +       depends on I2C && IIO_ST_LSM9DS0
> +       default I2C && IIO_ST_LSM9DS0
Have you tested this for the case
I2C=y
IIO_ST_LSM9DS0=m
So, what is the result?
-- 
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists
 
