From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
Wolfram Sang <wsa@kernel.org>,
linux-i2c@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 2/2] i2c: Add i2c_device_get_match_data() callback
Date: Thu, 27 Jul 2023 12:59:35 +0300 [thread overview]
Message-ID: <ZMJAB7RcICd9wjdv@smile.fi.intel.com> (raw)
In-Reply-To: <CAKdAkRT1Zdut28YYG9PxOQXfvMGZuXD8=qG9q4KtHKNvsxy76A@mail.gmail.com>
On Wed, Jul 26, 2023 at 10:56:41AM -0700, Dmitry Torokhov wrote:
> On Wed, Jul 26, 2023 at 07:44:17PM +0300, Andy Shevchenko wrote:
> > On Wed, Jul 26, 2023 at 02:08:04PM +0100, Biju Das wrote:
...
> > > +static const void *i2c_device_get_match_data(const struct device *dev)
> > > +{
> > > + const struct i2c_client *client = (dev->type == &i2c_client_type) ?
> > > + to_i2c_client(dev) : NULL;
> >
> > There is an API i2c_verify_client() or something like this, I don't remember
> > by heart.
>
> It's been discussed in a separate thread. i2c_verify_client() needs a
> non-const pointer. It would be nice to clean up i2c_verify_client() to
> accept both variants, but that can be done later.
Then this code needs a TODO comment:
/* TODO: use i2c_verify_client() when it accepts const pointer */
> > > + if (!dev->driver)
> > > + return NULL;
> > > +
> > > + return i2c_get_match_data_helper(to_i2c_driver(dev->driver), client);
> > > +}
...
> > Side question, what is the idea for i2c_of_match_device()? Shouldn't you also
> > take it into consideration?
>
> Good call. I think we need to add something like
>
> if (!data && driver->driver.of_match_table) {
> match =
> i2c_of_match_device_sysfs(driver->driver.of_match_table, client);
> if (match)
> data = match->data;
> }
>
> to i2c_device_get_match_data().
Haven't checked myself, by I trust your suggestion. Let's see it in v3 then.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-07-27 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 13:08 [PATCH v2 0/2] Extend device_get_match_data() to struct bus_type Biju Das
2023-07-26 13:08 ` [PATCH v2 2/2] i2c: Add i2c_device_get_match_data() callback Biju Das
2023-07-26 16:44 ` Andy Shevchenko
2023-07-26 17:56 ` Dmitry Torokhov
2023-07-27 9:59 ` Andy Shevchenko [this message]
2023-08-01 6:46 ` Biju Das
2023-07-27 7:27 ` Biju Das
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=ZMJAB7RcICd9wjdv@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=dmitry.torokhov@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa@kernel.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