All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fran Hsu (徐誌謙)" <Fran.Hsu@quantatw.com>
To: Tomer Maimon <tmaimon77@gmail.com>,
	Benjamin Fair <benjaminfair@google.com>
Cc: Emily Shaffer <emilyshaffer@google.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: RE: [PATCH dev-5.0 v1 2/3] ARM: dts: nuvoton: Add Quanta GSJ BMC machine.
Date: Mon, 1 Apr 2019 15:26:05 +0000	[thread overview]
Message-ID: <c751cf73e00843f8a9af8d4b56af775a@quantatw.com> (raw)
In-Reply-To: <0e83b98fe2cf4b41a15546651e73d79d@quantatw.com>

Hi Tomer,
	I think the main idea is to provide a full and common pinctrl file (just like nuvoton-npcm7xx-gpio.dtsi) for each NPCM7xx BMC family.
The device tree maintainers can reference the GPIO configuration from this file what they needed.
Once if the driver is changed, maybe the only change is the common pinctrl file.
But if there is no common pinctrl file, each device tree maintainers have to modify the gpio-dtsi file.
And as your opinion, there will be a lots of gpio-dtsi files for different boards or different vendors.
And most of gpio-dtsi files will include same GPIO setting.

Thanks,
Fran

>
>Hi Benjamin,
>
>On Sat, 30 Mar 2019 at 02:31, Benjamin Fair
<mailto:benjaminfair@google.com> wrote:
>Hi Fran,
>
>Thanks for sending these patches!
>
>On Thu, Mar 28, 2019 at 8:06 AM <mailto:fran.hsu@quantatw.com> wrote:
>>
>> From: FranHsu <mailto:Fran.Hsu@quantatw.com>
>>
>> Add pinctrl definition file for quanta-gsj BMC device tree.
>>
>> Signed-off-by: FranHsu <mailto:Fran.Hsu@quantatw.com>
>> ---
>>  .../boot/dts/nuvoton-npcm730-gsj-gpio.dtsi    | 2591
+++++++++++++++++
>>  1 file changed, 2591 insertions(+)
>>  create mode 100644 arch/arm/boot/dts/nuvoton-npcm730-gsj-gpio.dtsi
>
>Would it make more sense to merge this into the existing
>nuvoton-npcm750-gpio.dtsi file? That seems like it would make it easier to
>maintain the definitions and these are a superset of the existing ones, so it
>shouldn't conflict.
>
>the GPIO configuration depend on the server board that using it, we think it is
better that each
>server board or a family of server boards will have its own GPIO device tree
definition.
>
>We know that the GPIO device tree name and placement is confusing,
because is called nuvoton-npcm750-gpio.dtsi and not
nuvoton-npcm750-gpio-evb.dtsi
>and placed at nuvoton-npcm750.dtsi but should move the
nuvoton-npcm750-evb.dts file.
>
>we will modify the gpio npcm750 device tree soon.
>
>Fran,
>
>Does the nuvoton-npcm730-gsj-gpio.dtsi set GPIO configuration you are using
or will use in the future on Quanta server boards?
>For example I see you defined "gpio0o_pins" pin configuration, and you are
not using it in your dts file. will you use it in the future or in other Quanta
based NPCM7xx BMC boards?
>if not I think you should remove it. eqtully I think you should defined only the
GPIO/PIN configuration you are using, (I attend to do it at
nuvoton-npcm750-gpio.dtsi as well)
>
>
>>
>> diff --git a/arch/arm/boot/dts/nuvoton-npcm730-gsj-gpio.dtsi
b/arch/arm/boot/dts/nuvoton-npcm730-gsj-gpio.dtsi
>> new file mode 100644
>> index 000000000000..b66ea5099e5e
>> --- /dev/null
>> +++ b/arch/arm/boot/dts/nuvoton-npcm730-gsj-gpio.dtsi
>> @@ -0,0 +1,2591 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +// Copyright (c) 2018 Nuvoton Technology
mailto:tomer.maimon@nuvoton.com
>> +
>> +/ {
>> +       pinctrl: pinctrl@f0800000 {
>> +               gpio0o_pins: gpio0o-pins {
>> +                       pins = "GPIO0/IOX1DI";
>> +                       bias-disable;
>> +                       output-high;
>> +               };
>> +               gpio0ol_pins: gpio0ol-pins {
>> +                       pins = "GPIO0/IOX1DI";
>> +                       bias-disable;
>> +                       output-low;
>> +               };
>> +               gpio0od_pins: gpio0od-pins {
>> +                       pins = "GPIO0/IOX1DI";
>> +                       bias-disable;
>> +                       drive-open-drain;
>> +               };
>> +               gpio0pp_pins: gpio0pp-pins {
>> +                       pins = "GPIO0/IOX1DI";
>> +                       bias-disable;
>> +                       drive-push-pull;
>> +               };
>> +               gpio1_pins: gpio1-pins {
>> +                       pins = "GPIO1/IOX1LD";
>> +                       bias-disable;
>> +                       input-enable;
>> +               };
>> +               gpio1o_pins: gpio1o-pins {
>> +                       pins = "GPIO1/IOX1LD";
>> +                       bias-disable;
>> +                       output-high;
>> +               };
>> +               gpio1ol_pins: gpio1ol-pins {

  parent reply	other threads:[~2019-04-01 15:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28 15:05 [PATCH dev-5.0 v1 1/3] ARM: dts: nuvoton: Add Quanta GSJ BMC machine fran.hsu
2019-03-28 15:05 ` [PATCH dev-5.0 v1 2/3] " fran.hsu
2019-03-29 23:29   ` Benjamin Fair
2019-03-31  9:52     ` Tomer Maimon
     [not found]       ` <0e83b98fe2cf4b41a15546651e73d79d@quantatw.com>
2019-04-01 15:26         ` Fran Hsu (徐誌謙) [this message]
2019-04-01 17:51         ` Tomer Maimon
2019-04-02 13:54           ` Fran Hsu (徐誌謙)
2019-03-28 15:05 ` [PATCH dev-5.0 v1 3/3] " fran.hsu
2019-04-02 21:11   ` Benjamin Fair
2019-04-01  3:06 ` [PATCH dev-5.0 v1 1/3] " Joel Stanley

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=c751cf73e00843f8a9af8d4b56af775a@quantatw.com \
    --to=fran.hsu@quantatw.com \
    --cc=benjaminfair@google.com \
    --cc=emilyshaffer@google.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=tmaimon77@gmail.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 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.