From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 11/12 v2] ARM: shmobile: multiplatform: add Audo DMAC peri peri support on defconfig
Date: Wed, 10 Dec 2014 02:41:01 +0000 [thread overview]
Message-ID: <20141210024056.GA24477@verge.net.au> (raw)
In-Reply-To: <87h9yl2ie3.wl%kuninori.morimoto.gx@gmail.com>
On Wed, Dec 10, 2014 at 12:58:42AM +0000, Kuninori Morimoto wrote:
>
> Hi Simon
>
> > > Is it possible to revert this patch from defconfig ?
> > > Current upstreamed Audio DMAC peri peri driver is based on SH_DMAE_BASE,
> > > but, it breaks DMAEngine handling.
> > >
> > > I fix-uped this issue on below patch, but it is not yet accepted.
> > >
> > > Subject: [PATCH][resend] dmaengine: rcar-audmapp: independent from SH_DMAE_BASE
> > > Date: Fri, 28 Nov 2014 00:17:59 +0000
> > >
> > > Above patches need this order
> > > [1/2] : dmaengine: rcar-audmapp: independent from SH_DMAE_BASE
> > > [2/2] : ARM: shmobile: multiplatform: add Audo DMAC peri peri support on defconfig
> > >
> > > It seems that I2C driver is broken by this patch.
> > > I will re-send it if missing DMAEngine patch was accepted.
> >
> > Hi Morimoto-san,
> >
> > I believe this patch is not present in v3.18 (good) but has been accepted
> > by the ARM SoC maintainers for v3.19 (not so good). In other words its
> > present in arm-soc/for-next and linux-next but not Linus's tree
> > (but may be soon).
> >
> > Would you like me to submit a reversion of a fix-for-v3.19 to the ARM SoC
> > maintainers?
>
> Thank you for your help
> It depends on RCAR-DMAC enable/disable and driver (which want to use DMAEngine).
> But, unfortunately, reverting it from v3.19 is very safety.
Thanks, I think I understand.
I plan to queue-up the following:
From: Simon Horman <horms+renesas@verge.net.au>
[PATCH] Revert "ARM: shmobile: multiplatform: add Audo DMAC peri peri support on defconfig"
This reverts commit 2315f9fce4da7df9362e4baeb5250d14ea48bf63.
Unfortunately enabling RCAR_AUDMAC_PP support this patch breaks dmaengine
support on R-Car Gen2 boards. This should be resolved by driver updates
in v3.20. But v3.19 was too early for this defconfig change.
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/shmobile_defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
index cc67508..302faab 100644
--- a/arch/arm/configs/shmobile_defconfig
+++ b/arch/arm/configs/shmobile_defconfig
@@ -147,7 +147,6 @@ CONFIG_RTC_CLASS=y
CONFIG_RTC_DRV_S35390A=y
CONFIG_DMADEVICES=y
CONFIG_SH_DMAE=y
-CONFIG_RCAR_AUDMAC_PP=y
CONFIG_RCAR_DMAC=y
# CONFIG_IOMMU_SUPPORT is not set
CONFIG_PWM=y
--
2.1.3
next prev parent reply other threads:[~2014-12-10 2:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 0:27 [PATCH 11/12 v2] ARM: shmobile: multiplatform: add Audo DMAC peri peri support on defconfig Kuninori Morimoto
2014-12-08 4:37 ` Kuninori Morimoto
2014-12-09 0:20 ` Simon Horman
2014-12-10 0:58 ` Kuninori Morimoto
2014-12-10 2:41 ` Simon Horman [this message]
2014-12-10 3:51 ` Kuninori Morimoto
2014-12-11 3:23 ` Simon Horman
2014-12-11 3:40 ` Kuninori Morimoto
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=20141210024056.GA24477@verge.net.au \
--to=horms@verge.net.au \
--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