From: Lucas Stach <dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Alexandre Courbot
<acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ARM kernel mailing list
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH v2] ARM: dts: tegra: correct Beaver pinmux
Date: Fri, 26 Feb 2016 20:36:24 +0100 [thread overview]
Message-ID: <1456515384.20487.2.camel@lynxeye.de> (raw)
In-Reply-To: <56D0A748.6060104-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Am Freitag, den 26.02.2016, 12:28 -0700 schrieb Stephen Warren:
> On 02/26/2016 12:18 PM, Lucas Stach wrote:
> > Update pinmux to get rid of invalid uses of the rsvd1 function,
> > which lead
> > to the mux settings on those pins to not be applied.
> >
> > Also add correct drive settings, derived from the Tegra3 TRM, for
Your comment from v1 is addressed here ^^^^^^^^^^^^^^^^^^^^^^^^
> > SDIO1,
> > which makes some more SD-cards work.
>
> I replied the following to V1, which I don't see resolved:
>
> > I think it would be worth mentioning in the commit description
> where
> > this[1] data came from.
>
> [1] that was in response to the addition of the sdio1 drive settings.
>
> Also, what is different in V2; is this actually V1 REPOST?
Other than the reworded commit message there is no change in v2.
Regards,
Lucas
WARNING: multiple messages have this Message-ID (diff)
From: dev@lynxeye.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: dts: tegra: correct Beaver pinmux
Date: Fri, 26 Feb 2016 20:36:24 +0100 [thread overview]
Message-ID: <1456515384.20487.2.camel@lynxeye.de> (raw)
In-Reply-To: <56D0A748.6060104@wwwdotorg.org>
Am Freitag, den 26.02.2016, 12:28 -0700 schrieb Stephen Warren:
> On 02/26/2016 12:18 PM, Lucas Stach wrote:
> > Update pinmux to get rid of invalid uses of the rsvd1 function,
> > which lead
> > to the mux settings on those pins to not be applied.
> >
> > Also add correct drive settings, derived from the Tegra3 TRM, for
Your comment from v1 is addressed here ?^^^^^^^^^^^^^^^^^^^^^^^^
> > SDIO1,
> > which makes some more SD-cards work.
>
> I replied the following to V1, which I don't see resolved:
>
> ?> I think it would be worth mentioning in the commit description
> where?
> ?> this[1] data came from.
>
> [1] that was in response to the addition of the sdio1 drive settings.
>
> Also, what is different in V2; is this actually V1 REPOST?
Other than the reworded commit message there is no change in v2.
Regards,
Lucas
next prev parent reply other threads:[~2016-02-26 19:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 19:18 [PATCH v2] ARM: dts: tegra: correct Beaver pinmux Lucas Stach
2016-02-26 19:18 ` Lucas Stach
[not found] ` <1456514310-27605-1-git-send-email-dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
2016-02-26 19:28 ` Stephen Warren
2016-02-26 19:28 ` Stephen Warren
[not found] ` <56D0A748.6060104-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2016-02-26 19:36 ` Lucas Stach [this message]
2016-02-26 19:36 ` Lucas Stach
[not found] ` <1456515384.20487.2.camel-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
2016-02-26 19:53 ` Stephen Warren
2016-02-26 19:53 ` Stephen Warren
2016-04-22 11:46 ` Thierry Reding
2016-04-22 11:46 ` Thierry Reding
[not found] ` <20160422114642.GD9047-EkSeR96xj6Pcmrwk2tT4+A@public.gmane.org>
2016-04-22 18:00 ` Stephen Warren
2016-04-22 18:00 ` Stephen Warren
2016-04-21 18:16 ` Lucas Stach
2016-04-21 18:16 ` Lucas Stach
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=1456515384.20487.2.camel@lynxeye.de \
--to=dev-8ppwabl0hbeelga04laivw@public.gmane.org \
--cc=acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@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.