public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
	Paul Elder <paul.elder@ideasonboard.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] media: i2c: thp7312: use fwnode_for_each_child_node()
Date: Tue, 8 Apr 2025 10:36:39 +0000	[thread overview]
Message-ID: <Z_T8N8aHR-2OzHAO@kekkonen.localdomain> (raw)
In-Reply-To: <3d8546b9-92bd-40da-a61a-4534ba7779db@gmail.com>

Hei Laurent, Matti,

On Tue, Apr 08, 2025 at 01:26:42PM +0300, Matti Vaittinen wrote:
> On 08/04/2025 13:12, Laurent Pinchart wrote:
> > Hi Sakari,
> > 
> > On Tue, Apr 08, 2025 at 08:48:45AM +0000, Sakari Ailus wrote:
> > > On Fri, Mar 21, 2025 at 12:41:00PM +0200, Laurent Pinchart wrote:
> > > > On Fri, Mar 21, 2025 at 10:58:27AM +0200, Matti Vaittinen wrote:
> > > > > When fwnode_for_each_available_child_node() is used on the device-tree
> > > > > backed systems, it renders to same operation as the
> > > > > fwnode_for_each_child_node(), because the fwnode_for_each_child_node()
> > > > > does only iterate through those device-tree nodes which are available.
> > > > 
> > > > This makes me wonder why the OF backend implements
> > > > fwnode_for_each_child_node() as fwnode_for_each_available_child_node().
> > > > Is that on purpose, or is it a bug ?
> > > 
> > > I discussed this with Rafael and he didn't recall why the original
> > > implementation was like that. The general direction later on has been not
> > > to present unavailable nodes over the fwnode interface.
> > > 
> > > So I'd say:
> > > 
> > > Reviewed-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> > > 
> > > We should also change the documentation of the fwnode API accordingly.
> > 
> > Does that also mean that the fwnode_for_each_available_child_node()
> > function will be dropped ? It's used by few drivers (5 in addition to
> > the thp7312 driver, plus 3 call sites in drivers/base/core.c), so a
> > patch series to drop it should be easy.
> > 
> 
> I assume the fwnode_for_each_available_child_node() still makes sense for
> ACPI backed users, no?

Not really (see my earlier explanation in
<Z9mQPJwnKAkPHriT@kekkonen.localdomain>). I think all the *available* stuff
should be removed from include/linux/property.h, apart from
fwnode_device_is_availble(), which should be turned to work on struct
device to signal its availability for device nodes only.

-- 
Terveisin,

Sakari Ailus

  reply	other threads:[~2025-04-08 10:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21  8:58 [PATCH v2] media: i2c: thp7312: use fwnode_for_each_child_node() Matti Vaittinen
2025-03-21 10:41 ` Laurent Pinchart
2025-03-24  9:28   ` Sakari Ailus
2025-04-08  8:48   ` Sakari Ailus
2025-04-08 10:12     ` Laurent Pinchart
2025-04-08 10:26       ` Matti Vaittinen
2025-04-08 10:36         ` Sakari Ailus [this message]
2025-04-08 10:42           ` Matti Vaittinen
2025-04-08 11:08             ` Sakari Ailus
2025-04-08 11:16               ` Laurent Pinchart
2025-04-08 11:40                 ` Matti Vaittinen

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_T8N8aHR-2OzHAO@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=mazziesaccount@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=paul.elder@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