linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ayush Singh <ayush@beagleboard.org>,
	Mark Brown <broonie@kernel.org>,
	herve.codina@bootlin.com, luca.ceresoli@bootlin.com,
	conor+dt@kernel.org, Jason Kridner <jkridner@beagleboard.org>,
	Deepak Khatri <lorforlinux@beagleboard.org>,
	Dhruva Gole <d-gole@ti.com>,
	Robert Nelson <robertcnelson@beagleboard.org>,
	Andrew Davis <afd@ti.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 3/4] spi: Handle spi bus extension
Date: Tue, 29 Jul 2025 15:09:10 +0200	[thread overview]
Message-ID: <2f13c7fd-fa60-4151-ae1f-1a522e98b33e@kernel.org> (raw)
In-Reply-To: <e01669d6-a233-4e64-a0e9-56b54c7d38cd@beagleboard.org>

On 29/07/2025 14:52, Ayush Singh wrote:
> On 7/29/25 18:16, Krzysztof Kozlowski wrote:
> 
>> On 29/07/2025 11:51, Ayush Singh wrote:
>>>   	for_each_available_child_of_node(node, nc) {
>>> +		/* Filter out extension node */
>>> +		if (of_node_name_eq(nc, "spi-bus-extension"))
>>> +			continue;
>>> +
>>>   		if (of_node_test_and_set_flag(nc, OF_POPULATED))
>>>   			continue;
>>>   
>>> @@ -2541,6 +2549,23 @@ static void of_register_spi_children(struct spi_controller *ctlr,
>>>   			of_node_clear_flag(nc, OF_POPULATED);
>>>   		}
>>>   	}
>>> +
>>> +	/* Look at extensions */
>>> +	for_each_available_child_of_node(node, nc) {
>>> +		if (!of_node_name_eq(nc, "spi-bus-extension"))
>> Where did you document the new ABI? There is no DT bindings patch with it.
> 
> Patch 4 is the dt bindings patch. I will reorder the patches in any 
> future to make the dt bindings patch 1.
> 
> Here is a direct link in case it got lost in mail: 
> https://lore.kernel.org/all/20250729-spi-bus-extension-v1-4-b20c73f2161a@beagleboard.org/


I found it, just did not spot as a binding because my filters expect
certain subjects (see submitting patches in DT subdir).

Best regards,
Krzysztof

  reply	other threads:[~2025-07-29 13:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-29  9:50 [PATCH 0/4] spi: Introduce spi bus extensions Ayush Singh
2025-07-29  9:51 ` [PATCH 1/4] spi: Follow spi-parent when retrieving a controller from node Ayush Singh
2025-07-29  9:51 ` [PATCH 2/4] spi: Move children registration in a dedicated function Ayush Singh
2025-07-29  9:51 ` [PATCH 3/4] spi: Handle spi bus extension Ayush Singh
2025-07-29 12:46   ` Krzysztof Kozlowski
2025-07-29 12:52     ` Ayush Singh
2025-07-29 13:09       ` Krzysztof Kozlowski [this message]
2025-07-29  9:51 ` [PATCH 4/4] devicetree: bindings: spi: Introduce SPI bus extensions Ayush Singh
2025-07-29 12:52   ` Krzysztof Kozlowski
2025-07-30 15:45     ` Luca Ceresoli
2025-07-30 18:30       ` Andrew Davis
2025-07-29 13:12   ` Rob Herring (Arm)

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=2f13c7fd-fa60-4151-ae1f-1a522e98b33e@kernel.org \
    --to=krzk@kernel.org \
    --cc=afd@ti.com \
    --cc=ayush@beagleboard.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=d-gole@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=herve.codina@bootlin.com \
    --cc=jkridner@beagleboard.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=lorforlinux@beagleboard.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=robertcnelson@beagleboard.org \
    --cc=robh@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;
as well as URLs for NNTP newsgroup(s).