From: thomas.petazzoni@free-electrons•com (Thomas Petazzoni)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] dma: mv_xor_v2: new driver
Date: Mon, 15 Feb 2016 11:58:34 +0100 [thread overview]
Message-ID: <20160215115834.60f4e559@free-electrons.com> (raw)
In-Reply-To: <56C1A17F.9030206@arm.com>
Hello,
On Mon, 15 Feb 2016 09:59:27 +0000, Marc Zyngier wrote:
> Seems like something is selecting GENERIC_MSI_IRQ_DOMAIN on a system
> that doesn't implement the required bits.
>
> It may be that we need to implement something like
> HAS_GENERIC_MSI_IRQ_DOMAIN, and make GENERIC_MSI_IRQ_DOMAIN conditional
> on that. Or just whitelist the architectures that do implement this.
>
> Any chance you could have a closer look?
I'll have a look. However, in the mean time, I will probably make this
new driver depend on ARM64 so that it does not depend on other patches
touching the MSI mechanism.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-15 10:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 7:58 [PATCH] dma: mv_xor_v2: new driver Thomas Petazzoni
2016-02-15 9:09 ` kbuild test robot
2016-02-15 9:50 ` Thomas Petazzoni
2016-02-15 9:59 ` Marc Zyngier
2016-02-15 10:58 ` Thomas Petazzoni [this message]
2016-02-15 9:34 ` kbuild test robot
2016-02-15 9:34 ` [PATCH] dma: mv_xor_v2: fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-02-15 9:56 ` [PATCH] dma: mv_xor_v2: new driver kbuild test robot
2016-02-22 2:53 ` Rob Herring
2016-02-22 7:21 ` Thomas Petazzoni
2016-02-22 20:02 ` Rob Herring
2016-02-22 3:27 ` Vinod Koul
2016-02-22 9:16 ` Thomas Petazzoni
2016-02-22 19:58 ` Rob Herring
2016-02-23 3:02 ` Vinod Koul
2016-06-15 14:08 ` Thomas Petazzoni
2016-06-15 16:41 ` Vinod Koul
2016-06-16 12:42 ` Thomas Petazzoni
2016-06-17 2:39 ` Vinod Koul
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=20160215115834.60f4e559@free-electrons.com \
--to=thomas.petazzoni@free-electrons$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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