Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/5] dmaengine: allow sun6i-dma for more SoCs
Date: Thu, 24 Nov 2016 11:55:16 +0100	[thread overview]
Message-ID: <20161124105516.tv2ybfgka5teiv2h@lukather> (raw)
In-Reply-To: <CAGb2v65G7=9ah+sEet=z5vss60kL5ZLSkNsAcGpwu8V6AWdEGA@mail.gmail.com>

On Thu, Nov 24, 2016 at 05:30:45PM +0800, Chen-Yu Tsai wrote:
> On Thu, Nov 24, 2016 at 5:16 PM, Andre Przywara <andre.przywara@arm.com> wrote:
> > Hi,
> >
> > On 24/11/16 04:16, Chen-Yu Tsai wrote:
> >> Hi,
> >>
> >> On Thu, Nov 24, 2016 at 9:17 AM, Andre Przywara <andre.przywara@arm.com> wrote:
> >>> The sun6i DMA driver is used in the Allwinner A64 and H5 SoC, which
> >>> have arm64 capable cores. Add the generic sunxi config symbol to allow
> >>> the driver to be selected by arm64 Kconfigs, which don't feature
> >>> SoC specific MACH_xxxx configs.
> >>>
> >>> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> >>> ---
> >>>  drivers/dma/Kconfig | 2 +-
> >>>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>> diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
> >>> index af63a6b..003c284 100644
> >>> --- a/drivers/dma/Kconfig
> >>> +++ b/drivers/dma/Kconfig
> >>> @@ -157,7 +157,7 @@ config DMA_SUN4I
> >>>
> >>>  config DMA_SUN6I
> >>>         tristate "Allwinner A31 SoCs DMA support"
> >>> -       depends on MACH_SUN6I || MACH_SUN8I || COMPILE_TEST
> >>> +       depends on MACH_SUN6I || MACH_SUN8I || COMPILE_TEST || ARCH_SUNXI
> >>
> >> AFAIK ARCH_SUNXI encompasses/supersedes MACH_SUN*I.
> >> (And I don't have to add MACH_SUN9I later :) )
> >
> > Sure, admittedly it was just a quick hack to get things going.
> > Actually I don't know why we had a *depend* on those MACH_s before. I
> > think technically it does not depend on a certain SoC (having the
> > COMPILE_TEST in there hints on that). So what about:
> 
> It was really because this DMA engine only comes with the later
> SoCs. We have dma-sun4i for the older one.

Indeed.

> But yes, there's no reason why you can't build it for the earlier
> SoC. It just doesn't get used.

I'm still in favor of keeping the depends on. There's no point of
compiling something we know have zero chance of running.

(But that would be (ARCH_SUNXI && ARM64))

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161124/a116f60d/attachment.sig>

  parent reply	other threads:[~2016-11-24 10:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24  1:17 [RFC PATCH 0/5] arm64: Allwinner H5 support Andre Przywara
2016-11-24  1:17 ` [RFC PATCH 1/5] arm: dts: sun8i: split Allwinner H3 .dtsi Andre Przywara
2016-11-24  1:17 ` [RFC PATCH 2/5] dmaengine: allow sun6i-dma for more SoCs Andre Przywara
2016-11-24  4:16   ` Chen-Yu Tsai
2016-11-24  9:16     ` Andre Przywara
2016-11-24  9:30       ` Chen-Yu Tsai
2016-11-24 10:12         ` Andre Przywara
2016-11-24 10:55         ` Maxime Ripard [this message]
2016-11-24 11:15           ` Andre Przywara
2016-11-24 20:44             ` Maxime Ripard
2016-11-24  1:17 ` [RFC PATCH 3/5] arm64: defconfig: sunxi: include options for Allwinner H5 SoC Andre Przywara
2016-11-24 10:57   ` Maxime Ripard
2016-11-24 11:01     ` Chen-Yu Tsai
2016-11-24 11:09       ` Andre Przywara
2016-11-24  1:17 ` [RFC PATCH 4/5] arm64: dts: sunxi: add Allwinner H5 .dtsi Andre Przywara
2016-11-24  1:17 ` [RFC PATCH 5/5] arm64: dts: sunxi: add support for the Orange Pi PC 2 board Andre Przywara
2016-11-24 10:59 ` [RFC PATCH 0/5] arm64: Allwinner H5 support Maxime Ripard
2016-11-24 11:05   ` Andre Przywara
2016-11-24 17:03     ` [linux-sunxi] " Ian Campbell

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=20161124105516.tv2ybfgka5teiv2h@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox