From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Tomeu Vizoso
<tomeu.vizoso-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>,
Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Alexandre Courbot
<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Andrew Bresticker
<abrestic-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Subject: Re: [PATCH] ARM: tegra: Enable TPM on tegra124 nyan boards
Date: Thu, 14 May 2015 08:11:23 -0600 [thread overview]
Message-ID: <5554AD0B.1060106@wwwdotorg.org> (raw)
In-Reply-To: <CAAObsKCxFJA=6kyHM5rtpJMVRZRDbBO3KSn+QdNoOQz1rXCWTQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 05/14/2015 07:09 AM, Tomeu Vizoso wrote:
> On 13 May 2015 at 16:45, Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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)
>>
>>> 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.
>>
>>> 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.
>
> Are you sure? Just checked and what tegra-pinmux-scripts currently
> generates matches what is currently in the kernel, for both nyans.
My apologies; you're correct.
This patch to the kernel DTs includes changes that aren't generated by
either current tegra-pinmux-scripts, nor by tegra-pinmux-scripts with
Simon's "[pinmux scripts PATCH] Support TPM on nyan boards" applied.
Simon, can you double-check you didn't have any local patches to
tegra-pinmux-scripts applied when you generated the DT content for this
patch?
>> 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.
>
> From what Andrew (added to CC) said when these changes were discussed,
> it shouldn't matter as a fixed regulator is used to drive those pins
> high.
It looks like nyan-big and nyan-blaze configure these pins differently,
which may be incorrect if the boards are truly almost identical. Is that
expected? Nyan-big sets them both to open-drain but Nyan-blaze sets them
to push-pull. The pull-up enable is different too. Typically these pins
are open-drain, because there's often a current sensor chip on the USB
port power rail which asserts (pulls low in open-drain mode) these
signals to turn off the power when an over-current condition is
detected. Not all boards do this though, so the difference may be
perfectly expected; someone with access to the schematics would have to
check.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: Enable TPM on tegra124 nyan boards
Date: Thu, 14 May 2015 08:11:23 -0600 [thread overview]
Message-ID: <5554AD0B.1060106@wwwdotorg.org> (raw)
In-Reply-To: <CAAObsKCxFJA=6kyHM5rtpJMVRZRDbBO3KSn+QdNoOQz1rXCWTQ@mail.gmail.com>
On 05/14/2015 07:09 AM, Tomeu Vizoso wrote:
> On 13 May 2015 at 16: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)
>>
>>> 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.
>>
>>> 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.
>
> Are you sure? Just checked and what tegra-pinmux-scripts currently
> generates matches what is currently in the kernel, for both nyans.
My apologies; you're correct.
This patch to the kernel DTs includes changes that aren't generated by
either current tegra-pinmux-scripts, nor by tegra-pinmux-scripts with
Simon's "[pinmux scripts PATCH] Support TPM on nyan boards" applied.
Simon, can you double-check you didn't have any local patches to
tegra-pinmux-scripts applied when you generated the DT content for this
patch?
>> 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.
>
> From what Andrew (added to CC) said when these changes were discussed,
> it shouldn't matter as a fixed regulator is used to drive those pins
> high.
It looks like nyan-big and nyan-blaze configure these pins differently,
which may be incorrect if the boards are truly almost identical. Is that
expected? Nyan-big sets them both to open-drain but Nyan-blaze sets them
to push-pull. The pull-up enable is different too. Typically these pins
are open-drain, because there's often a current sensor chip on the USB
port power rail which asserts (pulls low in open-drain mode) these
signals to turn off the power when an over-current condition is
detected. Not all boards do this though, so the difference may be
perfectly expected; someone with access to the schematics would have to
check.
next prev parent reply other threads:[~2015-05-14 14:11 UTC|newest]
Thread overview: 20+ 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:13 ` Simon Glass
[not found] ` <1431526427-13340-1-git-send-email-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2015-05-13 14:45 ` Stephen Warren
2015-05-13 14:45 ` Stephen Warren
[not found] ` <5553637C.5010506-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2015-05-13 15:22 ` Simon Glass
2015-05-13 15:22 ` Simon Glass
[not found] ` <CAPnjgZ0ga6==w7YWQoeUtXRxUhCjQ+BHMJuCL7vbqN9WTLM2kQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-14 14:21 ` Stephen Warren
2015-05-14 14:21 ` Stephen Warren
2015-05-14 13:09 ` Tomeu Vizoso
2015-05-14 13:09 ` Tomeu Vizoso
[not found] ` <CAAObsKCxFJA=6kyHM5rtpJMVRZRDbBO3KSn+QdNoOQz1rXCWTQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-14 14:11 ` Stephen Warren [this message]
2015-05-14 14:11 ` Stephen Warren
[not found] ` <5554AD0B.1060106-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2015-05-14 14:28 ` Simon Glass
2015-05-14 14:28 ` Simon Glass
[not found] ` <CAPnjgZ2QrTu=D_AapTded+_NR1waZTbNoN8rCtHnTdd0OdnwLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-14 15:47 ` Stephen Warren
2015-05-14 15:47 ` Stephen Warren
[not found] ` <5554C399.4060807-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2015-05-14 16:30 ` Simon Glass
2015-05-14 16:30 ` Simon Glass
[not found] ` <CAPnjgZ1o-DvWjJqkEjwbxKxx_0L7p1k8Mc58boqjHQEGh=yj3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-03 23:06 ` 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=5554AD0B.1060106@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=abrestic-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=tomeu.vizoso-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.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 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.