linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: dts: Use IOPAD pinmux for IGEP boards
Date: Tue, 20 Oct 2015 09:26:09 -0700	[thread overview]
Message-ID: <20151020162608.GI3078@atomide.com> (raw)
In-Reply-To: <1445268861-11857-1-git-send-email-javier@osg.samsung.com>

* Javier Martinez Canillas <javier@osg.samsung.com> [151019 08:39]:
> Hello,
> 
> This series use the IOPAD pinmux macros for the remaining IGEP boards that
> still used the register offset instead of the physical address using these
> macros so the DTS matches what is in the Technical Reference Manual.
> 
> The changes are only cosmetic since they make the DTS easier to read but
> does not change functionality. I built tested and compared the binary DTB
> MD5 checksum and both matches before and after the series applied:
> 
> Before
> 
> d7a56205bdc54365d49d9a90dfe3fafb  am335x-base0033.dtb
> fa272fcdee65d7bf4c03bd5a6c5ec4fd  omap3-igep0020.dtb
> ba65bf74d8c6ea8e7bd8face17179e6e  omap3-igep0020-rev-f.dtb
> 
> After
> 
> d7a56205bdc54365d49d9a90dfe3fafb  am335x-base0033.dtb
> fa272fcdee65d7bf4c03bd5a6c5ec4fd  omap3-igep0020.dtb
> ba65bf74d8c6ea8e7bd8face17179e6e  omap3-igep0020-rev-f.dtb

Good idea to test the dtb checksums :)

Applying all into omap-for-v4.4/dt thanks.

Tony

  parent reply	other threads:[~2015-10-20 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19 15:34 [PATCH 0/3] ARM: dts: Use IOPAD pinmux for IGEP boards Javier Martinez Canillas
2015-10-19 15:34 ` [PATCH 1/3] ARM: dts: omap3-igep0020: Use IOPAD pinmux macro Javier Martinez Canillas
2015-10-19 15:34 ` [PATCH 2/3] ARM: dts: am335x-igep0033: " Javier Martinez Canillas
2015-10-19 15:34 ` [PATCH 3/3] ARM: dts: am335x-base0033: " Javier Martinez Canillas
2015-10-20 16:26 ` Tony Lindgren [this message]
2015-10-20 17:26   ` [PATCH 0/3] ARM: dts: Use IOPAD pinmux for IGEP boards Javier Martinez Canillas
2015-10-20 17:32     ` Tony Lindgren

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=20151020162608.GI3078@atomide.com \
    --to=tony@atomide.com \
    --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).