[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1807020810580.31530@fox.voss.local>
Date: Mon, 2 Jul 2018 08:41:23 +0200 (CEST)
From: Nikolaus Voss <nikolaus.voss@...wensteinmedical.de>
To: Andy Shevchenko <andy.shevchenko@...il.com>
cc: Jonathan Cameron <jic23@...nel.org>,
Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
Lorenzo Bianconi <lorenzo.bianconi83@...il.com>,
Linus Walleij <linus.walleij@...aro.org>,
Xiongfeng Wang <xiongfeng.wang@...aro.org>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] IIO: st_sensors_i2c: improve device enumeration
On Fri, 29 Jun 2018, Andy Shevchenko wrote:
> I'm not sure I understand how ->probe_new() is supposed to work
> against i2c_id_table, but I don't care for legacy platform data
> anyway.
>
> What I would like to point to is device_get_match_data() API which
> should simplify / unify the case how you get driver data.
This driver doesn't need any driver data/ platform_data beyond the
i2c_id_table name (which has already been matched when probe()/
probe_new() is called), so strictly neither of_match_table nor
apci_match_table would be necessary, because i2c DT/ ACPI enumeration also
matches against i2c_table names.
But thanks for the hint ;-).
Niko
Powered by blists - more mailing lists