Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
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.
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.
Applied to mvebu/dt.
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
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.
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.
Applied to mvebu/dt.
thx,
Jason.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
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
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On Wed, Oct 15, 2014 at 02:53:02AM +0200, Benoit Masson wrote: > > Le 6 oct. 2014 à 18:13, Sebastian Hesselbarth > a écrit : > > > On 10/06/2014 01:11 AM, Benoit Masson wrote: > >> Le 3 oct. 2014 à 17:41, Sebastian Hesselbarth > >> a écrit : > >>> On 10/03/2014 05:29 PM, Benoit Masson wrote: > Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth > a écrit : > > On 10/03/2014 04:11 PM, Jason Cooper wrote: > >> On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote: > Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth > a écrit : > >>> [...] > 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? > > > > Uhm, I never prepared a branch for Benoit to test. I have pushed the > > patches with Thomas Acked-by's and renamed eeprom node based on > > v3.17-rc1 to > > > > https://github.com/shesselba/linux-dove.git devel/mvebu-ix4 > > > >>> [...] > >> Maybe I missed something ? is this branch you sent me a bare fork > >> from mainline 3.17 ? does it includes the armada XP step A0 patch ? > > > > Benoit, > > > Hi, > > I prepared more branches with the series > > - on top of v3.17 release: > > https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_v3.17 > > > > - on top of next-20141003 (i.e. what will become v3.18-rc1): > > https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_next-20141003 > > > > It would be great, if you can test in this order: > > - vanilla v3.17 > > - mvebu-ix4_v3.17 > > - mvebu-ix4_next-20141003 > > > All the 3 branch works WHEN APPLYING A0 patch (below), with both my > custom kernel config and the arch/arm/configs/mvebu_v7_defconfig Can I count this as a Tested-by? > The reason why it didn't worked last time was that apparently the A0 > patch (copied) below was not merged into 3.17 :( Yep, sorry. Life got the best of me. The pull request is now sent. > This means that ix4-300d support is broken on 3.17 because of the A0 > stepping patch not merged. Not a problem. It's flagged for stable v3.12 and up. thx, Jason. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
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
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Sebastian,
On Fri, Sep 19, 2014 at 10:14:36PM +0200, Sebastian Hesselbarth wrote:
> Guys,
>
> 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?
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Sebastian,
On Fri, Sep 19, 2014 at 10:14:36PM +0200, Sebastian Hesselbarth wrote:
Guys,
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?
thx,
Jason.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
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
Sebastian
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On Wed, Oct 15, 2014 at 02:53:02AM +0200, Benoit Masson wrote: Le 6 oct. 2014 à 18:13, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : On 10/06/2014 01:11 AM, Benoit Masson wrote: Le 3 oct. 2014 à 17:41, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : On 10/03/2014 05:29 PM, Benoit Masson wrote: Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : On 10/03/2014 04:11 PM, Jason Cooper wrote: On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote: Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : [...] 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? Uhm, I never prepared a branch for Benoit to test. I have pushed the patches with Thomas Acked-by's and renamed eeprom node based on v3.17-rc1 to https://github.com/shesselba/linux-dove.git devel/mvebu-ix4 [...] Maybe I missed something ? is this branch you sent me a bare fork from mainline 3.17 ? does it includes the armada XP step A0 patch ? Benoit, Hi, I prepared more branches with the series - on top of v3.17 release: https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_v3.17 - on top of next-20141003 (i.e. what will become v3.18-rc1): https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_next-20141003 It would be great, if you can test in this order: - vanilla v3.17 - mvebu-ix4_v3.17 - mvebu-ix4_next-20141003 All the 3 branch works WHEN APPLYING A0 patch (below), with both my custom kernel config and the arch/arm/configs/mvebu_v7_defconfig Can I count this as a Tested-by? The reason why it didn't worked last time was that apparently the A0 patch (copied) below was not merged into 3.17 :( Yep, sorry. Life got the best of me. The pull request is now sent. This means that ix4-300d support is broken on 3.17 because of the A0 stepping patch not merged. Not a problem. It's flagged for stable v3.12 and up. thx, Jason. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On Wed, Oct 15, 2014 at 11:30:49AM -0400, Jason Cooper wrote: > On Wed, Oct 15, 2014 at 04:55:39PM +0200, Andrew Lunn wrote: > > > >Do you have a link to an email thread or the patch Subject line? I can > > > >confirm it's missing from mvebu/fixes... > > > > > > http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275487.html > > > > > > But you and Andrew should check what Arnd suggested. IIRC, there > > > was also an appropriate follow-up patch discussion started by > > > Andrew. > > > > There was a lot of back and forth with Arnd. In the end, he gave up > > arguing because too many voices did not like his solution. So my > > original version stands. > > Yes, this appears to have been a mistake on my part. In the > conversation regarding patch #2 of V2, you said you were going to work > on implementing something and would report back. I applied that to the > whole series instead of just to the second patch. At any rate, applied > to mvebu/fixes now. > > > However, the patch at the end of > > > > http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275528.html > > > > is useful, and it would be nice if it could be merged as well. > > I'll take a look. I'd still like to see that note captured in the binding doc. Did I miss another patch somewhere? thx, Jason. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Le 15 oct. 2014 à 16:41, Andrew Lunn a écrit : >>> All the 3 branch works WHEN APPLYING A0 patch (below), with both my custom >>> kernel config and the arch/arm/configs/mvebu_v7_defconfig >> Just one thing though, one of my cron behavior change with 3.17, when I use >> the cmd "/sbin/hwclock --adjust -f /dev/rtc1" I get this new error I never >> had before: >> "hwclock: select() to /dev/rtc1 to wait for clock tick timed out: Success" >> >> where rtc1 if the i2c rtc connected to the i2C bus, can this be related to >> the i2c patch that would slow down i2c operation or somthing ? > > Hi Benoit > > It won't fix your problem, but if the built in RTC is not usable, it > would be good to disable it in the .dts file. The i2c RTC will then > become RTC0. > > > The actual "error" message is odd: > "hwclock: select() to /dev/rtc1 to wait for clock tick timed out: Success" > Yes this is the wired thing is that everything works, even getting the date via "cat /sys/class/i2c-adapter/i2c-0/0-0051/rtc/rtc1/time" is ok reading the rtc driver code it seems this message is shown when multiple resources try to access shared rtc... but why now and not before ? So I was wondering if the i2c_quirk() applied by the batch has any effect with this ? Anyhow I'll handle the message for now and see if there are performance impact on this... Benoit > Success means it actually worked, not an error. Does the RTC contain > the correct time afterwards? > >Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On Wed, Oct 15, 2014 at 04:55:39PM +0200, Andrew Lunn wrote: > > >Do you have a link to an email thread or the patch Subject line? I can > > >confirm it's missing from mvebu/fixes... > > > > http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275487.html > > > > But you and Andrew should check what Arnd suggested. IIRC, there > > was also an appropriate follow-up patch discussion started by > > Andrew. > > There was a lot of back and forth with Arnd. In the end, he gave up > arguing because too many voices did not like his solution. So my > original version stands. Yes, this appears to have been a mistake on my part. In the conversation regarding patch #2 of V2, you said you were going to work on implementing something and would report back. I applied that to the whole series instead of just to the second patch. At any rate, applied to mvebu/fixes now. > However, the patch at the end of > > http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275528.html > > is useful, and it would be nice if it could be merged as well. I'll take a look. thx, Jason. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
> >Do you have a link to an email thread or the patch Subject line? I can > >confirm it's missing from mvebu/fixes... > > http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275487.html > > But you and Andrew should check what Arnd suggested. IIRC, there > was also an appropriate follow-up patch discussion started by > Andrew. There was a lot of back and forth with Arnd. In the end, he gave up arguing because too many voices did not like his solution. So my original version stands. However, the patch at the end of http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275528.html is useful, and it would be nice if it could be merged as well. Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On 10/15/2014 04:42 PM, Jason Cooper wrote: On Wed, Oct 15, 2014 at 02:53:02AM +0200, Benoit Masson wrote: Le 6 oct. 2014 à 18:13, Sebastian Hesselbarth a écrit : I prepared more branches with the series - on top of v3.17 release: https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_v3.17 - on top of next-20141003 (i.e. what will become v3.18-rc1): https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_next-20141003 It would be great, if you can test in this order: - vanilla v3.17 - mvebu-ix4_v3.17 - mvebu-ix4_next-20141003 All the 3 branch works WHEN APPLYING A0 patch (below), with both my custom kernel config and the arch/arm/configs/mvebu_v7_defconfig The reason why it didn't worked last time was that apparently the A0 patch (copied) below was not merged into 3.17 :( This means that ix4-300d support is broken on 3.17 because of the A0 stepping patch not merged. Do you have a link to an email thread or the patch Subject line? I can confirm it's missing from mvebu/fixes... http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275487.html But you and Andrew should check what Arnd suggested. IIRC, there was also an appropriate follow-up patch discussion started by Andrew. Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On Wed, Oct 15, 2014 at 02:53:02AM +0200, Benoit Masson wrote:
>
> Le 6 oct. 2014 à 18:13, Sebastian Hesselbarth
> a écrit :
>
> > On 10/06/2014 01:11 AM, Benoit Masson wrote:
> >> Le 3 oct. 2014 à 17:41, Sebastian Hesselbarth
> >> a écrit :
> >>> On 10/03/2014 05:29 PM, Benoit Masson wrote:
> Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth
> a écrit :
> > On 10/03/2014 04:11 PM, Jason Cooper wrote:
> >> On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote:
> Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth
> a écrit :
> >>> [...]
> 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?
> >
> > Uhm, I never prepared a branch for Benoit to test. I have pushed the
> > patches with Thomas Acked-by's and renamed eeprom node based on
> > v3.17-rc1 to
> >
> > https://github.com/shesselba/linux-dove.git devel/mvebu-ix4
> >
> >>> [...]
> >> Maybe I missed something ? is this branch you sent me a bare fork
> >> from mainline 3.17 ? does it includes the armada XP step A0 patch ?
> >
> > Benoit,
> >
> Hi,
> > I prepared more branches with the series
> > - on top of v3.17 release:
> > https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_v3.17
> >
> > - on top of next-20141003 (i.e. what will become v3.18-rc1):
> > https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_next-20141003
> >
> > It would be great, if you can test in this order:
> > - vanilla v3.17
> > - mvebu-ix4_v3.17
> > - mvebu-ix4_next-20141003
> >
> All the 3 branch works WHEN APPLYING A0 patch (below), with both my custom
> kernel config and the arch/arm/configs/mvebu_v7_defconfig
>
> The reason why it didn't worked last time was that apparently the A0 patch
> (copied) below was not merged into 3.17 :(
>
> This means that ix4-300d support is broken on 3.17 because of the A0 stepping
> patch not merged.
Do you have a link to an email thread or the patch Subject line? I can
confirm it's missing from mvebu/fixes...
thx,
Jason.
> patch (from Andrew Lunn Acked-by Gregory Clement is missing:
>
> ---
> arch/arm/mach-mvebu/board-v7.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-mvebu/board-v7.c b/arch/arm/mach-mvebu/board-v7.c
> index b2524d6..b1e148d 100644
> --- a/arch/arm/mach-mvebu/board-v7.c
> +++ b/arch/arm/mach-mvebu/board-v7.c
> @@ -174,7 +174,7 @@ static void __init thermal_quirk(void)
>
> static void __init mvebu_dt_init(void)
> {
> - if (of_machine_is_compatible("plathome,openblocks-ax3-4"))
> + if (of_machine_is_compatible("marvell,armadaxp"))
> i2c_quirk();
> if (of_machine_is_compatible("marvell,a375-db")) {
> external_abort_quirk();
> --
> 1.9.1
> > If any branch fails, you can stop and please report back.
> >
> > I also have the ix4 but I need more time for a full setup like you
> > already seem to have ready. Again, there is no hurry, take your time.
> >
> > Thanks!
> >
> > Sebastian
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
> > All the 3 branch works WHEN APPLYING A0 patch (below), with both my custom > > kernel config and the arch/arm/configs/mvebu_v7_defconfig > Just one thing though, one of my cron behavior change with 3.17, when I use > the cmd "/sbin/hwclock --adjust -f /dev/rtc1" I get this new error I never > had before: > "hwclock: select() to /dev/rtc1 to wait for clock tick timed out: Success" > > where rtc1 if the i2c rtc connected to the i2C bus, can this be related to > the i2c patch that would slow down i2c operation or somthing ? Hi Benoit It won't fix your problem, but if the built in RTC is not usable, it would be good to disable it in the .dts file. The i2c RTC will then become RTC0. The actual "error" message is odd: "hwclock: select() to /dev/rtc1 to wait for clock tick timed out: Success" Success means it actually worked, not an error. Does the RTC contain the correct time afterwards? Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
All the 3 branch works WHEN APPLYING A0 patch (below), with both my custom kernel config and the arch/arm/configs/mvebu_v7_defconfig Just one thing though, one of my cron behavior change with 3.17, when I use the cmd /sbin/hwclock --adjust -f /dev/rtc1 I get this new error I never had before: hwclock: select() to /dev/rtc1 to wait for clock tick timed out: Success where rtc1 if the i2c rtc connected to the i2C bus, can this be related to the i2c patch that would slow down i2c operation or somthing ? Hi Benoit It won't fix your problem, but if the built in RTC is not usable, it would be good to disable it in the .dts file. The i2c RTC will then become RTC0. The actual error message is odd: hwclock: select() to /dev/rtc1 to wait for clock tick timed out: Success Success means it actually worked, not an error. Does the RTC contain the correct time afterwards? Andrew -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On Wed, Oct 15, 2014 at 02:53:02AM +0200, Benoit Masson wrote:
Le 6 oct. 2014 à 18:13, Sebastian Hesselbarth
sebastian.hesselba...@gmail.com a écrit :
On 10/06/2014 01:11 AM, Benoit Masson wrote:
Le 3 oct. 2014 à 17:41, Sebastian Hesselbarth
sebastian.hesselba...@gmail.com a écrit :
On 10/03/2014 05:29 PM, Benoit Masson wrote:
Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth
sebastian.hesselba...@gmail.com a écrit :
On 10/03/2014 04:11 PM, Jason Cooper wrote:
On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote:
Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth
sebastian.hesselba...@gmail.com a écrit :
[...]
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?
Uhm, I never prepared a branch for Benoit to test. I have pushed the
patches with Thomas Acked-by's and renamed eeprom node based on
v3.17-rc1 to
https://github.com/shesselba/linux-dove.git devel/mvebu-ix4
[...]
Maybe I missed something ? is this branch you sent me a bare fork
from mainline 3.17 ? does it includes the armada XP step A0 patch ?
Benoit,
Hi,
I prepared more branches with the series
- on top of v3.17 release:
https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_v3.17
- on top of next-20141003 (i.e. what will become v3.18-rc1):
https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_next-20141003
It would be great, if you can test in this order:
- vanilla v3.17
- mvebu-ix4_v3.17
- mvebu-ix4_next-20141003
All the 3 branch works WHEN APPLYING A0 patch (below), with both my custom
kernel config and the arch/arm/configs/mvebu_v7_defconfig
The reason why it didn't worked last time was that apparently the A0 patch
(copied) below was not merged into 3.17 :(
This means that ix4-300d support is broken on 3.17 because of the A0 stepping
patch not merged.
Do you have a link to an email thread or the patch Subject line? I can
confirm it's missing from mvebu/fixes...
thx,
Jason.
patch (from Andrew Lunn Acked-by Gregory Clement is missing:
---
arch/arm/mach-mvebu/board-v7.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-mvebu/board-v7.c b/arch/arm/mach-mvebu/board-v7.c
index b2524d6..b1e148d 100644
--- a/arch/arm/mach-mvebu/board-v7.c
+++ b/arch/arm/mach-mvebu/board-v7.c
@@ -174,7 +174,7 @@ static void __init thermal_quirk(void)
static void __init mvebu_dt_init(void)
{
- if (of_machine_is_compatible(plathome,openblocks-ax3-4))
+ if (of_machine_is_compatible(marvell,armadaxp))
i2c_quirk();
if (of_machine_is_compatible(marvell,a375-db)) {
external_abort_quirk();
--
1.9.1
If any branch fails, you can stop and please report back.
I also have the ix4 but I need more time for a full setup like you
already seem to have ready. Again, there is no hurry, take your time.
Thanks!
Sebastian
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On 10/15/2014 04:42 PM, Jason Cooper wrote: On Wed, Oct 15, 2014 at 02:53:02AM +0200, Benoit Masson wrote: Le 6 oct. 2014 à 18:13, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : I prepared more branches with the series - on top of v3.17 release: https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_v3.17 - on top of next-20141003 (i.e. what will become v3.18-rc1): https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_next-20141003 It would be great, if you can test in this order: - vanilla v3.17 - mvebu-ix4_v3.17 - mvebu-ix4_next-20141003 All the 3 branch works WHEN APPLYING A0 patch (below), with both my custom kernel config and the arch/arm/configs/mvebu_v7_defconfig The reason why it didn't worked last time was that apparently the A0 patch (copied) below was not merged into 3.17 :( This means that ix4-300d support is broken on 3.17 because of the A0 stepping patch not merged. Do you have a link to an email thread or the patch Subject line? I can confirm it's missing from mvebu/fixes... http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275487.html But you and Andrew should check what Arnd suggested. IIRC, there was also an appropriate follow-up patch discussion started by Andrew. Sebastian -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Do you have a link to an email thread or the patch Subject line? I can confirm it's missing from mvebu/fixes... http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275487.html But you and Andrew should check what Arnd suggested. IIRC, there was also an appropriate follow-up patch discussion started by Andrew. There was a lot of back and forth with Arnd. In the end, he gave up arguing because too many voices did not like his solution. So my original version stands. However, the patch at the end of http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275528.html is useful, and it would be nice if it could be merged as well. Andrew -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On Wed, Oct 15, 2014 at 04:55:39PM +0200, Andrew Lunn wrote: Do you have a link to an email thread or the patch Subject line? I can confirm it's missing from mvebu/fixes... http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275487.html But you and Andrew should check what Arnd suggested. IIRC, there was also an appropriate follow-up patch discussion started by Andrew. There was a lot of back and forth with Arnd. In the end, he gave up arguing because too many voices did not like his solution. So my original version stands. Yes, this appears to have been a mistake on my part. In the conversation regarding patch #2 of V2, you said you were going to work on implementing something and would report back. I applied that to the whole series instead of just to the second patch. At any rate, applied to mvebu/fixes now. However, the patch at the end of http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275528.html is useful, and it would be nice if it could be merged as well. I'll take a look. thx, Jason. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Le 15 oct. 2014 à 16:41, Andrew Lunn and...@lunn.ch a écrit : All the 3 branch works WHEN APPLYING A0 patch (below), with both my custom kernel config and the arch/arm/configs/mvebu_v7_defconfig Just one thing though, one of my cron behavior change with 3.17, when I use the cmd /sbin/hwclock --adjust -f /dev/rtc1 I get this new error I never had before: hwclock: select() to /dev/rtc1 to wait for clock tick timed out: Success where rtc1 if the i2c rtc connected to the i2C bus, can this be related to the i2c patch that would slow down i2c operation or somthing ? Hi Benoit It won't fix your problem, but if the built in RTC is not usable, it would be good to disable it in the .dts file. The i2c RTC will then become RTC0. The actual error message is odd: hwclock: select() to /dev/rtc1 to wait for clock tick timed out: Success Yes this is the wired thing is that everything works, even getting the date via cat /sys/class/i2c-adapter/i2c-0/0-0051/rtc/rtc1/time is ok reading the rtc driver code it seems this message is shown when multiple resources try to access shared rtc... but why now and not before ? So I was wondering if the i2c_quirk() applied by the batch has any effect with this ? Anyhow I'll handle the message for now and see if there are performance impact on this... Benoit Success means it actually worked, not an error. Does the RTC contain the correct time afterwards? Andrew -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On Wed, Oct 15, 2014 at 11:30:49AM -0400, Jason Cooper wrote: On Wed, Oct 15, 2014 at 04:55:39PM +0200, Andrew Lunn wrote: Do you have a link to an email thread or the patch Subject line? I can confirm it's missing from mvebu/fixes... http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275487.html But you and Andrew should check what Arnd suggested. IIRC, there was also an appropriate follow-up patch discussion started by Andrew. There was a lot of back and forth with Arnd. In the end, he gave up arguing because too many voices did not like his solution. So my original version stands. Yes, this appears to have been a mistake on my part. In the conversation regarding patch #2 of V2, you said you were going to work on implementing something and would report back. I applied that to the whole series instead of just to the second patch. At any rate, applied to mvebu/fixes now. However, the patch at the end of http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275528.html is useful, and it would be nice if it could be merged as well. I'll take a look. I'd still like to see that note captured in the binding doc. Did I miss another patch somewhere? thx, Jason. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Le 6 oct. 2014 à 18:13, Sebastian Hesselbarth
a écrit :
> On 10/06/2014 01:11 AM, Benoit Masson wrote:
>> Le 3 oct. 2014 à 17:41, Sebastian Hesselbarth
>> a écrit :
>>> On 10/03/2014 05:29 PM, Benoit Masson wrote:
Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth
a écrit :
> On 10/03/2014 04:11 PM, Jason Cooper wrote:
>> On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote:
Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth
a écrit :
>>> [...]
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?
>
> Uhm, I never prepared a branch for Benoit to test. I have pushed the
> patches with Thomas Acked-by's and renamed eeprom node based on
> v3.17-rc1 to
>
> https://github.com/shesselba/linux-dove.git devel/mvebu-ix4
>
>>> [...]
>> Maybe I missed something ? is this branch you sent me a bare fork
>> from mainline 3.17 ? does it includes the armada XP step A0 patch ?
>
> Benoit,
>
Hi,
> I prepared more branches with the series
> - on top of v3.17 release:
> https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_v3.17
>
> - on top of next-20141003 (i.e. what will become v3.18-rc1):
> https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_next-20141003
>
> It would be great, if you can test in this order:
> - vanilla v3.17
> - mvebu-ix4_v3.17
> - mvebu-ix4_next-20141003
>
All the 3 branch works WHEN APPLYING A0 patch (below), with both my custom
kernel config and the arch/arm/configs/mvebu_v7_defconfig
The reason why it didn't worked last time was that apparently the A0 patch
(copied) below was not merged into 3.17 :(
This means that ix4-300d support is broken on 3.17 because of the A0 stepping
patch not merged.
patch (from Andrew Lunn Acked-by Gregory Clement is missing:
---
arch/arm/mach-mvebu/board-v7.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-mvebu/board-v7.c b/arch/arm/mach-mvebu/board-v7.c
index b2524d6..b1e148d 100644
--- a/arch/arm/mach-mvebu/board-v7.c
+++ b/arch/arm/mach-mvebu/board-v7.c
@@ -174,7 +174,7 @@ static void __init thermal_quirk(void)
static void __init mvebu_dt_init(void)
{
- if (of_machine_is_compatible("plathome,openblocks-ax3-4"))
+ if (of_machine_is_compatible("marvell,armadaxp"))
i2c_quirk();
if (of_machine_is_compatible("marvell,a375-db")) {
external_abort_quirk();
--
1.9.1
> If any branch fails, you can stop and please report back.
>
> I also have the ix4 but I need more time for a full setup like you
> already seem to have ready. Again, there is no hurry, take your time.
>
> Thanks!
>
> Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Le 6 oct. 2014 à 18:13, Sebastian Hesselbarth sebastian.hesselba...@gmail.com
a écrit :
On 10/06/2014 01:11 AM, Benoit Masson wrote:
Le 3 oct. 2014 à 17:41, Sebastian Hesselbarth
sebastian.hesselba...@gmail.com a écrit :
On 10/03/2014 05:29 PM, Benoit Masson wrote:
Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth
sebastian.hesselba...@gmail.com a écrit :
On 10/03/2014 04:11 PM, Jason Cooper wrote:
On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote:
Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth
sebastian.hesselba...@gmail.com a écrit :
[...]
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?
Uhm, I never prepared a branch for Benoit to test. I have pushed the
patches with Thomas Acked-by's and renamed eeprom node based on
v3.17-rc1 to
https://github.com/shesselba/linux-dove.git devel/mvebu-ix4
[...]
Maybe I missed something ? is this branch you sent me a bare fork
from mainline 3.17 ? does it includes the armada XP step A0 patch ?
Benoit,
Hi,
I prepared more branches with the series
- on top of v3.17 release:
https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_v3.17
- on top of next-20141003 (i.e. what will become v3.18-rc1):
https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_next-20141003
It would be great, if you can test in this order:
- vanilla v3.17
- mvebu-ix4_v3.17
- mvebu-ix4_next-20141003
All the 3 branch works WHEN APPLYING A0 patch (below), with both my custom
kernel config and the arch/arm/configs/mvebu_v7_defconfig
The reason why it didn't worked last time was that apparently the A0 patch
(copied) below was not merged into 3.17 :(
This means that ix4-300d support is broken on 3.17 because of the A0 stepping
patch not merged.
patch (from Andrew Lunn Acked-by Gregory Clement is missing:
---
arch/arm/mach-mvebu/board-v7.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-mvebu/board-v7.c b/arch/arm/mach-mvebu/board-v7.c
index b2524d6..b1e148d 100644
--- a/arch/arm/mach-mvebu/board-v7.c
+++ b/arch/arm/mach-mvebu/board-v7.c
@@ -174,7 +174,7 @@ static void __init thermal_quirk(void)
static void __init mvebu_dt_init(void)
{
- if (of_machine_is_compatible(plathome,openblocks-ax3-4))
+ if (of_machine_is_compatible(marvell,armadaxp))
i2c_quirk();
if (of_machine_is_compatible(marvell,a375-db)) {
external_abort_quirk();
--
1.9.1
If any branch fails, you can stop and please report back.
I also have the ix4 but I need more time for a full setup like you
already seem to have ready. Again, there is no hurry, take your time.
Thanks!
Sebastian
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On 10/06/2014 01:11 AM, Benoit Masson wrote: Le 3 oct. 2014 à 17:41, Sebastian Hesselbarth a écrit : On 10/03/2014 05:29 PM, Benoit Masson wrote: Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth a écrit : On 10/03/2014 04:11 PM, Jason Cooper wrote: On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote: Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth a écrit : [...] 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? Uhm, I never prepared a branch for Benoit to test. I have pushed the patches with Thomas Acked-by's and renamed eeprom node based on v3.17-rc1 to https://github.com/shesselba/linux-dove.git devel/mvebu-ix4 [...] Maybe I missed something ? is this branch you sent me a bare fork from mainline 3.17 ? does it includes the armada XP step A0 patch ? Benoit, I prepared more branches with the series - on top of v3.17 release: https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_v3.17 - on top of next-20141003 (i.e. what will become v3.18-rc1): https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_next-20141003 It would be great, if you can test in this order: - vanilla v3.17 - mvebu-ix4_v3.17 - mvebu-ix4_next-20141003 If any branch fails, you can stop and please report back. I also have the ix4 but I need more time for a full setup like you already seem to have ready. Again, there is no hurry, take your time. Thanks! Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Hi Benoit, >>> NR_IRQS:16 nr_irqs:16 16 >>> L2C: device tree omits to specify unified cache >> >> Jason, Thomas, Gregory, >> >> we should add a "cache-unified" to the l2cc nodes for all SoCs. > > It seems all armada dtsi using marvell,aurora-system-cache doesn't have the > "cache-unified" entry isn't this on purpose ? > No it was not really done in purpose. It was missing from the beginning. As the aurora l2cc was not a real l2x0 l2cc we put the minimal configuration. But I've just checked and the aurora l2cc is unified too, so a patch is coming soon to update the dtsi for Armada 370 and Armada XP. -- Gregory Clement, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Hi Sebastian, > [...] >> NR_IRQS:16 nr_irqs:16 16 >> L2C: device tree omits to specify unified cache > > Jason, Thomas, Gregory, > > we should add a "cache-unified" to the l2cc nodes for all SoCs. Right, I take care of it. Thanks, Gregory -- Gregory Clement, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On 06.10.2014 01:11, Benoit Masson wrote: > Le 3 oct. 2014 à 17:41, Sebastian Hesselbarth a écrit : On 10/03/2014 05:29 PM, Benoit Masson wrote: Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth a écrit : On 10/03/2014 04:11 PM, Jason Cooper wrote: On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote: Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth a écrit : [...] 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. [...] Did you ever get a chance to test this series? Uhm, I never prepared a branch for Benoit to test. I have pushed the patches with Thomas Acked-by's and renamed eeprom node based on v3.17-rc1 to https://github.com/shesselba/linux-dove.git devel/mvebu-ix4 [...] It is too late for v3.18 anyway, so I'll resend them once v3.18-rc1 drops. I'll test those over Sunday night. No so great, so far what I've done: - use my working config this config has worked over mainline 3.16 for weeks - compil you branch with it using you dts file - boot KO it get stuck on i2C pcf8563 init (at least it is the last message dsplayed. then I turn on DEBUG_LL but I get nothing more on the serial that could help - I've tried removing the eeprom section you added to the dts -> same results Maybe I missed something ? is this branch you sent me a bare fork from mainline 3.17 ? does it includes the armada XP step A0 patch ? Benoit, the branch is straight forked from v3.17-rc1 with the patches in question added. If there is any fixes that got in after rc1, they are not included. I'll rebase the series on latest next tonight. Anyway, I doubt the series is involved in the regression you see, can you also boot plain v3.17-rc1 and v3.17 which got just released? Also, DEBUG_LL will not give you any more information on this one, as you passed serial console hand-off. You only need it for early debugging and you have to make sure that (a) you select the correct DEBUG_LL Kconfig for MVEBU with registers located at 0xd000 and (b) you should always double check the phys/virt addresses of the early console. dump of the serial output: Uncompressing Linux... done, booting the kernel. Booting Linux on physical CPU 0x0 Linux version 3.17.0-rc1-42264-gb065757 (benoitm@) (gcc version 4.6.3 (Debian 4.6.3-14) ) #3 SMP Mon Oct 6 00:42:59 CEST 2014 CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c5387d CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache Machine model: Lenovo Iomega ix4-300d Memory policy: Data cache writealloc PERCPU: Embedded 7 pages/cpu @dfbd9000 s6784 r8192 d13696 u32768 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 Kernel command line: console=ttyS0,115200 earlyprintk=ttyS0,115200 root=/dev/md0 rw mem=512M /dev/md0 is soft-RAID on your harddisks, isn't it? Also, you should not need the mem= parameter but that is just a nit. [...] NR_IRQS:16 nr_irqs:16 16 L2C: device tree omits to specify unified cache Jason, Thomas, Gregory, we should add a "cache-unified" to the l2cc nodes for all SoCs. L2C: DT/platform modifies aux control register: 0x1a696b10 -> 0x1a696b12 Aurora cache controller enabled, 16 ways, 1024 kB Aurora: CACHE_ID 0x0100, AUX_CTRL 0x1a696b12 sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 171798691800ns [...] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled console [ttyS0] disabled d0012000.serial: ttyS0 at MMIO 0xd0012000 (irq = 19, base_baud = 15625000) is a 16550A console [ttyS0] enabled Here is the serial console hand-off, i.e. if you get this far, you don't need DEBUG_LL at all. zram: Created 1 device(s) ... pci :00:01.0: enabling device (0140 -> 0143) sata_mv :01:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx scsi host0: sata_mv scsi host1: sata_mv scsi host2: sata_mv scsi host3: sata_mv ata1: SATA max UDMA/133 mmio m1048576@0xf800 port 0xf8022000 irq 86 ata2: SATA max UDMA/133 mmio m1048576@0xf800 port 0xf8024000 irq 86 ata3: SATA max UDMA/133 mmio m1048576@0xf800 port 0xf8026000 irq 86 ata4: SATA max UDMA/133 mmio m1048576@0xf800 port 0xf8028000 irq 86 Shouldn't it detect your hard-disks attached here? Sebastian pxa3xx-nand d00d.nand: This platform can't do DMA on this device nand: device found, Manufacturer ID: 0xec, Chip ID: 0xd3 nand: Samsung NAND 1GiB 3,3V 8-bit nand: 1024MiB, SLC, page size: 2048, OOB size: 64 pxa3xx-nand d00d.nand: ECC strength 1, ECC step size 512 Bad block table found at page 524224, version 0x01 Bad block table found at page 524160, version 0x01 nand_read_bbt: bad block at 0x3ca6 7 ofpart partitions found on MTD device pxa3xx_nand-0 Creating 7 MTD partitions on "pxa3xx_nand-0": 0x-0x000e : "u-boot" 0x000e-0x0010 : "u-boot-env" 0x0010-0x0012 : "u-boot-env2"
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On 06.10.2014 01:11, Benoit Masson wrote: Le 3 oct. 2014 à 17:41, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : On 10/03/2014 05:29 PM, Benoit Masson wrote: Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : On 10/03/2014 04:11 PM, Jason Cooper wrote: On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote: Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : [...] 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. [...] Did you ever get a chance to test this series? Uhm, I never prepared a branch for Benoit to test. I have pushed the patches with Thomas Acked-by's and renamed eeprom node based on v3.17-rc1 to https://github.com/shesselba/linux-dove.git devel/mvebu-ix4 [...] It is too late for v3.18 anyway, so I'll resend them once v3.18-rc1 drops. I'll test those over Sunday night. No so great, so far what I've done: - use my working config this config has worked over mainline 3.16 for weeks - compil you branch with it using you dts file - boot KO it get stuck on i2C pcf8563 init (at least it is the last message dsplayed. then I turn on DEBUG_LL but I get nothing more on the serial that could help - I've tried removing the eeprom section you added to the dts - same results Maybe I missed something ? is this branch you sent me a bare fork from mainline 3.17 ? does it includes the armada XP step A0 patch ? Benoit, the branch is straight forked from v3.17-rc1 with the patches in question added. If there is any fixes that got in after rc1, they are not included. I'll rebase the series on latest next tonight. Anyway, I doubt the series is involved in the regression you see, can you also boot plain v3.17-rc1 and v3.17 which got just released? Also, DEBUG_LL will not give you any more information on this one, as you passed serial console hand-off. You only need it for early debugging and you have to make sure that (a) you select the correct DEBUG_LL Kconfig for MVEBU with registers located at 0xd000 and (b) you should always double check the phys/virt addresses of the early console. dump of the serial output: Uncompressing Linux... done, booting the kernel. Booting Linux on physical CPU 0x0 Linux version 3.17.0-rc1-42264-gb065757 (benoitm@) (gcc version 4.6.3 (Debian 4.6.3-14) ) #3 SMP Mon Oct 6 00:42:59 CEST 2014 CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c5387d CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache Machine model: Lenovo Iomega ix4-300d Memory policy: Data cache writealloc PERCPU: Embedded 7 pages/cpu @dfbd9000 s6784 r8192 d13696 u32768 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 Kernel command line: console=ttyS0,115200 earlyprintk=ttyS0,115200 root=/dev/md0 rw mem=512M /dev/md0 is soft-RAID on your harddisks, isn't it? Also, you should not need the mem= parameter but that is just a nit. [...] NR_IRQS:16 nr_irqs:16 16 L2C: device tree omits to specify unified cache Jason, Thomas, Gregory, we should add a cache-unified to the l2cc nodes for all SoCs. L2C: DT/platform modifies aux control register: 0x1a696b10 - 0x1a696b12 Aurora cache controller enabled, 16 ways, 1024 kB Aurora: CACHE_ID 0x0100, AUX_CTRL 0x1a696b12 sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 171798691800ns [...] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled console [ttyS0] disabled d0012000.serial: ttyS0 at MMIO 0xd0012000 (irq = 19, base_baud = 15625000) is a 16550A console [ttyS0] enabled Here is the serial console hand-off, i.e. if you get this far, you don't need DEBUG_LL at all. zram: Created 1 device(s) ... pci :00:01.0: enabling device (0140 - 0143) sata_mv :01:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx scsi host0: sata_mv scsi host1: sata_mv scsi host2: sata_mv scsi host3: sata_mv ata1: SATA max UDMA/133 mmio m1048576@0xf800 port 0xf8022000 irq 86 ata2: SATA max UDMA/133 mmio m1048576@0xf800 port 0xf8024000 irq 86 ata3: SATA max UDMA/133 mmio m1048576@0xf800 port 0xf8026000 irq 86 ata4: SATA max UDMA/133 mmio m1048576@0xf800 port 0xf8028000 irq 86 Shouldn't it detect your hard-disks attached here? Sebastian pxa3xx-nand d00d.nand: This platform can't do DMA on this device nand: device found, Manufacturer ID: 0xec, Chip ID: 0xd3 nand: Samsung NAND 1GiB 3,3V 8-bit nand: 1024MiB, SLC, page size: 2048, OOB size: 64 pxa3xx-nand d00d.nand: ECC strength 1, ECC step size 512 Bad block table found at page 524224, version 0x01 Bad block table found at page 524160, version 0x01 nand_read_bbt: bad block at 0x3ca6 7 ofpart partitions found on MTD device pxa3xx_nand-0 Creating 7 MTD partitions on pxa3xx_nand-0: 0x-0x000e : u-boot 0x000e-0x0010 :
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Hi Sebastian, [...] NR_IRQS:16 nr_irqs:16 16 L2C: device tree omits to specify unified cache Jason, Thomas, Gregory, we should add a cache-unified to the l2cc nodes for all SoCs. Right, I take care of it. Thanks, Gregory -- Gregory Clement, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Hi Benoit, NR_IRQS:16 nr_irqs:16 16 L2C: device tree omits to specify unified cache Jason, Thomas, Gregory, we should add a cache-unified to the l2cc nodes for all SoCs. It seems all armada dtsi using marvell,aurora-system-cache doesn't have the cache-unified entry isn't this on purpose ? No it was not really done in purpose. It was missing from the beginning. As the aurora l2cc was not a real l2x0 l2cc we put the minimal configuration. But I've just checked and the aurora l2cc is unified too, so a patch is coming soon to update the dtsi for Armada 370 and Armada XP. -- Gregory Clement, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On 10/06/2014 01:11 AM, Benoit Masson wrote: Le 3 oct. 2014 à 17:41, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : On 10/03/2014 05:29 PM, Benoit Masson wrote: Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : On 10/03/2014 04:11 PM, Jason Cooper wrote: On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote: Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : [...] 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? Uhm, I never prepared a branch for Benoit to test. I have pushed the patches with Thomas Acked-by's and renamed eeprom node based on v3.17-rc1 to https://github.com/shesselba/linux-dove.git devel/mvebu-ix4 [...] Maybe I missed something ? is this branch you sent me a bare fork from mainline 3.17 ? does it includes the armada XP step A0 patch ? Benoit, I prepared more branches with the series - on top of v3.17 release: https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_v3.17 - on top of next-20141003 (i.e. what will become v3.18-rc1): https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_next-20141003 It would be great, if you can test in this order: - vanilla v3.17 - mvebu-ix4_v3.17 - mvebu-ix4_next-20141003 If any branch fails, you can stop and please report back. I also have the ix4 but I need more time for a full setup like you already seem to have ready. Again, there is no hurry, take your time. Thanks! Sebastian -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Le 3 oct. 2014 à 17:41, Sebastian Hesselbarth a écrit : > On 10/03/2014 05:29 PM, Benoit Masson wrote: >> Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth >> a écrit : >>> On 10/03/2014 04:11 PM, Jason Cooper wrote: On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote: >> Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth >> a écrit : > [...] >> 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? >>> >>> Uhm, I never prepared a branch for Benoit to test. I have pushed the >>> patches with Thomas Acked-by's and renamed eeprom node based on >>> v3.17-rc1 to >>> >>> https://github.com/shesselba/linux-dove.git devel/mvebu-ix4 >>> > [...] >> Also I've noted you did some other patch for Armada XP not related to >> ix-4-300d, > > are they included here or should I get them too ? > > No, they are neither included nor is there any need to test. They are > about pcie-lanes property but it is more or less unused on Linux. > > It is too late for v3.18 anyway, so I'll resend them once v3.18-rc1 > drops. > >> I'll test those over Sunday night. > > Ok, great! Hi, No so great, so far what I've done: - use my working config this config has worked over mainline 3.16 for weeks - compil you branch with it using you dts file - boot KO it get stuck on i2C pcf8563 init (at least it is the last message dsplayed. then I turn on DEBUG_LL but I get nothing more on the serial that could help - I've tried removing the eeprom section you added to the dts -> same results Maybe I missed something ? is this branch you sent me a bare fork from mainline 3.17 ? does it includes the armada XP step A0 patch ? dump of the serial output: Uncompressing Linux... done, booting the kernel. Booting Linux on physical CPU 0x0 Linux version 3.17.0-rc1-42264-gb065757 (benoitm@) (gcc version 4.6.3 (Debian 4.6.3-14) ) #3 SMP Mon Oct 6 00:42:59 CEST 2014 CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c5387d CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache Machine model: Lenovo Iomega ix4-300d Memory policy: Data cache writealloc PERCPU: Embedded 7 pages/cpu @dfbd9000 s6784 r8192 d13696 u32768 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 Kernel command line: console=ttyS0,115200 earlyprintk=ttyS0,115200 root=/dev/md0 rw mem=512M PID hash table entries: 2048 (order: 1, 8192 bytes) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 512868K/524288K available (4787K kernel code, 254K rwdata, 1324K rodata, 254K init, 131K bss, 11420K reserved, 0K highmem) Virtual kernel memory layout: vector : 0x - 0x1000 ( 4 kB) fixmap : 0xffc0 - 0xffe0 (2048 kB) vmalloc : 0xe080 - 0xff00 ( 488 MB) lowmem : 0xc000 - 0xe000 ( 512 MB) pkmap : 0xbfe0 - 0xc000 ( 2 MB) modules : 0xbf00 - 0xbfe0 ( 14 MB) .text : 0xc0008000 - 0xc05fffac (6112 kB) .init : 0xc060 - 0xc063fa80 ( 255 kB) .data : 0xc064 - 0xc067fa60 ( 255 kB) .bss : 0xc067fa60 - 0xc06a098c ( 132 kB) Hierarchical RCU implementation. NR_IRQS:16 nr_irqs:16 16 L2C: device tree omits to specify unified cache L2C: DT/platform modifies aux control register: 0x1a696b10 -> 0x1a696b12 Aurora cache controller enabled, 16 ways, 1024 kB Aurora: CACHE_ID 0x0100, AUX_CTRL 0x1a696b12 sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 171798691800ns Console: colour dummy device 80x30 Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok CPU0: thread -1, cpu 0, socket 0, mpidr 8000 Setting up static identity map for 0x4b2b70 - 0x4b2bc8 mvebu-soc-id: MVEBU SoC ID=0x7823, Rev=0x1 mvebu-pmsu: Initializing Power Management Service Unit Booting CPU 1 CPU1: Booted secondary processor CPU1: thread -1, cpu 1, socket 0, mpidr 8001 Brought up 2 CPUs SMP: Total of 2 processors activated. CPU: All CPU(s) started in SVC mode. VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6 xor: measuring software checksum speed arm4regs : 1093.200 MB/sec 8regs : 1092.000 MB/sec 32regs: 1011.200 MB/sec xor: using function: arm4regs (1093.200 MB/sec) pinctrl core: initialized pinctrl subsystem NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Le 3 oct. 2014 à 17:41, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : On 10/03/2014 05:29 PM, Benoit Masson wrote: Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : On 10/03/2014 04:11 PM, Jason Cooper wrote: On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote: Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : [...] 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? Uhm, I never prepared a branch for Benoit to test. I have pushed the patches with Thomas Acked-by's and renamed eeprom node based on v3.17-rc1 to https://github.com/shesselba/linux-dove.git devel/mvebu-ix4 [...] Also I've noted you did some other patch for Armada XP not related to ix-4-300d, are they included here or should I get them too ? No, they are neither included nor is there any need to test. They are about pcie-lanes property but it is more or less unused on Linux. It is too late for v3.18 anyway, so I'll resend them once v3.18-rc1 drops. I'll test those over Sunday night. Ok, great! Hi, No so great, so far what I've done: - use my working config this config has worked over mainline 3.16 for weeks - compil you branch with it using you dts file - boot KO it get stuck on i2C pcf8563 init (at least it is the last message dsplayed. then I turn on DEBUG_LL but I get nothing more on the serial that could help - I've tried removing the eeprom section you added to the dts - same results Maybe I missed something ? is this branch you sent me a bare fork from mainline 3.17 ? does it includes the armada XP step A0 patch ? dump of the serial output: Uncompressing Linux... done, booting the kernel. Booting Linux on physical CPU 0x0 Linux version 3.17.0-rc1-42264-gb065757 (benoitm@) (gcc version 4.6.3 (Debian 4.6.3-14) ) #3 SMP Mon Oct 6 00:42:59 CEST 2014 CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c5387d CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache Machine model: Lenovo Iomega ix4-300d Memory policy: Data cache writealloc PERCPU: Embedded 7 pages/cpu @dfbd9000 s6784 r8192 d13696 u32768 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 Kernel command line: console=ttyS0,115200 earlyprintk=ttyS0,115200 root=/dev/md0 rw mem=512M PID hash table entries: 2048 (order: 1, 8192 bytes) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 512868K/524288K available (4787K kernel code, 254K rwdata, 1324K rodata, 254K init, 131K bss, 11420K reserved, 0K highmem) Virtual kernel memory layout: vector : 0x - 0x1000 ( 4 kB) fixmap : 0xffc0 - 0xffe0 (2048 kB) vmalloc : 0xe080 - 0xff00 ( 488 MB) lowmem : 0xc000 - 0xe000 ( 512 MB) pkmap : 0xbfe0 - 0xc000 ( 2 MB) modules : 0xbf00 - 0xbfe0 ( 14 MB) .text : 0xc0008000 - 0xc05fffac (6112 kB) .init : 0xc060 - 0xc063fa80 ( 255 kB) .data : 0xc064 - 0xc067fa60 ( 255 kB) .bss : 0xc067fa60 - 0xc06a098c ( 132 kB) Hierarchical RCU implementation. NR_IRQS:16 nr_irqs:16 16 L2C: device tree omits to specify unified cache L2C: DT/platform modifies aux control register: 0x1a696b10 - 0x1a696b12 Aurora cache controller enabled, 16 ways, 1024 kB Aurora: CACHE_ID 0x0100, AUX_CTRL 0x1a696b12 sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 171798691800ns Console: colour dummy device 80x30 Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok CPU0: thread -1, cpu 0, socket 0, mpidr 8000 Setting up static identity map for 0x4b2b70 - 0x4b2bc8 mvebu-soc-id: MVEBU SoC ID=0x7823, Rev=0x1 mvebu-pmsu: Initializing Power Management Service Unit Booting CPU 1 CPU1: Booted secondary processor CPU1: thread -1, cpu 1, socket 0, mpidr 8001 Brought up 2 CPUs SMP: Total of 2 processors activated. CPU: All CPU(s) started in SVC mode. VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6 xor: measuring software checksum speed arm4regs : 1093.200 MB/sec 8regs : 1092.000 MB/sec 32regs: 1011.200 MB/sec xor: using function: arm4regs (1093.200 MB/sec) pinctrl core: initialized pinctrl subsystem NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations raid6:
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On 10/03/2014 05:29 PM, Benoit Masson wrote: Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth a écrit : On 10/03/2014 04:11 PM, Jason Cooper wrote: On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote: Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth a écrit : [...] 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? Uhm, I never prepared a branch for Benoit to test. I have pushed the patches with Thomas Acked-by's and renamed eeprom node based on v3.17-rc1 to https://github.com/shesselba/linux-dove.git devel/mvebu-ix4 [...] Also I've noted you did some other patch for Armada XP not related to ix-4-300d, > are they included here or should I get them too ? No, they are neither included nor is there any need to test. They are about pcie-lanes property but it is more or less unused on Linux. It is too late for v3.18 anyway, so I'll resend them once v3.18-rc1 drops. I'll test those over Sunday night. Ok, great! Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth
a écrit :
> On 10/03/2014 04:11 PM, Jason Cooper wrote:
>> On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote:
Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth
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?
>
> Uhm, I never prepared a branch for Benoit to test. I have pushed the
> patches with Thomas Acked-by's and renamed eeprom node based on
> v3.17-rc1 to
>
> https://github.com/shesselba/linux-dove.git devel/mvebu-ix4
>
Hi tahnks, that was my last question, because I was lost about which to apply
from the list of 8.
Also I've noted you did some other patch for Armada XP not related to
ix-4-300d, are they included here or should I get them too ?
I'll test those over Sunday night.
Benoit
> Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On 10/03/2014 04:11 PM, Jason Cooper wrote:
On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote:
Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth
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?
Uhm, I never prepared a branch for Benoit to test. I have pushed the
patches with Thomas Acked-by's and renamed eeprom node based on
v3.17-rc1 to
https://github.com/shesselba/linux-dove.git devel/mvebu-ix4
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Benoit,
On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote:
> > Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth
> > 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Benoit,
On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote:
Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth
sebastian.hesselba...@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.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On 10/03/2014 04:11 PM, Jason Cooper wrote:
On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote:
Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth
sebastian.hesselba...@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?
Uhm, I never prepared a branch for Benoit to test. I have pushed the
patches with Thomas Acked-by's and renamed eeprom node based on
v3.17-rc1 to
https://github.com/shesselba/linux-dove.git devel/mvebu-ix4
Sebastian
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth sebastian.hesselba...@gmail.com
a écrit :
On 10/03/2014 04:11 PM, Jason Cooper wrote:
On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote:
Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth
sebastian.hesselba...@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?
Uhm, I never prepared a branch for Benoit to test. I have pushed the
patches with Thomas Acked-by's and renamed eeprom node based on
v3.17-rc1 to
https://github.com/shesselba/linux-dove.git devel/mvebu-ix4
Hi tahnks, that was my last question, because I was lost about which to apply
from the list of 8.
Also I've noted you did some other patch for Armada XP not related to
ix-4-300d, are they included here or should I get them too ?
I'll test those over Sunday night.
Benoit
Sebastian
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
On 10/03/2014 05:29 PM, Benoit Masson wrote: Le 3 oct. 2014 à 17:06, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : On 10/03/2014 04:11 PM, Jason Cooper wrote: On Sun, Sep 21, 2014 at 04:11:23PM +0200, Benoit Masson wrote: Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth sebastian.hesselba...@gmail.com a écrit : [...] 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? Uhm, I never prepared a branch for Benoit to test. I have pushed the patches with Thomas Acked-by's and renamed eeprom node based on v3.17-rc1 to https://github.com/shesselba/linux-dove.git devel/mvebu-ix4 [...] Also I've noted you did some other patch for Armada XP not related to ix-4-300d, are they included here or should I get them too ? No, they are neither included nor is there any need to test. They are about pcie-lanes property but it is more or less unused on Linux. It is too late for v3.18 anyway, so I'll resend them once v3.18-rc1 drops. I'll test those over Sunday night. Ok, great! Sebastian -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
> Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth
> a écrit :
>
> Guys,
Hi
>
> 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.
>
> Sébastien
>
Thanks benoît
>
> Sebastian Hesselbarth (8):
> ARM: mvebu: armada-xp: Consolidate pinctrl node
> ARM: mvebu: armada-xp: Add node alias to pinctrl and add base address
> ARM: mvebu: armada-xp: Use pinctrl node alias
> ARM: mvebu: armada-xp: Move GE0/1 pinctrl settings for RGMII
> ARM: mvebu: armada-xp: Add GE0 pinctrl settings for GMII
> ARM: mvebu: armada-xp: Add RGMII pinctrl to Lenovo ix4-300d
> ARM: mvebu: armada-xp: Add I2C eeprom on Lenovo ix4-300d
> ARM: mvebu: armada-xp: Fix 74hc595 count for Lenovo ix4-300d
>
> arch/arm/boot/dts/armada-xp-axpwifiap.dts| 58 +++-
> arch/arm/boot/dts/armada-xp-lenovo-ix4-300d.dts | 73 +-
> arch/arm/boot/dts/armada-xp-mv78230.dtsi | 15 +--
> arch/arm/boot/dts/armada-xp-mv78260.dtsi | 15 +--
> arch/arm/boot/dts/armada-xp-mv78460.dtsi | 15 +--
> arch/arm/boot/dts/armada-xp-netgear-rn2120.dts | 164 +++
> arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts | 14 +-
> arch/arm/boot/dts/armada-xp.dtsi | 37 +
> 8 files changed, 202 insertions(+), 189 deletions(-)
>
> ---
> Cc: Jason Cooper
> Cc: Andrew Lunn
> Cc: Gregory Clement
> Cc: Ezequiel Garcia
> Cc: Thomas Petazzoni
> Cc: Benoit Masson
> Cc: devicet...@vger.kernel.org
> Cc: linux-arm-ker...@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> --
> 2.0.0
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Le 19 sept. 2014 à 22:14, Sebastian Hesselbarth
sebastian.hesselba...@gmail.com a écrit :
Guys,
Hi
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.
Sébastien
Thanks benoît
Sebastian Hesselbarth (8):
ARM: mvebu: armada-xp: Consolidate pinctrl node
ARM: mvebu: armada-xp: Add node alias to pinctrl and add base address
ARM: mvebu: armada-xp: Use pinctrl node alias
ARM: mvebu: armada-xp: Move GE0/1 pinctrl settings for RGMII
ARM: mvebu: armada-xp: Add GE0 pinctrl settings for GMII
ARM: mvebu: armada-xp: Add RGMII pinctrl to Lenovo ix4-300d
ARM: mvebu: armada-xp: Add I2C eeprom on Lenovo ix4-300d
ARM: mvebu: armada-xp: Fix 74hc595 count for Lenovo ix4-300d
arch/arm/boot/dts/armada-xp-axpwifiap.dts| 58 +++-
arch/arm/boot/dts/armada-xp-lenovo-ix4-300d.dts | 73 +-
arch/arm/boot/dts/armada-xp-mv78230.dtsi | 15 +--
arch/arm/boot/dts/armada-xp-mv78260.dtsi | 15 +--
arch/arm/boot/dts/armada-xp-mv78460.dtsi | 15 +--
arch/arm/boot/dts/armada-xp-netgear-rn2120.dts | 164 +++
arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts | 14 +-
arch/arm/boot/dts/armada-xp.dtsi | 37 +
8 files changed, 202 insertions(+), 189 deletions(-)
---
Cc: Jason Cooper ja...@lakedaemon.net
Cc: Andrew Lunn and...@lunn.ch
Cc: Gregory Clement gregory.clem...@free-electrons.com
Cc: Ezequiel Garcia ezequiel.gar...@free-electrons.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Benoit Masson ya...@perenite.com
Cc: devicet...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
--
2.0.0
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Guys,
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.
Sebastian
Sebastian Hesselbarth (8):
ARM: mvebu: armada-xp: Consolidate pinctrl node
ARM: mvebu: armada-xp: Add node alias to pinctrl and add base address
ARM: mvebu: armada-xp: Use pinctrl node alias
ARM: mvebu: armada-xp: Move GE0/1 pinctrl settings for RGMII
ARM: mvebu: armada-xp: Add GE0 pinctrl settings for GMII
ARM: mvebu: armada-xp: Add RGMII pinctrl to Lenovo ix4-300d
ARM: mvebu: armada-xp: Add I2C eeprom on Lenovo ix4-300d
ARM: mvebu: armada-xp: Fix 74hc595 count for Lenovo ix4-300d
arch/arm/boot/dts/armada-xp-axpwifiap.dts| 58 +++-
arch/arm/boot/dts/armada-xp-lenovo-ix4-300d.dts | 73 +-
arch/arm/boot/dts/armada-xp-mv78230.dtsi | 15 +--
arch/arm/boot/dts/armada-xp-mv78260.dtsi | 15 +--
arch/arm/boot/dts/armada-xp-mv78460.dtsi | 15 +--
arch/arm/boot/dts/armada-xp-netgear-rn2120.dts | 164 +++
arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts | 14 +-
arch/arm/boot/dts/armada-xp.dtsi | 37 +
8 files changed, 202 insertions(+), 189 deletions(-)
---
Cc: Jason Cooper
Cc: Andrew Lunn
Cc: Gregory Clement
Cc: Ezequiel Garcia
Cc: Thomas Petazzoni
Cc: Benoit Masson
Cc: devicet...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
--
2.0.0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Guys,
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.
Sebastian
Sebastian Hesselbarth (8):
ARM: mvebu: armada-xp: Consolidate pinctrl node
ARM: mvebu: armada-xp: Add node alias to pinctrl and add base address
ARM: mvebu: armada-xp: Use pinctrl node alias
ARM: mvebu: armada-xp: Move GE0/1 pinctrl settings for RGMII
ARM: mvebu: armada-xp: Add GE0 pinctrl settings for GMII
ARM: mvebu: armada-xp: Add RGMII pinctrl to Lenovo ix4-300d
ARM: mvebu: armada-xp: Add I2C eeprom on Lenovo ix4-300d
ARM: mvebu: armada-xp: Fix 74hc595 count for Lenovo ix4-300d
arch/arm/boot/dts/armada-xp-axpwifiap.dts| 58 +++-
arch/arm/boot/dts/armada-xp-lenovo-ix4-300d.dts | 73 +-
arch/arm/boot/dts/armada-xp-mv78230.dtsi | 15 +--
arch/arm/boot/dts/armada-xp-mv78260.dtsi | 15 +--
arch/arm/boot/dts/armada-xp-mv78460.dtsi | 15 +--
arch/arm/boot/dts/armada-xp-netgear-rn2120.dts | 164 +++
arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts | 14 +-
arch/arm/boot/dts/armada-xp.dtsi | 37 +
8 files changed, 202 insertions(+), 189 deletions(-)
---
Cc: Jason Cooper ja...@lakedaemon.net
Cc: Andrew Lunn and...@lunn.ch
Cc: Gregory Clement gregory.clem...@free-electrons.com
Cc: Ezequiel Garcia ezequiel.gar...@free-electrons.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Benoit Masson ya...@perenite.com
Cc: devicet...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
--
2.0.0
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
