From: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Chester Lin <chester62515@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
devicetree@vger.kernel.org, NXP S32 Linux Team <s32@nxp.com>,
imx@lists.linux.dev, Christophe Lizzi <clizzi@redhat.com>,
Alberto Ruiz <aruizrui@redhat.com>,
Enric Balletbo <eballetb@redhat.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: linflexuart: add clock definitions
Date: Thu, 7 Nov 2024 14:00:54 +0200 [thread overview]
Message-ID: <5235d325-c33c-40cc-8304-b041b612e0e9@oss.nxp.com> (raw)
In-Reply-To: <f16771dc-533d-43b9-8c04-6470191fd191@kernel.org>
On 11/7/2024 1:53 PM, Krzysztof Kozlowski wrote:
> On 07/11/2024 12:46, Ciprian Costea wrote:
>> From: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
>>
>> Add clock definitions for NXP LINFlexD UART bindings
>> and update the binding examples with S32G2 node.
>
> Why?
>
> What you are doing we see easily from the diff. I do not see why. Your
> commit msg must explain this.
>
>>
>> Signed-off-by: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
>
> Please use subject prefixes matching the subsystem. You can get them for
> example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
> your patch is touching. For bindings, the preferred subjects are
> explained here:
> https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
>
> Missing serial prefix and final is fsl,s32-linflexuart, not linflexuart
>
Hello Krzysztof,
Thank you for your remarks. I will try to address them/add more context
for these changes in V4.
Regards,
Ciprian
>> ---
>> .../bindings/serial/fsl,s32-linflexuart.yaml | 29 +++++++++++++++++++
>> 1 file changed, 29 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml b/Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml
>> index 4171f524a928..2716a9cd6c22 100644
>> --- a/Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml
>> +++ b/Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml
>> @@ -34,10 +34,24 @@ properties:
>> interrupts:
>> maxItems: 1
>>
>> + clocks:
>> + items:
>> + - description:
>> + ipg clock drives the access to the LINFlexD
>> + iomapped registers
>> + - description: lin is the frequency of the baud clock
>> +
>> + clock-names:
>> + items:
>> + - const: ipg
>> + - const: lin
>> +
>> required:
>> - compatible
>> - reg
>> - interrupts
>> + - clocks
>> + - clock-names
>>
>> unevaluatedProperties: false
>>
>> @@ -47,4 +61,19 @@ examples:
>> compatible = "fsl,s32v234-linflexuart";
>> reg = <0x40053000 0x1000>;
>> interrupts = <0 59 4>;
>> + clocks = <&clks 132>, <&clks 131>;
>> + clock-names = "ipg", "lin";
>> + };
>> +
>> + - |
>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>> + #include <dt-bindings/interrupt-controller/irq.h>
>> +
>> + serial@401c8000 {
>> + compatible = "nxp,s32g2-linflexuart",
>> + "fsl,s32v234-linflexuart";
>> + reg = <0x401c8000 0x3000>;
>> + interrupts = <GIC_SPI 82 IRQ_TYPE_EDGE_RISING>;
>> + clocks = <&clks 13>, <&clks 14>;
>
> Nope, drop the example. Not explained why you need it and really no point.
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2024-11-07 12:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 11:46 [PATCH v3 0/2] add NXP LINFlexD UART clock support for S32G2/S32G3 Ciprian Costea
2024-11-07 11:46 ` [PATCH v3 1/2] dt-bindings: linflexuart: add clock definitions Ciprian Costea
2024-11-07 11:53 ` Krzysztof Kozlowski
2024-11-07 12:00 ` Ciprian Marian Costea [this message]
2024-11-07 11:53 ` Krzysztof Kozlowski
2024-11-07 12:05 ` Ciprian Marian Costea
2024-11-07 11:46 ` [PATCH v3 2/2] serial: fsl_linflexuart: add clock support Ciprian Costea
2024-11-07 15:19 ` Frank Li
2024-11-07 15:39 ` Ciprian Marian Costea
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=5235d325-c33c-40cc-8304-b041b612e0e9@oss.nxp.com \
--to=ciprianmarian.costea@oss.nxp.com \
--cc=aruizrui@redhat.com \
--cc=chester62515@gmail.com \
--cc=clizzi@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eballetb@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s32@nxp.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
all inboxes | Powered by JetHome®