From: Ping Guo <guopingjn@gmail.com>
To: Joel Stanley <joel@jms.id.au>
Cc: Andrew Jeffery <andrew@aj.id.au>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
guoping@inspur.com, banht@inspur.com, liuxiwei@inspur.com,
wangxinglong@inspur.com
Subject: Re: [PATCH 1/1] ARM: dts: aspeed: Add Inspur NF5280M6 BMC machine
Date: Wed, 26 May 2021 13:33:52 +0800 [thread overview]
Message-ID: <4f3bb433-d050-a4bf-1797-933cdec77bda@gmail.com> (raw)
In-Reply-To: <CACPK8XfGytJEmRDzdbCjLMT5jFWN67h7OOeH-bGJP6RgFJZDGw@mail.gmail.com>
On 5/25/21 3:27 PM, Joel Stanley wrote:
> On Tue, 25 May 2021 at 07:18, Joel Stanley <joel@jms.id.au> wrote:
>> On Tue, 25 May 2021 at 06:48, <guopingjn@gmail.com> wrote:
>>> From: Ping Guo <guoping@inspur.com>
>>>
>>> The Inspur NF5280M6 is an x86 platform server with an AST2500-based BMC.
>>> This dts file provides a basic configuration for its OpenBMC
>>> development.
>>>
>>> Signed-off-by: George Liu <liuxiwei@inspur.com>
>>> Signed-off-by: Ping Guo <guoping@inspur.com>
>> In the future you can use git format-patch to set a version on your
>> patch. "-v 2" will set the version to 2, for example.
>>
>>> ---
>> Put the changelog of what is different compared to last time just
>> below this ---. It won't be included in the git history of the kernel,
>> but it's for reviewers to understand what you've changed.
>>
>> The patch looks good. I will apply this for v5.14 and to the openbmc
>> dev-5.10 tree.
> I spoke too soon. There's a mistake below:
>
>>> +&gpio {
>>> + power_out {
>>> + gpios = <ASPEED_GPIO(AA, 7) GPIO_ACTIVE_LOW>;
> This warns:
>
> ../arch/arm/boot/dts/aspeed-bmc-inspur-nf5280m6.dts:138.3-30: Warning
> (gpios_property): /ahb/apb/gpio@1e780000/power_out:gpios: cell 0 is
> not a phandle reference
> ../arch/arm/boot/dts/aspeed-bmc-inspur-nf5280m6.dts:138.3-30: Warning
> (gpios_property): /ahb/apb/gpio@1e780000/power_out:gpios: Could not
> get phandle node for (cell 0)
>
> Taking a closer look, I'm not sure that it's a valid description. What
> are you trying to do there?
>
> Is it supposed to be a gpio hog?
Thanks for your reminder.I'll see.
>>> + output-low;
>>> + };
>>> +};
>>> +
>>> +&gpio {
>>> + status = "okay";
>>> + /* Enable GPIOE0 and GPIOE2 pass-through by default */
>>> + pinctrl-names = "pass-through";
>>> + pinctrl-0 = <&pinctrl_gpie0_default
>>> + &pinctrl_gpie2_default>;
>>> + gpio-line-names =
>>> +&gfx {
>>> + status = "okay";
>>> +};
> So you're using the BMC display device?
Negative.I'll remove this node.
>>> +
>>> +&kcs3 {
>>> + status = "okay";
>>> + kcs_addr = <0xca2>;
> This is the old binding for KCS. Please update it to the newer style
> with the "aspeed,lpc-io-reg" property.
>
>>> +};
>>> +
>>> +&kcs4 {
>>> + status = "okay";
>>> + kcs_addr = <0xca4>;
> as above.
Will modify.
next prev parent reply other threads:[~2021-05-26 5:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 6:47 [PATCH 1/1] ARM: dts: aspeed: Add Inspur NF5280M6 BMC machine guopingjn
2021-05-25 7:18 ` Joel Stanley
2021-05-25 7:27 ` Joel Stanley
2021-05-26 5:33 ` Ping Guo [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-24 1:27 guopingjn
2021-05-24 0:30 guopingjn
2021-05-24 2:40 ` Joel Stanley
2021-05-25 3:12 ` Ping Guo
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=4f3bb433-d050-a4bf-1797-933cdec77bda@gmail.com \
--to=guopingjn@gmail.com \
--cc=andrew@aj.id.au \
--cc=banht@inspur.com \
--cc=guoping@inspur.com \
--cc=joel@jms.id.au \
--cc=liuxiwei@inspur.com \
--cc=openbmc@lists.ozlabs.org \
--cc=wangxinglong@inspur.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.