From: Olof Johansson <olof@lixom.net>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, arm@kernel.org,
Christina Quast <cquast@hanoverdisplays.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] pinmux dts defines for am335x for v5.2
Date: Sun, 28 Apr 2019 12:39:02 -0700 [thread overview]
Message-ID: <20190428193902.7tj2yyfcolk44crm@localhost> (raw)
In-Reply-To: <pull-1555431314-599391@atomide.com>
On Tue, Apr 16, 2019 at 09:16:58AM -0700, Tony Lindgren wrote:
> From: "Tony Lindgren" <tony@atomide.com>
>
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
>
> Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.2/dt-am3-signed
>
> for you to fetch changes up to e5b258e53e58a3afd228bbef4d376c7a470cfa58:
>
> ARM: dts: am335x: wega: Replaced register offsets with defines (2019-04-15 08:26:28 -0700)
>
> ----------------------------------------------------------------
> Add am335x pinmux defines and start using them
>
> This series of changes adds a new pinmux instance defines for am335x,
> and a new AM33XX_PADCONF macro. And then the rest of the series updates
> the dts files to use it.
>
> The reasons for doing this is the pinmux configuration has been hard to
> use and read. And we need to do this for eventually for moving to use
> values.
>
> This change is done one machine at a time, and can be easily reverted
> as needed in case of unexpected trouble. The old macro is still working,
> and we're planning to keep it around until we eventually change to use
Merged, thanks!
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-04-28 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 16:16 [GIT PULL] pinmux dts defines for am335x for v5.2 Tony Lindgren
2019-04-28 19:39 ` Olof Johansson [this message]
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=20190428193902.7tj2yyfcolk44crm@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=cquast@hanoverdisplays.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 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).