From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: Robert Jarzmik <robert.jarzmik-GANU6spQydw@public.gmane.org>,
Daniel Mack <zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] spi: pxa2xx: disallow building on MMP
Date: Tue, 19 Apr 2016 16:06:56 +0100 [thread overview]
Message-ID: <20160419150656.GU3217@sirena.org.uk> (raw)
In-Reply-To: <1461071933-3273163-1-git-send-email-arnd-r2nGTMty4D4@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
On Tue, Apr 19, 2016 at 03:18:20PM +0200, Arnd Bergmann wrote:
> What happens here is that we can enable SPI_PXA2XX when some other
> platform in the same build supports PCI. This normally works because the
> pxa_ssp_request/pxa_ssp_free functions are stubbed out when CONFIG_PXA_SSP
> is disabled. However, we can have PXA_SSP=m when that driver is used by
> the SND_SOC_TTC_DKB audio driver.
> This changes the Kconfig logic to just disallow the pxa2xx SPI
> driver on anything but x86 and pxa.
This doesn't seem like a sane fix, I'd be *very* surprised if Marvell
had created a new SPI controller for the MMP SoCs.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-04-19 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 13:18 [PATCH] spi: pxa2xx: disallow building on MMP Arnd Bergmann
[not found] ` <1461071933-3273163-1-git-send-email-arnd-r2nGTMty4D4@public.gmane.org>
2016-04-19 15:06 ` Mark Brown [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=20160419150656.GU3217@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robert.jarzmik-GANU6spQydw@public.gmane.org \
--cc=zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).