From: "Tanwar, Rahul" <rahul.tanwar@linux.intel.com>
To: Rob Herring <robh@kernel.org>
Cc: linus.walleij@linaro.org, mark.rutland@arm.com,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, andriy.shevchenko@intel.com,
qi-ming.wu@intel.com, yixin.zhu@linux.intel.com,
cheol.yong.kim@intel.com
Subject: Re: [PATCH v3 2/2] dt-bindings: pinctrl: intel: Add for new SoC
Date: Wed, 6 Nov 2019 18:24:25 +0800 [thread overview]
Message-ID: <e7d1d72e-54d7-63ae-0eae-685a207d36ef@linux.intel.com> (raw)
In-Reply-To: <20191105212941.GA8677@bogus>
Hi Rob,
Thanks for the feedback.
On 6/11/2019 5:29 AM, Rob Herring wrote:
>> + bias-pull-up:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description: Specifies pull-up configuration.
> Isn't this boolean?
>
>> +
>> + bias-pull-down:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description: Specifies pull-down configuration.
> And this?
>
> Though looks like sometimes it has a value? Pull strength I guess.
>
>> +
>> + drive-strength:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description: Enables driver-current.
>> +
>> + slew-rate:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description: Enables slew-rate.
>> +
>> + drive-open-drain:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description: Specifies open-drain configuration.
> boolean?
>
>> +
>> + output-enable:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description: Specifies if the pin is to be configured as output.
> boolean?
>
> But really, all of these should have a common schema defining the types
> and only put any additional constraints here.
Yes, you are right. These are all boolean types.
All these are standard properties & we are using them with no
additional constraintsi.e conforming to how they are already
documented in pinctrl-bindings.txt. Shall ijust omit documenting
these properties here in driver bindings ?
>> +
>> +examples:
>> + # Pinmux controller node
>> + - |
>> + pinctrl: pinctrl@e2880000 {
>> + compatible = "intel,lgm-pinctrl";
>> + reg = <0xe2880000 0x100000>;
>> +
>> + # Client device subnode
>> + uart0:uart0 {
> space ^
Just to be sure, you mean space misalignment at below
line <65>; /* UART_TX0 */ ?Or is it something else ?
>> + pins = <64>, /* UART_RX0 */
>> + <65>; /* UART_TX0 */
>> + function = "CONSOLE_UART0";
>> + pinmux = <1>,
>> + <1>;
>> + groups = "CONSOLE_UART0";
>> + };
>> + };
>> +
>> +...
>> --
>> 2.11.0
>>
Regards,
Rahul
next prev parent reply other threads:[~2019-11-06 10:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 6:49 [PATCH v3 0/2] pinctrl: Add new pinctrl/GPIO driver Rahul Tanwar
2019-11-05 6:49 ` [PATCH v3 1/2] pinctrl: Add pinmux & GPIO controller driver for a new SoC Rahul Tanwar
2019-11-05 9:49 ` Andy Shevchenko
2019-11-05 10:52 ` Tanwar, Rahul
2019-11-05 12:05 ` Andy Shevchenko
2019-11-05 6:49 ` [PATCH v3 2/2] dt-bindings: pinctrl: intel: Add for " Rahul Tanwar
2019-11-05 21:29 ` Rob Herring
2019-11-06 10:24 ` Tanwar, Rahul [this message]
2019-11-06 10:29 ` Tanwar, Rahul
2019-11-05 9:46 ` [PATCH v3 0/2] pinctrl: Add new pinctrl/GPIO driver Linus Walleij
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=e7d1d72e-54d7-63ae-0eae-685a207d36ef@linux.intel.com \
--to=rahul.tanwar@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=qi-ming.wu@intel.com \
--cc=robh@kernel.org \
--cc=yixin.zhu@linux.intel.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).