* [PATCH v2] dt-bindings: remoteproc: Fix dead link to Keystone DSP GPIO binding
@ 2025-12-03 18:03 Soham Metha
2025-12-03 18:35 ` Krzysztof Kozlowski
2025-12-15 1:47 ` Mathieu Poirier
0 siblings, 2 replies; 5+ messages in thread
From: Soham Metha @ 2025-12-03 18:03 UTC (permalink / raw)
To: linux-kernel-mentees
Cc: shuah, skhan, linux-kernel, Soham Metha, Bjorn Andersson,
Mathieu Poirier, Rob Herring, Krzysztof Kozlowski, Conor Dooley,
linux-remoteproc, devicetree
The old text binding 'gpio-dsp-keystone.txt' was replaced by a DT schema in
commit aff0a1701b020c8e6b172f28828fd4f3e6eed41a
("dt-bindings: gpio: Convert ti,keystone-dsp-gpio to DT schema").
Update the reference to point to the new file.
Signed-off-by: Soham Metha <sohammetha01@gmail.com>
---
.../devicetree/bindings/remoteproc/ti,keystone-rproc.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/remoteproc/ti,keystone-rproc.txt b/Documentation/devicetree/bindings/remoteproc/ti,keystone-rproc.txt
index 463a97c11eff..91f0a3b0c0b2 100644
--- a/Documentation/devicetree/bindings/remoteproc/ti,keystone-rproc.txt
+++ b/Documentation/devicetree/bindings/remoteproc/ti,keystone-rproc.txt
@@ -66,7 +66,7 @@ The following are the mandatory properties:
- kick-gpios: Should specify the gpio device needed for the virtio IPC
stack. This will be used to interrupt the remote processor.
The gpio device to be used is as per the bindings in,
- Documentation/devicetree/bindings/gpio/gpio-dsp-keystone.txt
+ Documentation/devicetree/bindings/gpio/ti,keystone-dsp-gpio.yaml
SoC-specific Required properties:
---------------------------------
--
2.34.1
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH v2] dt-bindings: remoteproc: Fix dead link to Keystone DSP GPIO binding
2025-12-03 18:03 [PATCH v2] dt-bindings: remoteproc: Fix dead link to Keystone DSP GPIO binding Soham Metha
@ 2025-12-03 18:35 ` Krzysztof Kozlowski
2025-12-03 18:56 ` Soham Metha
2025-12-15 1:47 ` Mathieu Poirier
1 sibling, 1 reply; 5+ messages in thread
From: Krzysztof Kozlowski @ 2025-12-03 18:35 UTC (permalink / raw)
To: Soham Metha, linux-kernel-mentees
Cc: shuah, skhan, linux-kernel, Bjorn Andersson, Mathieu Poirier,
Rob Herring, Krzysztof Kozlowski, Conor Dooley, linux-remoteproc,
devicetree
On 03/12/2025 19:03, Soham Metha wrote:
> The old text binding 'gpio-dsp-keystone.txt' was replaced by a DT schema in
> commit aff0a1701b020c8e6b172f28828fd4f3e6eed41a
Did you actually read what I asked? I think you just sent it too fast to
be able to read entire multi-page document. If you read it, you would
see that abbrev is 12 characters/digits.
> ("dt-bindings: gpio: Convert ti,keystone-dsp-gpio to DT schema").
>
> Update the reference to point to the new file.
This wasn't here before, no need to add obvious statements.
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH v2] dt-bindings: remoteproc: Fix dead link to Keystone DSP GPIO binding
2025-12-03 18:35 ` Krzysztof Kozlowski
@ 2025-12-03 18:56 ` Soham Metha
2025-12-03 20:07 ` Krzysztof Kozlowski
0 siblings, 1 reply; 5+ messages in thread
From: Soham Metha @ 2025-12-03 18:56 UTC (permalink / raw)
To: Krzysztof Kozlowski, linux-kernel-mentees
Cc: shuah, skhan, linux-kernel, Bjorn Andersson, Mathieu Poirier,
Rob Herring, Krzysztof Kozlowski, Conor Dooley, linux-remoteproc,
devicetree
Thank you for the feedback.
On 04/12/25 00:05, Krzysztof Kozlowski wrote:
> On 03/12/2025 19:03, Soham Metha wrote:
>> The old text binding 'gpio-dsp-keystone.txt' was replaced by a DT schema in
>> commit aff0a1701b020c8e6b172f28828fd4f3e6eed41a
>
> Did you actually read what I asked? I think you just sent it too fast to
> be able to read entire multi-page document. If you read it, you would
> see that abbrev is 12 characters/digits.
>
I did see the documentation mention that the abbreviation should use
at least 12 characters, but I didn’t notice any upper limit mentioned
in the text. Because of this wording, I assumed longer values were
acceptable.
Should I send a v3 with a 12-character abbreviation?
>> ("dt-bindings: gpio: Convert ti,keystone-dsp-gpio to DT schema").
>>
>> Update the reference to point to the new file.
>
> This wasn't here before, no need to add obvious statements.
>
> Best regards,
> Krzysztof
--
Soham
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH v2] dt-bindings: remoteproc: Fix dead link to Keystone DSP GPIO binding
2025-12-03 18:56 ` Soham Metha
@ 2025-12-03 20:07 ` Krzysztof Kozlowski
0 siblings, 0 replies; 5+ messages in thread
From: Krzysztof Kozlowski @ 2025-12-03 20:07 UTC (permalink / raw)
To: Soham Metha, linux-kernel-mentees
Cc: shuah, skhan, linux-kernel, Bjorn Andersson, Mathieu Poirier,
Rob Herring, Krzysztof Kozlowski, Conor Dooley, linux-remoteproc,
devicetree
On 03/12/2025 19:56, Soham Metha wrote:
> Thank you for the feedback.
>
> On 04/12/25 00:05, Krzysztof Kozlowski wrote:
>> On 03/12/2025 19:03, Soham Metha wrote:
>>> The old text binding 'gpio-dsp-keystone.txt' was replaced by a DT schema in
>>> commit aff0a1701b020c8e6b172f28828fd4f3e6eed41a
>>
>> Did you actually read what I asked? I think you just sent it too fast to
>> be able to read entire multi-page document. If you read it, you would
>> see that abbrev is 12 characters/digits.
>>
>
> I did see the documentation mention that the abbreviation should use
> at least 12 characters, but I didn’t notice any upper limit mentioned
> in the text. Because of this wording, I assumed longer values were
> acceptable.
>
> Should I send a v3 with a 12-character abbreviation?
No need, this is just a nit.
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH v2] dt-bindings: remoteproc: Fix dead link to Keystone DSP GPIO binding
2025-12-03 18:03 [PATCH v2] dt-bindings: remoteproc: Fix dead link to Keystone DSP GPIO binding Soham Metha
2025-12-03 18:35 ` Krzysztof Kozlowski
@ 2025-12-15 1:47 ` Mathieu Poirier
1 sibling, 0 replies; 5+ messages in thread
From: Mathieu Poirier @ 2025-12-15 1:47 UTC (permalink / raw)
To: Soham Metha
Cc: linux-kernel-mentees, shuah, skhan, linux-kernel, Bjorn Andersson,
Rob Herring, Krzysztof Kozlowski, Conor Dooley, linux-remoteproc,
devicetree
On Wed, Dec 03, 2025 at 11:33:37PM +0530, Soham Metha wrote:
> The old text binding 'gpio-dsp-keystone.txt' was replaced by a DT schema in
> commit aff0a1701b020c8e6b172f28828fd4f3e6eed41a
> ("dt-bindings: gpio: Convert ti,keystone-dsp-gpio to DT schema").
>
> Update the reference to point to the new file.
>
> Signed-off-by: Soham Metha <sohammetha01@gmail.com>
> ---
> .../devicetree/bindings/remoteproc/ti,keystone-rproc.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Applied.
Thanks,
Mathieu
> diff --git a/Documentation/devicetree/bindings/remoteproc/ti,keystone-rproc.txt b/Documentation/devicetree/bindings/remoteproc/ti,keystone-rproc.txt
> index 463a97c11eff..91f0a3b0c0b2 100644
> --- a/Documentation/devicetree/bindings/remoteproc/ti,keystone-rproc.txt
> +++ b/Documentation/devicetree/bindings/remoteproc/ti,keystone-rproc.txt
> @@ -66,7 +66,7 @@ The following are the mandatory properties:
> - kick-gpios: Should specify the gpio device needed for the virtio IPC
> stack. This will be used to interrupt the remote processor.
> The gpio device to be used is as per the bindings in,
> - Documentation/devicetree/bindings/gpio/gpio-dsp-keystone.txt
> + Documentation/devicetree/bindings/gpio/ti,keystone-dsp-gpio.yaml
>
> SoC-specific Required properties:
> ---------------------------------
> --
> 2.34.1
>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2025-12-15 1:47 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-12-03 18:03 [PATCH v2] dt-bindings: remoteproc: Fix dead link to Keystone DSP GPIO binding Soham Metha
2025-12-03 18:35 ` Krzysztof Kozlowski
2025-12-03 18:56 ` Soham Metha
2025-12-03 20:07 ` Krzysztof Kozlowski
2025-12-15 1:47 ` Mathieu Poirier
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox