Hi Olof, Hi Arnd,
please consider the following fixes for the Armadillo800 EVA and
Mackerel boards from Morimoto-san.
* "ARM: shmobile: armadillo800eva: fixup: sound card detection order"
is a regression fix.
* "ARM: shmobile: mackerel: fixup usb module order"
is a regression fix.
* "ARM: shmobile: armadillo800eva: enable rw rootfs mount"
is a boot-loader compatibility fix.
All of the changes are aimed at improving the end-user experience.
Notes:
* This pull request is based on my previous
"[GIT PULL] Renesas ARM-based SoC fix for v3.6" pull request
which was recently pulled by Olof. Please let me know
if you would like me to handle this a different way.
----------------------------------------------------------------
The following changes since commit 497dcf6fc355f0734faf851662b6957386715d24:
ARM: shmobile: marzen: fixup smsc911x id for regulator (2012-08-30 14:10:08 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git fixes
for you to fetch changes up to 28e515878f8896b33c325ff9767cb0237210fb4c:
ARM: shmobile: armadillo800eva: enable rw rootfs mount (2012-09-03 17:31:34 +0900)
----------------------------------------------------------------
Kuninori Morimoto (3):
ARM: shmobile: armadillo800eva: fixup: sound card detection order
ARM: shmobile: mackerel: fixup usb module order
ARM: shmobile: armadillo800eva: enable rw rootfs mount
arch/arm/configs/armadillo800eva_defconfig | 2 +-
arch/arm/mach-shmobile/board-armadillo800eva.c | 2 +-
arch/arm/mach-shmobile/board-mackerel.c | 3 ++-
3 files changed, 4 insertions(+), 3 deletions(-)
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Since armadillo800eva has 2 sound cards,
and had reversed deferred probe order issue,
it was purposely registered in reverse order.
But it was solved by
1d29cfa57471a5e4b8a7c2a7433eeba170d3ad92
(driver core: fixup reversed deferred probe order)
armadillo800eva board is expecting that
FSI-WM8978 is the 1st, and FSI-HDMI is the 2nd sound card.
This patch fixes it up
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Signed-off-by: Simon Horman <horms@verge.net.au>
---
arch/arm/mach-shmobile/board-armadillo800eva.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
renesas_usbhs driver can play role as both Host and Gadget.
In case of Gadget, it requires not only renesas_usbhs
but also usb gadget module (like g_ether).
So, renesas_usbhs driver calls usb_add_gadget_udc() on probe time.
Because of this behavior,
Host port plays also Gadget role if kernel has both Host/Gadget support.
In mackerel case, from 0ada2da51800a4914887a9bcf22d563be80e50be
(ARM: mach-shmobile: mackerel: use renesas_usbhs instead of r8a66597_hcd)
usb0 plays Gadget role, and usb1 plays Host role,
and current mackerel board probes as usb1 -> usb0.
Thus, 1st installed usb gadget module (like g_ether) will be
assigned to usb1 (= usb Host port), and 2nd module to usb0 (= usb Gadget port).
It is very confusable for user.
This patch fixup usb modes probing order as usb0 -> usb1.
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Signed-off-by: Simon Horman <horms@verge.net.au>
---
arch/arm/mach-shmobile/board-mackerel.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
armadillo800eva default boot loader is "hermit",
and it's tag->u.core.flags has flag when kernel boots.
Because of this, ${LINUX}/arch/arm/kernel/setup.c :: parse_tag_core()
didn't remove MS_RDONLY flag from root_mountflags.
Thus, the rootfs is mounted as "readonly".
This patch adds "rw" kernel parameter,
and enable read/write mounts for rootfs
Cc: Masahiro Nakai <redacted>
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Signed-off-by: Simon Horman <horms@verge.net.au>
---
arch/arm/configs/armadillo800eva_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Olof Johansson <hidden> Date: 2012-09-05 04:44:41
On Wed, Sep 05, 2012 at 10:34:50AM +0900, Simon Horman wrote:
Hi Olof, Hi Arnd,
please consider the following fixes for the Armadillo800 EVA and
Mackerel boards from Morimoto-san.
* "ARM: shmobile: armadillo800eva: fixup: sound card detection order"
is a regression fix.
* "ARM: shmobile: mackerel: fixup usb module order"
is a regression fix.
* "ARM: shmobile: armadillo800eva: enable rw rootfs mount"
is a boot-loader compatibility fix.
All of the changes are aimed at improving the end-user experience.
Notes:
* This pull request is based on my previous
"[GIT PULL] Renesas ARM-based SoC fix for v3.6" pull request
which was recently pulled by Olof. Please let me know
if you would like me to handle this a different way.
That's exactly the way to do it. In this case it meant I have two pulls after
each other from the same tree, and I suppose I could replace the older one with
the newer one but that means rebasing so I just pulled it in. Either way, you
just need to send a delta pull request like you did, the rest would be up to
us.
----------------------------------------------------------------
The following changes since commit 497dcf6fc355f0734faf851662b6957386715d24:
ARM: shmobile: marzen: fixup smsc911x id for regulator (2012-08-30 14:10:08 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git fixes
On Tue, Sep 04, 2012 at 09:44:41PM -0700, Olof Johansson wrote:
On Wed, Sep 05, 2012 at 10:34:50AM +0900, Simon Horman wrote:
quoted
Hi Olof, Hi Arnd,
please consider the following fixes for the Armadillo800 EVA and
Mackerel boards from Morimoto-san.
* "ARM: shmobile: armadillo800eva: fixup: sound card detection order"
is a regression fix.
* "ARM: shmobile: mackerel: fixup usb module order"
is a regression fix.
* "ARM: shmobile: armadillo800eva: enable rw rootfs mount"
is a boot-loader compatibility fix.
All of the changes are aimed at improving the end-user experience.
Notes:
* This pull request is based on my previous
"[GIT PULL] Renesas ARM-based SoC fix for v3.6" pull request
which was recently pulled by Olof. Please let me know
if you would like me to handle this a different way.
That's exactly the way to do it. In this case it meant I have two pulls
after each other from the same tree, and I suppose I could replace the
older one with the newer one but that means rebasing so I just pulled it
in. Either way, you just need to send a delta pull request like you did,
the rest would be up to us.