From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robherring2@gmail.com>
Cc: Alexandre Pereira da Silva <aletes.xgr@gmail.com>,
Roland Stigge <stigge@antcom.de>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Landley <rob@landley.net>,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
spi-devel-general@lists.sourceforge.net,
"Mark Brown (broonie@opensource.wolfsonmicro.com)"
<broonie@opensource.wolfsonmicro.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
sachin.verma@st.co
Subject: Re: [PATCH RESEND v4] spi/pl022: add devicetree support
Date: Mon, 20 Aug 2012 17:09:57 +0200 [thread overview]
Message-ID: <CACRpkdbJkL9bD-hG29LmB1mPAUpg5kwdQEfkMKNV4vRM9Sq87g@mail.gmail.com> (raw)
In-Reply-To: <50324835.6030806@gmail.com>
On Mon, Aug 20, 2012 at 4:22 PM, Rob Herring <robherring2@gmail.com> wrote:
> On 08/20/2012 06:39 AM, Alexandre Pereira da Silva wrote:
>> +- pl022,hierarchy : master or slave interface
>
> Is attaching a master and using the pl022 as a slave really a supported
> use case?
No not currently. People doing this crazy stuff need to have
the kernel with the hard real-time patches and lightening response
first. But it's in the platform data because it's a feature supported by
the hardware.
> The DT spi bindings are really designed for a master node with
> N slave nodes. So there is more general question of how to describe a
> spi controller as a slave. It's not really one I care to answer as the
> Linux spi framework isn't designed to act as a slave.
Currently the code should hardwire this to master and not define
a binding for it I think.
>> +- pl022,slave-tx-disable : disconnect tx line in slave mode
Applies also to this, then.
>> +- pl022,com-mode : polling, interrupt or dma
>> +- pl022,rx-level-trig : Rx FIFO watermark level
>> +- pl022,tx-level-trig : Tx FIFO watermark level
>> +- pl022,ctrl-len : Microwire interface: Control length
>> +- pl022,wait-state : Microwire interface: Wait state
>> +- pl022,duplex : Microwire interface: Full/Half duplex
>
> Most of these properties aren't used anywhere in the kernel other than
> u300 and I'm not sure what to purpose of dummy_chip_info is.
It is used for loopback-testing of the PL022. They're probably
not necessary there either.
> Perhaps
> Linus has some input? I think either they can be decided by the spi
> controller (com-mode, fifo watermark) or should be standard properties
> (microwire settings). I would argue they should be removed if the spi
> framework doesn't have support in a standard way.
Uncertain about this, others would need to comment.
At some point there has been a chip needing these to be set
to some magic values.
Yours,
Linus Walleij
next prev parent reply other threads:[~2012-08-20 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 11:39 [PATCH RESEND v4] spi/pl022: add devicetree support Alexandre Pereira da Silva
2012-08-20 12:58 ` Roland Stigge
2012-08-20 13:07 ` Rob Herring
2012-08-20 14:22 ` Rob Herring
2012-08-20 15:09 ` Linus Walleij [this message]
2012-08-20 15:33 ` Roland Stigge
2012-08-20 15:53 ` Rob Herring
2012-08-20 15:02 ` Linus Walleij
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=CACRpkdbJkL9bD-hG29LmB1mPAUpg5kwdQEfkMKNV4vRM9Sq87g@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=aletes.xgr@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=robherring2@gmail.com \
--cc=sachin.verma@st.co \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=stigge@antcom.de \
--cc=viresh.kumar@linaro.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).