public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Herve Codina <herve.codina@bootlin.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Luca Ceresoli <luca.ceresoli@bootlin.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [RFC PATCH 3/3] i2c: i2c-core-of: Handle i2c bus extensions
Date: Wed, 12 Feb 2025 10:45:49 +0100	[thread overview]
Message-ID: <20250212104549.6b1d8781@bootlin.com> (raw)
In-Reply-To: <71468d78-07aa-49b1-8b6d-3d98c6fc9893@kernel.org>

Hi Krzysztof,

On Wed, 12 Feb 2025 06:54:19 +0100
Krzysztof Kozlowski <krzk@kernel.org> wrote:

> On 05/02/2025 18:39, Herve Codina wrote:
> >  
> >  	dev_dbg(&adap->dev, "of_i2c: walking child nodes from %pOF\n", bus);
> >  
> > -	/* Register device directly attached to this bus */
> > +	/*
> > +	 * Register device directly described in this bus node before looking
> > +	 * at extensions.
> > +	 */
> >  	for_each_available_child_of_node(bus, node) {
> > +		/* Filter out extension node */
> > +		if (of_node_name_eq(node, "i2c-bus-extension"))  
> 
> Where is the ABI documented?
> 
> > +			continue;
> > +
> >  		if (of_node_test_and_set_flag(node, OF_POPULATED))
> >  			continue;
> >  
> > @@ -103,6 +110,23 @@ static void of_i2c_register_children(struct i2c_adapter *adap,
> >  			of_node_clear_flag(node, OF_POPULATED);
> >  		}
> >  	}
> > +
> > +	/* Look at extensions */
> > +	for_each_available_child_of_node(bus, node) {
> > +		if (!of_node_name_eq(node, "i2c-bus-extension"))
> > +			continue;
> > +
> > +		extension = of_parse_phandle(node, "i2c-bus", 0);  
> 
> And this?
> 
> > +		if (!extension)
> > +			continue;
> > +  

I know the binding is not present in this RFC series.

As I mentioned in my cover letter, the binding that needs to be updated is
available in dt-schema repo [0].

When the binding is be accepted in dt-schema repo, I will not be able to
change it and because two repos are involved, I cannot send the binding and
the implementation in the same series.

Before sending a patch to update the binding in dt-schema repo, I would
like first to discuss the proposed i2c bus extension idea in terms of:
  1) DT properties naming and purpose
  2) implementation

[0] https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/i2c/i2c-controller.yaml

Best regards,
Hervé

  reply	other threads:[~2025-02-12  9:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 17:39 [RFC PATCH 0/3] i2c: Introduce i2c bus extensions Herve Codina
2025-02-05 17:39 ` [RFC PATCH 1/3] i2c: core: Follow i2c-parent when retrieving an adapter from node Herve Codina
2025-04-03  9:03   ` Wolfram Sang
2025-04-03 10:50     ` Herve Codina
2025-04-03 11:20       ` Wolfram Sang
2025-04-03 12:21         ` Herve Codina
2025-02-05 17:39 ` [RFC PATCH 2/3] i2c: i2c-core-of: Move children registration in a dedicated function Herve Codina
2025-04-03  9:07   ` Wolfram Sang
2025-04-03 10:51     ` Herve Codina
2025-02-05 17:39 ` [RFC PATCH 3/3] i2c: i2c-core-of: Handle i2c bus extensions Herve Codina
2025-02-12  5:54   ` Krzysztof Kozlowski
2025-02-12  9:45     ` Herve Codina [this message]
2025-04-03  9:09   ` Wolfram Sang
2025-02-19 13:38 ` [RFC PATCH 0/3] i2c: Introduce " Herve Codina
2025-03-20 12:49 ` Wolfram Sang
2025-03-20 16:31   ` Luca Ceresoli
2025-03-20 21:37     ` Wolfram Sang
2025-04-03  9:15 ` Wolfram Sang
2025-06-12  7:52 ` Ayush Singh
2025-06-13  7:30   ` Herve Codina
2025-07-03 11:26     ` Ayush Singh
2025-07-03 15:19       ` Herve Codina

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=20250212104549.6b1d8781@bootlin.com \
    --to=herve.codina@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=robh@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --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