From: Tony Lindgren <tony@atomide.com>
To: "Andrew F. Davis" <afd@ti.com>
Cc: Javier Martinez Canillas <javier@osg.samsung.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-gpio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 00/39] ARM: dts: Convert OMAP boards to use IOPAD pinmux macros
Date: Mon, 30 Nov 2015 08:49:26 -0800 [thread overview]
Message-ID: <20151130164925.GD2517@atomide.com> (raw)
In-Reply-To: <564A0681.6010205@ti.com>
* Andrew F. Davis <afd@ti.com> [151116 08:39]:
> On 11/13/2015 08:47 AM, Tony Lindgren wrote:
> >* Javier Martinez Canillas <javier@osg.samsung.com> [151112 20:55]:
> >>Hello Tony,
> >>
> >>This series converts all the remaining OMAP boards that didn't use the
> >>IOPAD macros to specify the padconf register addresses. The only board
> >>that I left was arch/arm/boot/dts/am335x-boneblack.dts because Andrew
> >>already posted a patch for that DTS [0].
> >>
> >>I built tested all the DTBs that are build by omap2plus_defconfig and
> >>the md5 checksum was the same before and after the patches so there's
> >>no functional change and is only to make the DTS more readable.
> >
> >Yes great. Being able to compare the register against the documentation
> >helps quite a bit. I plan on applying this series before anything else
> >after -rc1 as it may require other patches to be rebased.
> >
> >>Patch #1 should be acked by the pinctrl maintainer and picked through
> >>the linux-omap tree to maintain bisectability.
> >>
> >>[0]: https://lkml.org/lkml/2015/10/24/114
> >
>
> v3 of my little contribution also out when you pull:
> https://lkml.org/lkml/2015/11/13/480
Applying that one too into omap-for-v4.5/dt thanks.
Tony
prev parent reply other threads:[~2015-11-30 16:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 4:53 [PATCH 00/39] ARM: dts: Convert OMAP boards to use IOPAD pinmux macros Javier Martinez Canillas
2015-11-13 4:53 ` [PATCH 01/39] pinctrl: Move am4372 and dra7 macros to the the SoC header files Javier Martinez Canillas
2015-11-17 13:47 ` Linus Walleij
2015-11-17 13:50 ` Javier Martinez Canillas
2015-11-19 0:23 ` Tony Lindgren
2015-11-25 18:39 ` Tony Lindgren
2015-11-30 16:46 ` Tony Lindgren
2015-12-10 16:48 ` Linus Walleij
2015-11-13 14:47 ` [PATCH 00/39] ARM: dts: Convert OMAP boards to use IOPAD pinmux macros Tony Lindgren
2015-11-16 16:38 ` Andrew F. Davis
2015-11-30 16:49 ` Tony Lindgren [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=20151130164925.GD2517@atomide.com \
--to=tony@atomide.com \
--cc=afd@ti.com \
--cc=javier@osg.samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.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).