From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Simon Horman <horms@verge.net.au>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <damm+renesas@opensource.se>,
Arnd Bergmann <arnd@arndb.de>,
linux-sh@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH 00/15] ARM: shmobile: Remove legacy sh73a0/kzm9g and r8a7740/armadillo
Date: Fri, 19 Jun 2015 12:05:08 +0300 [thread overview]
Message-ID: <2048890.5QyZKokOfh@avalon> (raw)
In-Reply-To: <20150619034052.GA22912@verge.net.au>
Hi Simon,
On Friday 19 June 2015 12:41:00 Simon Horman wrote:
> [ CC Linus, Laurent, linux-gpio ]
>
> On Wed, Jun 17, 2015 at 11:31:16AM +0200, Geert Uytterhoeven wrote:
> > Hi Simon, Magnus,
> >
> > The KZM-A9-GT and Armadillo-800 EVA boards are now sufficiently
> > supported by DT-based and board-less SH-Mobile AG5 (sh73a0) and R-Mobile
> > A1 (r8a7740) multi-platform kernels.
> >
> > Lacking areas are:
> > - USB (it does't work in legacy, neither),
> > - HDMI on armadillo (it doesn't work in legacy, neither),
> > - Camera on armadillo (we don't care),
> >
> > - LCDC:
> > - on armadillo, this is supported by the board staging code,
> > - on kzm9g, the LCDC is wired to the legacy INTC, which is not
> >
> > planned to be supported with DT,
> >
> > - DMAC/IPMMU (no DT bindings are planned).
> >
> > Hence this patch series removes legacy board and SoC code for
> > sh73a0/kzm9g and r8a7740/armadillo.
> >
> > It consists of 4 parts:
> > - Patches 1-4 remove legacy support for kzm9g (board code, defconfig,
> >
> > dtb) and sh73a0,
> >
> > - Patches 5-8 remove legacy support for armadillo (board code,
> >
> > defconfig, dtb) and r8a7740,
> >
> > - Patches 9-11 remove generic shmobile support code (dma-register.h,
> >
> > legacy PM Domains, zboot) that became unused by the removal of
> > legacy sh73a0/kzm9g and r8a7740/armadillo,
> >
> > - Patches 12-15 remove legacy sh73a0 and r8a7740 support in the
> >
> > pinctrl drivers.
> >
> > Dependencies:
> > - This is against next-20150617,
> > - To keep up with existing LCDC functionality for armadillo-legacy,
> >
> > the r8a7740/armadillo part (and later parts) depends on "[PATCH v2
> > 0/7] staging: board: armadillo800eva: Board staging for
> > sh_mobile_lcdc_fb" (https://lkml.org/lkml/2015/6/17/115).
> > However, it can be applied as-is now, and board staging can he
> > handled in parallel (if at all).
> >
> > Thanks for applying!
> >
> > Geert Uytterhoeven (15):
> > ARM: shmobile: Remove legacy board code for KZM-A9-GT
> > ARM: shmobile: Remove legacy kzm9g_defconfig
> > ARM: shmobile: Drop sh73a0-kzm9g.dtb for legacy builds
> > ARM: shmobile: Remove legacy SoC code for SH-Mobile AG5
> > ARM: shmobile: Remove legacy board code for Armadillo-800 EVA
> > ARM: shmobile: Remove legacy armadillo800eva_defconfig
> > ARM: shmobile: Drop r8a7740-armadillo800eva.dtb for legacy builds
> > ARM: shmobile: Remove legacy SoC code for R-Mobile A1
> > ARM: shmobile: Remove unused dma-register.h
> > ARM: shmobile: R-Mobile: Remove legacy PM Domain code
> > ARM: shmobile: Remove obsolete zboot support
>
> I have queued up the above patches for v4.3.
>
> > pinctrl: sh-pfc: sh73a0: Remove obsolete multi-platform check
> > pinctrl: sh-pfc: Remove obsolete sh73a0 platform_device_id entry
> > pinctrl: sh-pfc: r8a7740: Remove obsolete multi-platform check
> > pinctrl: sh-pfc: Remove obsolete r8a7740 platform_device_id entry
>
> As the above patches are sh-pfc patches they would typically
> be steered through Linus's tree via Laurent. If they wish
> to take that path then I'm happy for this to be attached:
>
> Acked-by: Simon Horman <horms+renesas@verge.net.au>
And
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> FWIW the above path is the one that the removal of mackerel/sh7372 took.
>
> Alternatively, I am happy to take the above sh-pfc patches through
> my tree but I would like to do so with an Ack from at least Linus.
I'm fine with both. I think it would be easier to applied them through your
tree if Linus is fine with that. Those patches shouldn't generate any
conflict.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2015-06-19 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1434533491-21979-1-git-send-email-geert+renesas@glider.be>
2015-06-19 3:41 ` [PATCH 00/15] ARM: shmobile: Remove legacy sh73a0/kzm9g and r8a7740/armadillo Simon Horman
2015-06-19 7:30 ` Geert Uytterhoeven
2015-06-19 8:17 ` Simon Horman
2015-07-13 10:00 ` Linus Walleij
2015-07-13 10:06 ` Geert Uytterhoeven
2015-06-19 9:05 ` Laurent Pinchart [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2048890.5QyZKokOfh@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=arnd@arndb.de \
--cc=damm+renesas@opensource.se \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).