From: Mark Brown <broonie@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: addy ke <addy.ke@rock-chips.com>,
"heiko@sntech.de" <heiko@sntech.de>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"huangtao@rock-chips.com" <huangtao@rock-chips.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"yzq@rock-chips.com" <yzq@rock-chips.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"kever.yang@rock-chips.com" <kever.yang@rock-chips.com>,
"zyw@rock-chips.com" <zyw@rock-chips.com>,
"xjq@rock-chips.com" <xjq@rock-chips.com>,
"zhenfu.fang@rock-chips.com" <zhenfu.fang@rock-chips.com>,
"olof@lixom.net" <olof@lixom.net>,
"cf@rock-chips.com" <cf@rock-chips.com>,
"hj@rock-chips.com" <hj@rock-chips.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] documentation: add rockchip spi documentation
Date: Tue, 24 Jun 2014 11:33:36 +0100 [thread overview]
Message-ID: <20140624103336.GG23300@sirena.org.uk> (raw)
In-Reply-To: <20140624101802.GE5856@leverpostej>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
On Tue, Jun 24, 2014 at 11:18:02AM +0100, Mark Rutland wrote:
> On Tue, Jun 24, 2014 at 04:58:43AM +0100, addy ke wrote:
> > +- Board Specific Portion:
> > +
> > + &spi0 {
> > + status = "okay";
> > + spi_test@00 {
> > + compatible = "rockchip,spi_test";
> Huh?
I expect that's just intended as an example of how to set up a device
and they're doing something like use a driver that generates known
patterns. We'd normally omit such examples from the binding document
since it's generic and covered well enough elsehwere.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-06-24 10:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 3:58 [PATCH 0/2] add rockchip spi drive addy ke
2014-06-24 3:58 ` [PATCH 1/2] documentation: add rockchip spi documentation addy ke
2014-06-24 10:18 ` Mark Rutland
2014-06-24 10:32 ` Heiko Stübner
2014-06-24 10:47 ` Mark Rutland
2014-06-24 10:33 ` Mark Brown [this message]
2014-07-01 1:02 ` [PATCH v2 " addy ke
2014-06-24 4:07 ` [PATCH 2/2] spi: add driver for Rockchip RK3xxx SoCs integrated SPI addy ke
2014-06-24 10:56 ` Mark Brown
2014-07-01 1:03 ` [PATCH v2 " addy ke
2014-07-04 18:32 ` Mark Brown
2014-07-05 18:56 ` Jonas Gorski
2014-07-07 1:42 ` addy ke
2014-07-07 7:08 ` Heiko Stübner
2014-07-07 7:21 ` Mark Brown
2014-07-07 7:26 ` Heiko Stübner
2014-07-07 7:16 ` Mark Brown
2014-07-08 1:53 ` [PATCH v3 " Addy Ke
2014-07-08 14:56 ` Mark Brown
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=20140624103336.GG23300@sirena.org.uk \
--to=broonie@kernel.org \
--cc=addy.ke@rock-chips.com \
--cc=cf@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=heiko@sntech.de \
--cc=hj@rock-chips.com \
--cc=huangtao@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=xjq@rock-chips.com \
--cc=yzq@rock-chips.com \
--cc=zhenfu.fang@rock-chips.com \
--cc=zyw@rock-chips.com \
/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