From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Wolfram Sang <wsa@kernel.org>,
linux-i2c@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v4 2/3] i2c: Add i2c_device_get_match_data() callback
Date: Wed, 2 Aug 2023 18:08:39 +0300 [thread overview]
Message-ID: <ZMpxd91WelcwGicN@smile.fi.intel.com> (raw)
In-Reply-To: <20230802112317.252745-3-biju.das.jz@bp.renesas.com>
On Wed, Aug 02, 2023 at 12:23:16PM +0100, Biju Das wrote:
> Add i2c_device_get_match_data() callback to struct bus_type().
>
> While at it, introduced i2c_get_match_data_helper() to avoid code
> duplication with i2c_get_match_data().
...
> +static const void *i2c_get_match_data_helper(const struct i2c_client *client)
> {
> - struct i2c_driver *driver = to_i2c_driver(client->dev.driver);
> + const struct i2c_driver *driver = to_i2c_driver(client->dev.driver);
> const struct i2c_device_id *match;
> +
> + match = i2c_match_id(driver->id_table, client);
> + if (!match)
> + return NULL;
> +
> + return (const void *)match->driver_data;
> +}
Yes, perfect!
...
> +static const void *i2c_device_get_match_data(const struct device *dev)
> +{
> + /* TODO: use i2c_verify_client() when it accepts const pointer */
> + const struct i2c_client *client = (dev->type == &i2c_client_type) ?
> + to_i2c_client(dev) : NULL;
> +
> + if (!client || !dev->driver)
> + return NULL;
> +
> + return i2c_get_match_data_helper(client);
I believe below looks better from readability and maintenance perspectives.
const struct i2c_client *client;
/* ...comment as in Dmitry's reply in v3 thread on why we need this check... */
if (!dev->driver)
return NULL;
/* TODO: use i2c_verify_client() when it accepts const pointer */
client = (dev->type == &i2c_client_type) ? to_i2c_client(dev) : NULL;
if (!client)
return NULL;
> + return i2c_get_match_data_helper(client);
> +}
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-08-02 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 11:23 [PATCH v4 0/3] Extend device_get_match_data() to struct bus_type Biju Das
2023-08-02 11:23 ` [PATCH v4 1/3] drivers: fwnode: " Biju Das
2023-08-02 11:23 ` [PATCH v4 2/3] i2c: Add i2c_device_get_match_data() callback Biju Das
2023-08-02 15:08 ` Andy Shevchenko [this message]
2023-08-03 6:01 ` Biju Das
2023-08-02 11:23 ` [PATCH v4 3/3] i2c: Extend i2c_device_get_match_data() to support i2c sysfs Biju Das
2023-08-02 18:00 ` Dmitry Torokhov
2023-08-03 6:05 ` Biju Das
2023-08-02 21:39 ` Andy Shevchenko
2023-08-03 6:04 ` 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=ZMpxd91WelcwGicN@smile.fi.intel.com \
--to=andriy.shevchenko@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.