From: Chester Lin <clin@suse.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Rob Herring <robh+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
s32@nxp.com, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Larisa Grigore <larisa.grigore@nxp.com>,
Ghennadi Procopciuc <Ghennadi.Procopciuc@nxp.com>,
Andrei Stefanescu <andrei.stefanescu@nxp.com>,
Matthias Brugger <mbrugger@suse.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: pinctrl: add schema for NXP S32 SoCs
Date: Tue, 29 Nov 2022 22:52:02 +0800 [thread overview]
Message-ID: <Y4Yckl3wl0i/nTwF@linux-8mug> (raw)
In-Reply-To: <6d328461-d705-9e82-ccf3-dec8885f17fe@suse.de>
Hi Andreas,
On Tue, Nov 29, 2022 at 03:00:52PM +0100, Andreas Färber wrote:
> Hi Chester,
>
> Am 28.11.22 um 06:48 schrieb Chester Lin:
> > Add DT schema for the pinctrl driver of NXP S32 SoC family.
> >
> > Signed-off-by: Larisa Grigore <larisa.grigore@nxp.com>
> > Signed-off-by: Ghennadi Procopciuc <Ghennadi.Procopciuc@nxp.com>
> > Signed-off-by: Andrei Stefanescu <andrei.stefanescu@nxp.com>
> > Signed-off-by: Chester Lin <clin@suse.com>
> > ---
> >
> > Changes in v2:
> > - Remove the "nxp,pins" property since it has been moved into the driver.
> > - Add descriptions for reg entries.
> > - Refine the compatible name from "nxp,s32g-..." to "nxp,s32g2-...".
>
> Thanks.
>
> > - Fix schema issues and revise the example.
> > - Fix the copyright format suggested by NXP.
> >
> > .../pinctrl/nxp,s32cc-siul2-pinctrl.yaml | 125 ++++++++++++++++++
> > 1 file changed, 125 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/pinctrl/nxp,s32cc-siul2-pinctrl.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/pinctrl/nxp,s32cc-siul2-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/nxp,s32cc-siul2-pinctrl.yaml
> > new file mode 100644
> > index 000000000000..2fc25a9362af
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/pinctrl/nxp,s32cc-siul2-pinctrl.yaml
> > @@ -0,0 +1,125 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>
> Any reason the code is GPL-2.0-or-later but the schema is GPL-2.0-only?
>
Actually this patch is modified from an original downstream schema, which has
"GPL-2.0-only". See:
https://source.codeaurora.org/external/autobsps32/linux/tree/Documentation/devicetree/bindings/pinctrl/nxp,s32cc-siul2.yaml?h=bsp34.0-5.10.120-rt#n1
> > +# Copyright 2022 NXP
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/pinctrl/nxp,s32cc-siul2-pinctrl.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: NXP S32 Common Chassis SIUL2 iomux controller
> > +
> > +maintainers:
> > + - Ghennadi Procopciuc <Ghennadi.Procopciuc@nxp.com>
> > + - Chester Lin <clin@suse.com>
> > +
> > +description: |
> > + Core driver for the pin controller found on S32 Common Chassis SoC.
>
> SoC family
>
Will fix in v3.
> > +
> > +properties:
> > + compatible:
> > + enum:
> > + - nxp,s32g2-siul2-pinctrl
> > +
> > + reg:
> > + description:
> > + A list of MSCR/IMCR register regions to be reserved.
> > + - MSCR (Multiplexed Signal Configuration Register)
> > + An MSCR register can configure the associated pin as either a GPIO pin
> > + or a function output pin depends on the selected signal source.
> > + - IMCR (Input Multiplexed Signal Configuration Register)
> > + An IMCR register can configure the associated pin as function input
> > + pin depends on the selected signal source.
>
> Does this multi-paragraph text not need "description: |" like above?
>
Will fix in v3, thanks for the reminder.
> > + minItems: 5
> > + items:
> > + - description: MSCR registers group 0 managed by the SIUL2 controller 0
> > + - description: MSCR registers group 1 managed by the SIUL2 controller 1
> > + - description: MSCR registers group 2 managed by the SIUL2 controller 1
> > + - description: IMCR registers group 0 managed by the SIUL2 controller 0
> > + - description: IMCR registers group 1 managed by the SIUL2 controller 1
> > + - description: IMCR registers group 2 managed by the SIUL2 controller 1
> > +
> > +required:
> > + - compatible
> > + - reg
> > +
> > +patternProperties:
> > + '-pins$':
> > + type: object
> > + additionalProperties: false
> > +
> > + patternProperties:
> > + '-grp[0-9]$':
> > + type: object
> > + allOf:
> > + - $ref: pinmux-node.yaml#
> > + - $ref: pincfg-node.yaml#
> > + unevaluatedProperties: false
> > + description:
> > + Pinctrl node's client devices specify pin muxes using subnodes,
> > + which in turn use the standard properties.
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > +
> > + /* Pins functions (SSS field) */
> > + #define FUNC0 0
> > + #define FUNC1 1
> > + #define FUNC2 2
> > + #define FUNC3 3
> > + #define FUNC4 4
> > + #define FUNC5 5
> > + #define FUNC6 6
> > + #define FUNC7 7
> > +
> > + #define S32CC_PINMUX(PIN, FUNC) (((PIN) << 4) | (FUNC))
> > +
> > + #define S32CC_SLEW_208MHZ 0
> > + #define S32CC_SLEW_166MHZ 4
> > + #define S32CC_SLEW_150MHZ 5
> > + #define S32CC_SLEW_133MHZ 6
> > + #define S32CC_SLEW_83MHZ 7
>
> I notice that neither this patch nor the following one introduces a
> dt-bindings header for these macros? Is the plan to only have them in TF-A
> sources? Thinking of DT overlays for SoMs, for example.
>
Yes, it is. Since the current arch relies on the FDT offered by NXP's
downstream TF-A, only TF-A sources include the dt-bindings header in order
to refer to these macros. However, introduce these macros in this example
can still help developers to understand how a pinmux constructs.
Regards,
Chester
> Regards,
> Andreas
>
> > +
> > + pinctrl@4009c240 {
> > + compatible = "nxp,s32g2-siul2-pinctrl";
> > +
> > + /*
> > + * There are two SIUL2 controllers in S32G2:
> > + *
> > + * siul2_0 @ 0x4009c000
> > + * siul2_1 @ 0x44010000
> > + *
> > + * Every SIUL2 controller has multiple register types, and here
> > + * only MSCR and IMCR registers need to be revealed for kernel
> > + * to configure pinmux. Please note that some indexes are reserved,
> > + * such as MSCR102-MSCR111 in the following reg property.
> > + */
> > +
> > + /* MSCR0-MSCR101 registers on siul2_0 */
> > + reg = <0x4009c240 0x198>,
> > + /* MSCR112-MSCR122 registers on siul2_1 */
> > + <0x44010400 0x2c>,
> > + /* MSCR144-MSCR190 registers on siul2_1 */
> > + <0x44010480 0xbc>,
> > + /* IMCR0-IMCR83 registers on siul2_0 */
> > + <0x4009ca40 0x150>,
> > + /* IMCR119-IMCR397 registers on siul2_1 */
> > + <0x44010c1c 0x45c>,
> > + /* IMCR430-IMCR495 registers on siul2_1 */
> > + <0x440110f8 0x108>;
> > +
> > + llce-can0-pins {
> > + llce-can0-grp0 {
> > + pinmux = <S32CC_PINMUX(43, FUNC0)>;
> > + input-enable;
> > + slew-rate = <S32CC_SLEW_208MHZ>;
> > + };
> > +
> > + llce-can0-grp1 {
> > + pinmux = <S32CC_PINMUX(44, FUNC2)>;
> > + output-enable;
> > + slew-rate = <S32CC_SLEW_208MHZ>;
> > + };
> > + };
> > + };
> > +...
>
> --
> SUSE Software Solutions Germany GmbH
> Frankenstraße 146, 90461 Nürnberg, Germany
> GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
> HRB 36809 (AG Nürnberg)
next prev parent reply other threads:[~2022-11-29 14:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 5:48 [PATCH v2 0/2] Add pinctrl support for S32 SoC family Chester Lin
2022-11-28 5:48 ` [PATCH v2 1/2] dt-bindings: pinctrl: add schema for NXP S32 SoCs Chester Lin
2022-11-29 14:00 ` Andreas Färber
2022-11-29 14:52 ` Chester Lin [this message]
2022-11-30 14:58 ` Krzysztof Kozlowski
2022-12-05 6:16 ` Chester Lin
2022-12-05 9:02 ` Krzysztof Kozlowski
2022-12-05 11:05 ` Chester Lin
2022-12-05 13:26 ` Krzysztof Kozlowski
2022-11-28 5:48 ` [PATCH v2 2/2] pinctrl: add NXP S32 SoC family support Chester Lin
2022-11-29 13:40 ` Andreas Färber
2022-12-05 7:06 ` Chester Lin
2022-12-07 22:52 ` Linus Walleij
2022-12-07 23:04 ` Fabio Estevam
2022-12-08 21:37 ` Linus Walleij
2022-12-09 4:38 ` Chester Lin
2022-12-09 11:27 ` Linus Walleij
2022-12-14 23:08 ` Saravana Kannan
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=Y4Yckl3wl0i/nTwF@linux-8mug \
--to=clin@suse.com \
--cc=Ghennadi.Procopciuc@nxp.com \
--cc=afaerber@suse.de \
--cc=andrei.stefanescu@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=larisa.grigore@nxp.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).