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 v2 0/3] ARM: dts: dra7-evm: pinmuxing updates
Date: Thu, 5 Jan 2017 08:55:55 -0800	[thread overview]
Message-ID: <20170105165555.GH4310@atomide.com> (raw)
In-Reply-To: <cover.1481628266.git.nsekhar@ti.com>

* Sekhar Nori <nsekhar@ti.com> [161213 03:30]:
> Hi,
> 
> This patch series drops most of the pinmuxing from dra7-evm
> to satisfy erratum i869 and adds missing eMMC and SD card pinmuxing.
> 
> The patches apply to latest linux-next. Tested on DRA74x EVM Rev H
> using U-Boot 2016.11. Boot tested using NFS and basic testing carried
> out on SD card, eMMC, Audio capture and playback.
> 
> NAND on DRA72 EVM is already unusable due to a similar patch. A patch
> included here disables the GPMC node.
> 
> v1 -> v2:
> - Add a patch to disable GPMC node on DRA72x EVM
> - Disable GPMC node on DRA74x EVM
> 
> Kishon Vijay Abraham I (1):
>   ARM: dts: dra7-evm: add pinmux configuration for mmc1/2
> 
> Sekhar Nori (2):
>   ARM: dts: dra7-evm: Remove pinmux configurations for erratum i869
>   ARM: dts: dra72-evm: drop NAND support
> 
>  arch/arm/boot/dts/dra7-evm.dts          | 282 ++++----------------------------
>  arch/arm/boot/dts/dra72-evm-common.dtsi |   7 +-
>  2 files changed, 35 insertions(+), 254 deletions(-)

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

Tony

      parent reply	other threads:[~2017-01-05 16:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13 11:29 [PATCH v2 0/3] ARM: dts: dra7-evm: pinmuxing updates Sekhar Nori
2016-12-13 11:29 ` [PATCH v2 1/3] ARM: dts: dra7-evm: Remove pinmux configurations for erratum i869 Sekhar Nori
2016-12-13 11:29 ` [PATCH v2 2/3] ARM: dts: dra7-evm: add pinmux configuration for mmc1/2 Sekhar Nori
2016-12-13 11:29 ` [PATCH v2 3/3] ARM: dts: dra72-evm: drop NAND support Sekhar Nori
2017-01-05 16:55 ` 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=20170105165555.GH4310@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).