linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: Benoit Masson <benoitm@perenite.com>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Gregory Clement <gregory.clement@free-electrons.com>,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Benoit Masson <yahoo@perenite.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Date: Fri, 3 Oct 2014 10:11:02 -0400	[thread overview]
Message-ID: <20141003141102.GJ3895@titan.lakedaemon.net> (raw)
In-Reply-To: <-7443282711873112734@unknownmsgid>

Benoit,

On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote:
> > Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> a écrit :
> > this is a patch set preparing barebox support for ix4-300d. As usual,
> > I stumbled upon a few nice-to-haves before actually touching ix4-300d
> > dts. As it is a mach-mvebu thing, I just added the related mailing
> > lists instead of each of the DT maintainers.
> >
> > First 5 patches consolidate SoC-specific pinctrl nodes to one common
> > node in armada-xp.dtsi, compatible overwrites for each SoC, and node
> > alias usage for each board. Also, ge{0,1} pinctrl settings are moved
> > to the common node from one board specific node.
> >
> > Last 3 patches then use that ge{0,1} pinctrl settings on ix4-300d which
> > is vital for bootloader init. During exploration of ix4-300d, I also
> > found a i2c eeprom that has not been added to the dts, yet. Finally,
> > there is only one 74hc595 on ix4 mainboard while dts property is set
> > for two.
> >
> > I cannot recall in detail what is on that eeprom, but IIRC it is nothing
> > important. Some reg,addr pairs for some init stuff that should have
> > already been done by stock u-boot. Anyway, adding the node will do no
> > harm.
> >
> > Patches are based on v3.17-rc1 and intended for v3.18 but I am not in
> > a hurry. I only compile tested this, so a formal Tested-by from Benoit
> > for the ix4 and any other Armada XP board would be great.
> 
> I'm not sure what to test since I only receive some patch from the
> series of 8. Should I get all 8 or only those you sent me. I'll be
> able to test during next week.

Did you ever get a chance to test this series?

thx,

Jason.

  reply	other threads:[~2014-10-03 14:11 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 20:14 [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes Sebastian Hesselbarth
2014-09-19 20:14 ` [PATCH 1/8] ARM: mvebu: armada-xp: Consolidate pinctrl node Sebastian Hesselbarth
2014-09-19 20:39   ` Thomas Petazzoni
2014-09-19 20:14 ` [PATCH 2/8] ARM: mvebu: armada-xp: Add node alias to pinctrl and add base address Sebastian Hesselbarth
2014-09-19 20:40   ` Thomas Petazzoni
2014-09-19 20:14 ` [PATCH 3/8] ARM: mvebu: armada-xp: Use pinctrl node alias Sebastian Hesselbarth
2014-09-19 20:42   ` Thomas Petazzoni
2014-09-19 20:14 ` [PATCH 4/8] ARM: mvebu: armada-xp: Move GE0/1 pinctrl settings for RGMII Sebastian Hesselbarth
2014-09-19 20:14 ` [PATCH 5/8] ARM: mvebu: armada-xp: Add GE0 pinctrl settings for GMII Sebastian Hesselbarth
2014-09-19 20:14 ` [PATCH 6/8] ARM: mvebu: armada-xp: Add RGMII pinctrl to Lenovo ix4-300d Sebastian Hesselbarth
2014-09-19 20:14 ` [PATCH 7/8] ARM: mvebu: armada-xp: Add I2C eeprom on " Sebastian Hesselbarth
2014-09-20  9:55   ` Sebastian Hesselbarth
2014-09-19 20:14 ` [PATCH 8/8] ARM: mvebu: armada-xp: Fix 74hc595 count for " Sebastian Hesselbarth
2014-09-21 14:11 ` [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes Benoit Masson
2014-10-03 14:11   ` Jason Cooper [this message]
2014-10-03 15:06     ` Sebastian Hesselbarth
2014-10-03 15:29       ` Benoit Masson
2014-10-03 15:41         ` Sebastian Hesselbarth
2014-10-05 23:11           ` Benoit Masson
2014-10-06  7:47             ` Sebastian Hesselbarth
2014-10-06  8:36               ` Gregory CLEMENT
     [not found]               ` <BAB12F2D-0142-4362-BA04-59D8E6B16AAE@perenite.com>
2014-10-06  9:14                 ` Gregory CLEMENT
2014-10-06 16:13             ` Sebastian Hesselbarth
2014-10-15  0:53               ` Benoit Masson
     [not found]                 ` <1CDF8F6B-42FF-4D6A-B52F-6DB270F2673C@perenite.com>
2014-10-15 14:41                   ` Andrew Lunn
2014-10-15 15:35                     ` Benoit Masson
2014-10-15 14:42                 ` Jason Cooper
2014-10-15 14:49                   ` Sebastian Hesselbarth
2014-10-15 14:55                     ` Andrew Lunn
2014-10-15 15:30                       ` Jason Cooper
2014-10-15 15:56                         ` Jason Cooper
2014-11-01 22:59                 ` Jason Cooper
2014-11-01 22:36 ` Jason Cooper
2014-11-01 22:48   ` Sebastian Hesselbarth
2014-11-02 19:03     ` Jason Cooper
2014-11-02 19:19       ` Sebastian Hesselbarth

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=20141003141102.GJ3895@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=andrew@lunn.ch \
    --cc=benoitm@perenite.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=yahoo@perenite.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).