From: Nikolaus Voss <nikolaus.voss@loewensteinmedical.de>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Xiongfeng Wang <xiongfeng.wang@linaro.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] IIO: st_sensors_i2c: improve device enumeration
Date: Mon, 2 Jul 2018 08:41:23 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1807020810580.31530@fox.voss.local> (raw)
In-Reply-To: <CAHp75VfR8JZaDbvzudW5mc4=nOoYM2EeXPMhUHCw1ovnPmGV5A@mail.gmail.com>
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
next prev parent reply other threads:[~2018-07-02 6:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 10:30 Nikolaus Voss
2018-06-29 8:10 ` [PATCH 1/3] IIO: st_accel_i2c.c: Use fallback if DT/ACPI enum failed Nikolaus Voss
2018-06-30 15:28 ` Jonathan Cameron
2018-07-02 6:53 ` Nikolaus Voss
2018-07-02 13:05 ` Jonathan Cameron
2018-06-29 8:19 ` [PATCH 2/3] IIO: st_sensors_i2c.c: Don't print error on failed ACPI match Nikolaus Voss
2018-06-29 8:45 ` [PATCH 3/3] IIO: st_accel.h: sync DT and I2C device ID table strings Nikolaus Voss
2018-06-30 15:33 ` Jonathan Cameron
2018-07-02 7:32 ` Nikolaus Voss
2018-06-29 20:19 ` [PATCH 0/3] IIO: st_sensors_i2c: improve device enumeration Andy Shevchenko
2018-07-02 6:41 ` Nikolaus Voss [this message]
2018-07-02 16:14 ` Andy Shevchenko
2018-07-03 8:18 ` Nikolaus Voss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1807020810580.31530@fox.voss.local \
--to=nikolaus.voss@loewensteinmedical.de \
--cc=andy.shevchenko@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=xiongfeng.wang@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®