From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Date: Sun, 02 Nov 2014 20:19:37 +0100 [thread overview]
Message-ID: <545683C9.6000101@gmail.com> (raw)
In-Reply-To: <20141102190333.GV3698@titan.lakedaemon.net>
On 02.11.2014 20:03, Jason Cooper wrote:
> On Sat, Nov 01, 2014 at 11:48:33PM +0100, Sebastian Hesselbarth wrote:
>> On 01.11.2014 23:36, Jason Cooper wrote:
>>> On Fri, Sep 19, 2014 at 10:14:36PM +0200, Sebastian Hesselbarth wrote:
>>>> 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 lost track of this thread, are you resending? Did Benoit get a
>>> successful test run?
>>
>> Looks like there was this A0 stepping thing, but basically yes
>>
>> http://www.spinics.net/lists/devicetree/msg53364.html
>>
>> I have just rebased it on top of v3.18-rc1, feel free to pick them
>> up from
>>
>> git://git.infradead.org/users/hesselba/linux-berlin.git devel/mvebu/ix4-300d
>> git://git.infradead.org/users/hesselba/linux-berlin.git
>
> Ahh, that's right. Do you still use the github repo? I hadn't added
> your infradead as a remote yet.
Usually, I use github for mvebu and infradead for berlin. But this time
I was too lazy to either boot-up the other laptop or clone the github
repo ;)
> At any rate, I cherry-picked them and added Benoit's Tested-by's. So if
> you had this branch in -next, please remove it before tonight's run.
I _did not_ put it into any -next branch. It's mvebu and that is your
git tree, I only put berlin patches into -next ;)
> Applied to mvebu/dt.
Thanks for having an eye on this patches, I almost forgot about them.
Sebastian
prev parent reply other threads:[~2014-11-02 19:19 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
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 [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=545683C9.6000101@gmail.com \
--to=sebastian.hesselbarth@gmail.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).