linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Tomer Maimon <tmaimon77@gmail.com>
Cc: linus.walleij@linaro.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	avifishman70@gmail.com, tali.perry1@gmail.com, joel@jms.id.au,
	venture@google.com, yuenn@google.com, benjaminfair@google.com,
	j.neuschaefer@gmx.net, openbmc@lists.ozlabs.org,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v6 1/2] dt-binding: pinctrl: Add NPCM8XX pinctrl and GPIO documentation
Date: Mon, 28 Aug 2023 12:39:34 +0200	[thread overview]
Message-ID: <5c0d985a-0492-778c-46b9-80899e52134c@linaro.org> (raw)
In-Reply-To: <c984d558-11b5-d5ea-9819-7641129de584@linaro.org>

On 28/08/2023 12:36, Krzysztof Kozlowski wrote:
> On 28/08/2023 12:26, Tomer Maimon wrote:
>> Hi Krzysztof,
>>
>> Thanks for your comments
>>
>> On Mon, 28 Aug 2023 at 10:10, Krzysztof Kozlowski
>> <krzysztof.kozlowski@linaro.org> wrote:
>>>
>>> On 27/08/2023 22:36, Tomer Maimon wrote:
>>>> Added device tree binding documentation for Nuvoton Arbel BMC NPCM8XX
>>>> pinmux and GPIO controller.
>>>>
>>>> Signed-off-by: Tomer Maimon <tmaimon77@gmail.com>
>>>> Reviewed-by: Rob Herring <robh@kernel.org>
>>>> ---
>>>
>>>
>>>> +  '^pin':
>>>> +    $ref: pincfg-node.yaml#
>>>> +
>>>> +    properties:
>>>> +      pins:
>>>> +        description:
>>>> +          A list of pins to configure in certain ways, such as enabling
>>>> +          debouncing
>>>
>>> What pin names are allowed?
>> Do you mean to describe all the allowed pin items?
>> for example:
>>       items:
>>         pattern:
>> 'GPIO0/IOX1_DI/SMB6C_SDA/SMB18_SDA|GPIO1/IOX1_LD/SMB6C_SCL/SMB18_SCL'
>> or
>>       items:
>>         pattern: '^GPIO([0-9]|[0-9][0-9]|[1-2][0-4][0-9]|25[0-6])$'
>>
>> is good enough?
> 
> Something like this. Whichever is correct.
> 
>>>
>>>> +
>>>> +      bias-disable: true
>>>> +
> 
>>>> +additionalProperties: false
>>>> +
>>>> +examples:
>>>> +  - |
>>>> +    #include <dt-bindings/interrupt-controller/arm-gic.h>
>>>> +    #include <dt-bindings/gpio/gpio.h>
>>>> +
>>>> +    soc {
>>>> +      #address-cells = <2>;
>>>> +      #size-cells = <2>;
>>>> +
>>>> +      pinctrl: pinctrl@f0800260 {
>>>
>>> Nothing improved here. Test your DTS. This is being reported - I checked.
>> what do you suggest since the pinctrl doesn't have a reg parameter,
>> maybe pinctrl: pinctrl@0?
> 
> It has ranges, so yes @0 looks correct here.

Wait, your address according to ranges is 0xf0010000, not 0x0, not
0xf0800260...


> Which leds to second
> question - how pinctrl could have @0? It's already taken by SoC! So your
> DTS here - unit address and ranges - are clearly wrong.
> 
> 
>> BTW, I have run both dt_binding_check and W=1 dtbs_check, and didn't
>> see an issue related to the pinctrl: pinctrl@f0800260, do I need to
>> add another flag to see the issue?
> 
> Did you read my message last time? I said - it's about DTS, not the binding.

Best regards,
Krzysztof


  reply	other threads:[~2023-08-28 10:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-27 20:36 [PATCH v6 0/2] pinctrl: nuvoton: add pinmux and GPIO driver for NPCM8XX Tomer Maimon
2023-08-27 20:36 ` [PATCH v6 1/2] dt-binding: pinctrl: Add NPCM8XX pinctrl and GPIO documentation Tomer Maimon
2023-08-28  7:10   ` Krzysztof Kozlowski
2023-08-28 10:26     ` Tomer Maimon
2023-08-28 10:36       ` Krzysztof Kozlowski
2023-08-28 10:39         ` Krzysztof Kozlowski [this message]
2023-08-28 11:43           ` Tomer Maimon
2023-08-28 12:30             ` Krzysztof Kozlowski
2023-08-27 20:36 ` [PATCH v6 2/2] pinctrl: nuvoton: add NPCM8XX pinctrl and GPIO driver Tomer Maimon
2023-08-28  7:08   ` Krzysztof Kozlowski

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=5c0d985a-0492-778c-46b9-80899e52134c@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=avifishman70@gmail.com \
    --cc=benjaminfair@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=j.neuschaefer@gmx.net \
    --cc=joel@jms.id.au \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=tali.perry1@gmail.com \
    --cc=tmaimon77@gmail.com \
    --cc=venture@google.com \
    --cc=yuenn@google.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).