[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YXJw2fX42REHylOy@google.com>
Date: Fri, 22 Oct 2021 09:05:45 +0100
From: Lee Jones <lee.jones@...aro.org>
To: Dmitry Osipenko <digetx@...il.com>, Wolfram Sang <wsa@...nel.org>
Cc: Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Alessandro Zummo <a.zummo@...ertech.it>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Laxman Dewangan <ldewangan@...dia.com>,
linux-kernel@...r.kernel.org, linux-rtc@...r.kernel.org,
linux-i2c@...r.kernel.org
Subject: Re: [PATCH v1 3/3] mfd: tps80031: Remove driver
On Thu, 21 Oct 2021, Dmitry Osipenko wrote:
> Driver was upstreamed in 2013 and never got a user, remove it.
>
> Signed-off-by: Dmitry Osipenko <digetx@...il.com>
> ---
> drivers/mfd/Kconfig | 14 -
> drivers/mfd/Makefile | 1 -
> drivers/mfd/tps80031.c | 526 -----------------------------
> include/linux/mfd/tps80031.h | 637 -----------------------------------
> 4 files changed, 1178 deletions(-)
> delete mode 100644 drivers/mfd/tps80031.c
> delete mode 100644 include/linux/mfd/tps80031.h
> -static const struct i2c_device_id tps80031_id_table[] = {
> - { "tps80031", TPS80031 },
> - { "tps80032", TPS80032 },
> - { }
> -};
This is an I2C driver, right?
I was under the impression that Linux could do auto-probing on I2C
devices? Such that they do not require platform code or DT in order
to bind?
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
Powered by blists - more mailing lists