From: sjg@chromium.org (Simon Glass)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: Enable TPM on tegra124 nyan boards
Date: Wed, 13 May 2015 09:22:53 -0600 [thread overview]
Message-ID: <CAPnjgZ0ga6==w7YWQoeUtXRxUhCjQ+BHMJuCL7vbqN9WTLM2kQ@mail.gmail.com> (raw)
In-Reply-To: <5553637C.5010506@wwwdotorg.org>
Hi Stephen,
On 13 May 2015 at 08:45, Stephen Warren <swarren@wwwdotorg.org> wrote:
> On 05/13/2015 08:13 AM, Simon Glass wrote:
>>
>> Regenerate the pinmux from the latest tegra-pinmux-scripts.
>
>
> (Dropping most CCs; DT maintainers and lists generally don't get CC'd on
> simple DT content changes but rather on schema adds/changes and perhaps
> major DT content changes depending on context)
OK, I'll try to remember to use patman -m.
>
>> diff --git a/arch/arm/boot/dts/tegra124-nyan-big.dts
>> b/arch/arm/boot/dts/tegra124-nyan-big.dts
>
>
>> pinctrl-names = "default";
>> pinctrl-0 = <&pinmux_default>;
>>
>> - pinmux_default: common {
>> + state_default: pinmux {
>
>
> This change will break compilation, since it changes the label name, yet the
> old name is still referenced in pinctrl-0 above. Same applies in the other
> file too.
Yes I saw that, but assumed that the tool was doing the right thing.
Is the tool wrong?
>
>> diff --git a/arch/arm/boot/dts/tegra124-nyan-blaze.dts
>> b/arch/arm/boot/dts/tegra124-nyan-blaze.dts
>
>
>> @@ -437,18 +437,18 @@
>> usb_vbus_en0_pn4 {
>> nvidia,pins = "usb_vbus_en0_pn4";
>> nvidia,function = "usb";
>> - nvidia,pull = <TEGRA_PIN_PULL_UP>;
>> + nvidia,pull = <TEGRA_PIN_PULL_NONE>;
>> nvidia,tristate = <TEGRA_PIN_DISABLE>;
>> nvidia,enable-input = <TEGRA_PIN_ENABLE>;
>> - nvidia,open-drain = <TEGRA_PIN_DISABLE>;
>> + nvidia,open-drain = <TEGRA_PIN_ENABLE>;
>> };
>> usb_vbus_en1_pn5 {
>> nvidia,pins = "usb_vbus_en1_pn5";
>> nvidia,function = "usb";
>> - nvidia,pull = <TEGRA_PIN_PULL_UP>;
>> + nvidia,pull = <TEGRA_PIN_PULL_NONE>;
>> nvidia,tristate = <TEGRA_PIN_DISABLE>;
>> nvidia,enable-input = <TEGRA_PIN_ENABLE>;
>> - nvidia,open-drain = <TEGRA_PIN_DISABLE>;
>> + nvidia,open-drain = <TEGRA_PIN_ENABLE>;
>> };
>
>
> Tomeu, can you comment on those changes? Evidently the pinmux configuration
> that's you added to the kernel doesn't exactly match the pinmux
> configuration that you added to tegra-pinmux-scripts. Is the change above
> correct, or do we need to propagate this change from the kernel DT into
> tegra-pinmux-scripts, and hence also into the U-Boot pinmux setup table?
>
> My understanding of how these pins are generally used is that open-drain is
> likely correct. I have no idea whether Tegra should supply the pullup for
> these pins, or whether the board has a pullup resistor in which case Tegra
> doesn't need to pull up.
Regards,
Simon
next prev parent reply other threads:[~2015-05-13 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 14:13 [PATCH] ARM: tegra: Enable TPM on tegra124 nyan boards Simon Glass
2015-05-13 14:45 ` Stephen Warren
2015-05-13 15:22 ` Simon Glass [this message]
2015-05-14 14:21 ` Stephen Warren
2015-05-14 13:09 ` Tomeu Vizoso
2015-05-14 14:11 ` Stephen Warren
2015-05-14 14:28 ` Simon Glass
2015-05-14 15:47 ` Stephen Warren
2015-05-14 16:30 ` Simon Glass
2015-07-03 23:06 ` Simon Glass
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='CAPnjgZ0ga6==w7YWQoeUtXRxUhCjQ+BHMJuCL7vbqN9WTLM2kQ@mail.gmail.com' \
--to=sjg@chromium.org \
--cc=linux-arm-kernel@lists.infradead.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 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).