From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Jai Luthra <jai.luthra@ideasonboard.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH v1 1/1] media: i2c: ds90ub960: Remove of_node assignment
Date: Thu, 3 Apr 2025 14:12:35 +0300 [thread overview]
Message-ID: <Z-5tI_WVF2YQQ837@smile.fi.intel.com> (raw)
In-Reply-To: <2e6599fd-0b79-430b-9e94-f731b60e1705@ideasonboard.com>
On Thu, Apr 03, 2025 at 02:01:40PM +0300, Tomi Valkeinen wrote:
> On 12/03/2025 19:41, Andy Shevchenko wrote:
> > Remove of_node assignment which duplicates fwnode in struct i2c_board_info.
> > In general drivers must not set both, it's quite confusing. The I²C core
> > will consider fwnode with a priority and of_node is subject to remove from
> > above mentioned data structure.
...
> > struct device *dev = &priv->client->dev;
> > struct ds90ub9xx_platform_data *ser_pdata = &rxport->ser.pdata;
> > struct i2c_board_info ser_info = {
> > - .of_node = to_of_node(rxport->ser.fwnode),
> > .fwnode = rxport->ser.fwnode,
> > .platform_data = ser_pdata,
> > };
>
> This sounds logical, but breaks the driver for me.
The above assignments are still confusing, but I think I understand what's
going on. You run on OF based environment and some code uses of_*() APIs
instead of fwnode ones. That's why the current implementation in the I²C core
doesn't work.
> I also couldn't find this documented and didn't immediately find this from
> the i2c core implementation side.
The current code does this:
client->dev.of_node = of_node_get(info->of_node);
client->dev.fwnode = info->fwnode;
when it should do something like device_set_node() instead.
> Or am I missing some patch (running on v6.14)?
Yeah, there is a series in the mailing list [1], but it has no comments and
no move so far...
TL;DR: it seems in this change is incomplete.
[1]: https://lore.kernel.org/r/20250312185137.4154173-1-andriy.shevchenko@linux.intel.com
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-04-03 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 17:41 [PATCH v1 1/1] media: i2c: ds90ub960: Remove of_node assignment Andy Shevchenko
2025-04-03 11:01 ` Tomi Valkeinen
2025-04-03 11:12 ` Andy Shevchenko [this message]
2025-04-07 15:51 ` 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=Z-5tI_WVF2YQQ837@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=jai.luthra@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.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