From: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: christophe leroy <christophe.leroy-GgN8y9CXRhA@public.gmane.org>
Cc: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
<linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2 2/2] spi: fsl-spi: Allow dynamic allocation of CPM1 parameter RAM
Date: Mon, 6 Oct 2014 19:24:10 -0500 [thread overview]
Message-ID: <1412641450.13320.509.camel@snotra.buserror.net> (raw)
In-Reply-To: <542FC6CC.4000507-GgN8y9CXRhA@public.gmane.org>
On Sat, 2014-10-04 at 12:07 +0200, christophe leroy wrote:
> The bindings for that driver are described in
> Documentation/devicetree/bindings/spi/fsl-spi.txt. But it seems that it
> doesn't describe anything related to those compatibles. The driver has a
> match on "fsl,fsl-spi" only,
I think you mean "fsl,spi", and that's a terrible compatible name.
> and for using it with CPM you have to add
> "fsl,cpm1-spi" or "fsl,cpm2-spi" to tell the driver that it is CPM
> (existing code below).
fsl-spi.txt doesn't describe CPM1/2 at all, but rather QE (CPM3) and
non-CPM.
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-10-07 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 16:49 [PATCH v2 2/2] spi: fsl-spi: Allow dynamic allocation of CPM1 parameter RAM Christophe Leroy
2014-10-03 19:51 ` Scott Wood
[not found] ` <1412365908.13320.429.camel-88ow+0ZRuxG2UiBs7uKeOtHuzzzSOjJt@public.gmane.org>
2014-10-04 10:07 ` christophe leroy
[not found] ` <542FC6CC.4000507-GgN8y9CXRhA@public.gmane.org>
2014-10-07 0:24 ` Scott Wood [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=1412641450.13320.509.camel@snotra.buserror.net \
--to=scottwood-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=christophe.leroy-GgN8y9CXRhA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@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