All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Bernhard Rosenkränzer" <bero@baylibre.com>,
	linux-mediatek@lists.infradead.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	matthias.bgg@gmail.com, angelogiocchino.delregno@collabora.com
Subject: Re: [PATCH v3 4/7] dt-bindings: pinctrl: add bindings for Mediatek MT8365 SoC
Date: Fri, 18 Nov 2022 11:52:30 -0800	[thread overview]
Message-ID: <7ha64o9h1d.fsf@baylibre.com> (raw)
In-Reply-To: <06e916b7-f8f2-6de5-f86e-7b020c052451@linaro.org>

Hi Krzysztof,

Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> writes:

> On 17/11/2022 22:03, Bernhard Rosenkränzer wrote:
>> Add devicetree bindings for Mediatek MT8365 pinctrl driver.
>> 
>> Signed-off-by: Bernhard Rosenkränzer <bero@baylibre.com>
>
> Thank you for your patch. There is something to discuss/improve.
>
>> +
>> +  pins-are-numbered:
>> +    $ref: /schemas/types.yaml#/definitions/flag
>> +    description: |
>> +      Specify the subnodes are using numbered pinmux to specify pins.
>
> Why would you name pins differently per board? And why this different
> naming of the same pins is a property of hardware?
>
> This looks like something to drop.

Yeah, having this as a flag kind of implies that this could be present
for some boards but not others.  But in practice, the driver requires it
to be present or just fails[1].  What's the right way to describe that?
We're just trying to add a binding that reflects the existing driver.

We also noticed that there's another documented binding with this
same flag[2] where similiarily, the driver simply requires it to be
present[2].

So is the way this flag is documented in the stm32 binding OK for the
mediatek one also?  If not, what would you suggest?

Thanks for the review,

Kevin

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pinctrl/mediatek/pinctrl-mtk-common.c#n1053
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml#n37
[3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pinctrl/stm32/pinctrl-stm32.c#n1499



WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Bernhard Rosenkränzer" <bero@baylibre.com>,
	linux-mediatek@lists.infradead.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	matthias.bgg@gmail.com, angelogiocchino.delregno@collabora.com
Subject: Re: [PATCH v3 4/7] dt-bindings: pinctrl: add bindings for Mediatek MT8365 SoC
Date: Fri, 18 Nov 2022 11:52:30 -0800	[thread overview]
Message-ID: <7ha64o9h1d.fsf@baylibre.com> (raw)
In-Reply-To: <06e916b7-f8f2-6de5-f86e-7b020c052451@linaro.org>

Hi Krzysztof,

Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> writes:

> On 17/11/2022 22:03, Bernhard Rosenkränzer wrote:
>> Add devicetree bindings for Mediatek MT8365 pinctrl driver.
>> 
>> Signed-off-by: Bernhard Rosenkränzer <bero@baylibre.com>
>
> Thank you for your patch. There is something to discuss/improve.
>
>> +
>> +  pins-are-numbered:
>> +    $ref: /schemas/types.yaml#/definitions/flag
>> +    description: |
>> +      Specify the subnodes are using numbered pinmux to specify pins.
>
> Why would you name pins differently per board? And why this different
> naming of the same pins is a property of hardware?
>
> This looks like something to drop.

Yeah, having this as a flag kind of implies that this could be present
for some boards but not others.  But in practice, the driver requires it
to be present or just fails[1].  What's the right way to describe that?
We're just trying to add a binding that reflects the existing driver.

We also noticed that there's another documented binding with this
same flag[2] where similiarily, the driver simply requires it to be
present[2].

So is the way this flag is documented in the stm32 binding OK for the
mediatek one also?  If not, what would you suggest?

Thanks for the review,

Kevin

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pinctrl/mediatek/pinctrl-mtk-common.c#n1053
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml#n37
[3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pinctrl/stm32/pinctrl-stm32.c#n1499


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-11-18 19:57 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 21:03 [PATCH v3 0/7] Add minimal MT8365 and MT8365-EVK support Bernhard Rosenkränzer
2022-11-17 21:03 ` Bernhard Rosenkränzer
2022-11-17 21:03 ` [PATCH v3 1/7] dt-bindings: arm64: dts: mediatek: Add mt8365-evk board Bernhard Rosenkränzer
2022-11-17 21:03   ` Bernhard Rosenkränzer
2022-11-18  8:15   ` Krzysztof Kozlowski
2022-11-18  8:15     ` Krzysztof Kozlowski
2022-11-17 21:03 ` [PATCH v3 2/7] dt-bindings: irq: mtk, sysirq: add support for mt8365 Bernhard Rosenkränzer
2022-11-17 21:03   ` Bernhard Rosenkränzer
2022-11-18  8:16   ` Krzysztof Kozlowski
2022-11-18  8:16     ` Krzysztof Kozlowski
2022-11-17 21:03 ` [PATCH v3 3/7] dt-bindings: mfd: syscon: Add mt8365-syscfg Bernhard Rosenkränzer
2022-11-17 21:03   ` Bernhard Rosenkränzer
2022-11-18  8:17   ` Krzysztof Kozlowski
2022-11-18  8:17     ` Krzysztof Kozlowski
2022-11-17 21:03 ` [PATCH v3 4/7] dt-bindings: pinctrl: add bindings for Mediatek MT8365 SoC Bernhard Rosenkränzer
2022-11-17 21:03   ` Bernhard Rosenkränzer
2022-11-18  8:25   ` Krzysztof Kozlowski
2022-11-18  8:25     ` Krzysztof Kozlowski
2022-11-18 19:52     ` Kevin Hilman [this message]
2022-11-18 19:52       ` Kevin Hilman
2022-11-20 10:40       ` Krzysztof Kozlowski
2022-11-20 10:40         ` Krzysztof Kozlowski
2022-11-20 14:38         ` Bernhard Rosenkränzer
2022-11-20 14:38           ` Bernhard Rosenkränzer
2022-11-21  1:58           ` Bernhard Rosenkränzer
2022-11-21  1:58             ` Bernhard Rosenkränzer
2022-11-21 10:20             ` Krzysztof Kozlowski
2022-11-21 10:20               ` Krzysztof Kozlowski
2022-11-17 21:03 ` [PATCH v3 5/7] dt-bindings: usb: mediatek,mtu3: add MT8365 SoC bindings Bernhard Rosenkränzer
2022-11-17 21:03   ` Bernhard Rosenkränzer
2022-11-17 21:03 ` [PATCH v3 6/7] dt-bindings: usb: mediatek,mtk-xhci: " Bernhard Rosenkränzer
2022-11-17 21:03   ` Bernhard Rosenkränzer
2022-11-17 21:03 ` [PATCH v3 7/7] arm64: dts: mediatek: Initial mt8365-evk support Bernhard Rosenkränzer
2022-11-17 21:03   ` Bernhard Rosenkränzer
2022-11-18 20:28   ` Kevin Hilman
2022-11-18 20:28     ` Kevin Hilman

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=7ha64o9h1d.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=angelogiocchino.delregno@collabora.com \
    --cc=bero@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.