From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] i2c: core: Move client towards fwnode
Date: Mon, 7 Apr 2025 14:34:48 +0300 [thread overview]
Message-ID: <d51a686c-583a-4fed-81bd-9287459c48fe@ideasonboard.com> (raw)
In-Reply-To: <20250407095852.215809-1-andriy.shevchenko@linux.intel.com>
Hi Andy,
On 07/04/2025 12:55, Andy Shevchenko wrote:
> The struct i2c_board_info has of_node and fwnode members. This is
> quite confusing as they are of the same semantics and it's tend
> to have an issue if user assigns both. Luckily there is only a
> single driver that does this and fix was sent today. Nevertheless
> the series moves the client handling code to use fwnode and deprecates
> the of_node member in the respective documentation.
>
> Tomi, can you test this series + the patch we discussed earlier so it works as
> expected?
I tested this series, and then tested this series + "[PATCH v1 1/1]
media: i2c: ds90ub960: Remove of_node assignment". I didn't see anything
amiss in either case.
Tested-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
I assume the ds90ub960 patch is the "single driver that does this and
fix was sent today"? If so, I think that patch could have been included
in this series as well, there's hardly a chance of conflicts with the
one liner. And if applied separately, we probably need to apply the
ub960 patch one kernel version later than this series.
Tomi
>
> In v2:
> - covered i2c-core-slave.c where it makes sense
> - covered i2c-core-of.c where it makes sense
> - rebased on top of the latest code base
>
> Andy Shevchenko (6):
> i2c: core: Drop duplicate check before calling OF APIs
> i2c: core: Unify the firmware node type check
> i2c: core: Switch to fwnode APIs to get IRQ
> i2c: core: Reuse fwnode variable where it makes sense
> i2c: core: Do not dereference fwnode in struct device
> i2c: core: Deprecate of_node in struct i2c_board_info
>
> drivers/i2c/i2c-core-base.c | 59 ++++++++++++++++++------------------
> drivers/i2c/i2c-core-of.c | 1 -
> drivers/i2c/i2c-core-slave.c | 11 ++++---
> include/linux/i2c.h | 2 +-
> 4 files changed, 37 insertions(+), 36 deletions(-)
>
next prev parent reply other threads:[~2025-04-07 11:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 9:55 [PATCH v2 0/6] i2c: core: Move client towards fwnode Andy Shevchenko
2025-04-07 9:55 ` [PATCH v2 1/6] i2c: core: Drop duplicate check before calling OF APIs Andy Shevchenko
2025-04-07 9:55 ` [PATCH v2 2/6] i2c: core: Unify the firmware node type check Andy Shevchenko
2025-04-07 12:45 ` kernel test robot
2025-04-07 13:48 ` Andy Shevchenko
2025-04-07 13:47 ` kernel test robot
2025-04-07 9:55 ` [PATCH v2 3/6] i2c: core: Switch to fwnode APIs to get IRQ Andy Shevchenko
2025-04-07 13:47 ` kernel test robot
2025-04-07 9:55 ` [PATCH v2 4/6] i2c: core: Reuse fwnode variable where it makes sense Andy Shevchenko
2025-04-07 9:55 ` [PATCH v2 5/6] i2c: core: Do not dereference fwnode in struct device Andy Shevchenko
2025-04-07 9:55 ` [PATCH v2 6/6] i2c: core: Deprecate of_node in struct i2c_board_info Andy Shevchenko
2025-04-07 11:34 ` Tomi Valkeinen [this message]
2025-04-07 12:23 ` [PATCH v2 0/6] i2c: core: Move client towards fwnode Andy Shevchenko
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=d51a686c-583a-4fed-81bd-9287459c48fe@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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