linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: [PATCH v1 3/3] mfd: tps80031: Remove driver
       [not found] ` <20211021192258.21968-4-digetx@gmail.com>
@ 2021-10-22  8:05   ` Lee Jones
  2021-10-22  8:20     ` Dmitry Osipenko
  0 siblings, 1 reply; 5+ messages in thread
From: Lee Jones @ 2021-10-22  8:05 UTC (permalink / raw)
  To: Dmitry Osipenko, Wolfram Sang
  Cc: Liam Girdwood, Mark Brown, Alessandro Zummo, Alexandre Belloni,
	Laxman Dewangan, linux-kernel, linux-rtc, linux-i2c

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@gmail.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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH v1 3/3] mfd: tps80031: Remove driver
  2021-10-22  8:05   ` [PATCH v1 3/3] mfd: tps80031: Remove driver Lee Jones
@ 2021-10-22  8:20     ` Dmitry Osipenko
  2021-10-22  8:46       ` Wolfram Sang
  2021-10-22  9:54       ` Lee Jones
  0 siblings, 2 replies; 5+ messages in thread
From: Dmitry Osipenko @ 2021-10-22  8:20 UTC (permalink / raw)
  To: Lee Jones, Wolfram Sang
  Cc: Liam Girdwood, Mark Brown, Alessandro Zummo, Alexandre Belloni,
	Laxman Dewangan, linux-kernel, linux-rtc, linux-i2c

22.10.2021 11:05, Lee Jones пишет:
> 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@gmail.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?
> 

It's I2C driver. I'm not sure about auto-probing because something
should provide information about device to Linux. It's possible to
detect/scan whether there is device sitting on I2C address, but there is
no auto-discovery mechanism, AFAIK.

TPS80031 device will fail to bind to this driver because it explicitly
requires platform data which should be NULL if device is probed solely
by I2C ID.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH v1 3/3] mfd: tps80031: Remove driver
  2021-10-22  8:20     ` Dmitry Osipenko
@ 2021-10-22  8:46       ` Wolfram Sang
  2021-10-22  8:50         ` Dmitry Osipenko
  2021-10-22  9:54       ` Lee Jones
  1 sibling, 1 reply; 5+ messages in thread
From: Wolfram Sang @ 2021-10-22  8:46 UTC (permalink / raw)
  To: Dmitry Osipenko
  Cc: Lee Jones, Liam Girdwood, Mark Brown, Alessandro Zummo,
	Alexandre Belloni, Laxman Dewangan, linux-kernel, linux-rtc,
	linux-i2c

[-- Attachment #1: Type: text/plain, Size: 857 bytes --]


> It's I2C driver. I'm not sure about auto-probing because something
> should provide information about device to Linux. It's possible to
> detect/scan whether there is device sitting on I2C address, but there is
> no auto-discovery mechanism, AFAIK.

Well, in general, it could be manually instantiated from userspace...

> 
> TPS80031 device will fail to bind to this driver because it explicitly
> requires platform data which should be NULL if device is probed solely
> by I2C ID.

..but I agree in this case. The driver has this code:

        if (!pdata) {
                dev_err(&client->dev, "tps80031 requires platform data\n");
                return -EINVAL;
        }

and git grep shows no user having platform data.

Shouldn't 'drivers/regulator/tps80031-regulator.c' and
'./rtc/rtc-tps80031.c' be removed as well?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH v1 3/3] mfd: tps80031: Remove driver
  2021-10-22  8:46       ` Wolfram Sang
@ 2021-10-22  8:50         ` Dmitry Osipenko
  0 siblings, 0 replies; 5+ messages in thread
From: Dmitry Osipenko @ 2021-10-22  8:50 UTC (permalink / raw)
  To: Wolfram Sang, Lee Jones, Liam Girdwood, Mark Brown,
	Alessandro Zummo, Alexandre Belloni, Laxman Dewangan,
	linux-kernel, linux-rtc, linux-i2c

22.10.2021 11:46, Wolfram Sang пишет:
> 
>> It's I2C driver. I'm not sure about auto-probing because something
>> should provide information about device to Linux. It's possible to
>> detect/scan whether there is device sitting on I2C address, but there is
>> no auto-discovery mechanism, AFAIK.
> 
> Well, in general, it could be manually instantiated from userspace...
> 
>>
>> TPS80031 device will fail to bind to this driver because it explicitly
>> requires platform data which should be NULL if device is probed solely
>> by I2C ID.
> 
> ..but I agree in this case. The driver has this code:
> 
>         if (!pdata) {
>                 dev_err(&client->dev, "tps80031 requires platform data\n");
>                 return -EINVAL;
>         }
> 
> and git grep shows no user having platform data.
> 
> Shouldn't 'drivers/regulator/tps80031-regulator.c' and
> './rtc/rtc-tps80031.c' be removed as well?
> 

They are removed by the other 2 patches of this series [1].

[1] https://lore.kernel.org/all/20211021192258.21968-1-digetx@gmail.com/

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH v1 3/3] mfd: tps80031: Remove driver
  2021-10-22  8:20     ` Dmitry Osipenko
  2021-10-22  8:46       ` Wolfram Sang
@ 2021-10-22  9:54       ` Lee Jones
  1 sibling, 0 replies; 5+ messages in thread
From: Lee Jones @ 2021-10-22  9:54 UTC (permalink / raw)
  To: Dmitry Osipenko
  Cc: Wolfram Sang, Liam Girdwood, Mark Brown, Alessandro Zummo,
	Alexandre Belloni, Laxman Dewangan, linux-kernel, linux-rtc,
	linux-i2c

On Fri, 22 Oct 2021, Dmitry Osipenko wrote:

> 22.10.2021 11:05, Lee Jones пишет:
> > 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@gmail.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?
> > 
> 
> It's I2C driver. I'm not sure about auto-probing because something
> should provide information about device to Linux. It's possible to
> detect/scan whether there is device sitting on I2C address, but there is
> no auto-discovery mechanism, AFAIK.
> 
> TPS80031 device will fail to bind to this driver because it explicitly
> requires platform data which should be NULL if device is probed solely
> by I2C ID.

This is a fair point.

I'll take the patch, thanks.

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2021-10-22  9:54 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20211021192258.21968-1-digetx@gmail.com>
     [not found] ` <20211021192258.21968-4-digetx@gmail.com>
2021-10-22  8:05   ` [PATCH v1 3/3] mfd: tps80031: Remove driver Lee Jones
2021-10-22  8:20     ` Dmitry Osipenko
2021-10-22  8:46       ` Wolfram Sang
2021-10-22  8:50         ` Dmitry Osipenko
2021-10-22  9:54       ` Lee Jones

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).