From: Dmitry Torokhov <dmitry.torokhov@gmail.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>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH RFC 2/2] i2c: Add i2c_device_get_match_data() callback
Date: Sun, 23 Jul 2023 13:08:15 -0700 [thread overview]
Message-ID: <ZL2Ir6ZZoewOwMNf@google.com> (raw)
In-Reply-To: <20230723083721.35384-3-biju.das.jz@bp.renesas.com>
On Sun, Jul 23, 2023 at 09:37:21AM +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().
>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
> drivers/i2c/i2c-core-base.c | 38 +++++++++++++++++++++++++++++--------
> 1 file changed, 30 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/i2c/i2c-core-base.c b/drivers/i2c/i2c-core-base.c
> index 60746652fd52..80259111355b 100644
> --- a/drivers/i2c/i2c-core-base.c
> +++ b/drivers/i2c/i2c-core-base.c
> @@ -114,20 +114,41 @@ const struct i2c_device_id *i2c_match_id(const struct i2c_device_id *id,
> }
> EXPORT_SYMBOL_GPL(i2c_match_id);
>
> +static void *i2c_get_match_data_helper(struct i2c_driver *driver,
> + const struct i2c_client *client)
> +{
> + const struct i2c_device_id *match;
> +
> + match = i2c_match_id(driver->id_table, client);
> + if (!match)
> + return NULL;
> +
> + return (const void *)match->driver_data;
Not sure if this helper is needed given that in the end (hopefully) we
can simply remove i2c_get_match_data() and leave only
i2c_device_get_match_data().
i2c_get_match_data() and leave only i2c_device_get_match_data().
Thanks.
--
Dmitry
next prev parent reply other threads:[~2023-07-23 20:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 8:37 [PATCH RFC 0/2] Extend device_get_match_data() to struct bus_type Biju Das
2023-07-23 8:37 ` [PATCH RFC 1/2] drivers: fwnode: " Biju Das
2023-07-24 11:06 ` Andy Shevchenko
2023-07-24 11:07 ` Andy Shevchenko
2023-07-24 11:46 ` Biju Das
2023-07-24 12:57 ` Andy Shevchenko
2023-07-24 13:35 ` Biju Das
2023-07-24 12:02 ` Biju Das
2023-07-24 13:00 ` Andy Shevchenko
2023-07-24 13:19 ` Biju Das
2023-07-24 13:50 ` Andy Shevchenko
2023-07-24 13:58 ` Biju Das
2023-07-24 16:38 ` Dmitry Torokhov
2023-07-26 5:33 ` Biju Das
2023-07-23 8:37 ` [PATCH RFC 2/2] i2c: Add i2c_device_get_match_data() callback Biju Das
2023-07-23 20:08 ` Dmitry Torokhov [this message]
2023-07-24 14:55 ` Geert Uytterhoeven
2023-07-24 15:06 ` Biju Das
2023-07-24 16:34 ` Dmitry Torokhov
2023-07-24 16:43 ` Geert Uytterhoeven
2023-07-24 16:47 ` Dmitry Torokhov
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=ZL2Ir6ZZoewOwMNf@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=biju.das.jz@bp.renesas.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