From: Marcus Weseloh <mweseloh42@gmail.com>
To: linux-sunxi@googlegroups.com
Cc: Marcus Weseloh <mweseloh42@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Mark Brown <broonie@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: [PATCH] spi: dts: sun4i: Add support for inter-word wait cycles
Date: Thu, 19 Nov 2015 16:53:41 +0100 [thread overview]
Message-ID: <1447948422-4915-1-git-send-email-mweseloh42@gmail.com> (raw)
Hi all,
the Allwinner A10/A20 SPI module supports an option to configure a number of
clock periods to wait between each word ("SPI Wait Clock Register" in the A20
manual). This is a very useful option if talking to devices which specify a
minimum amount of inter-word wait time.
I initially tried to find a way to let SPI protocol drivers specify this
option, but I couldn't find a mechanism to pass additional options to the spi
master. So I took the spi-davinci driver as an example (it implements a very
similiar functionality) and added a new devicetree property.
While testing this patch I noticed that the SPI module always adds a constant
3 clock cycles to the number set in the Wait Clock Register. That number stays
constant across many different baud rates, so I documented it in the
devicetree binding file.
One thing I am unsure of is the device example in the binding
documentation. I used "example,dummy" as compatible... is this acceptable or
should I use a device/compatible that actually exists somewhere?
Oh... and should I split binding documentation and code changing patch?
Best regards,
Marcus
Marcus Weseloh (1):
spi: dts: sun4i: Add support for inter-word wait cycles using the SPI
Wait Clock Register
Documentation/devicetree/bindings/spi/spi-sun4i.txt | 11 +++++++++++
drivers/spi/spi-sun4i.c | 7 +++++++
2 files changed, 18 insertions(+)
--
1.9.1
next reply other threads:[~2015-11-19 15:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 15:53 Marcus Weseloh [this message]
2015-11-19 15:53 ` [PATCH] spi: dts: sun4i: Add support for inter-word wait cycles using the SPI Wait Clock Register Marcus Weseloh
2015-11-19 22:59 ` [linux-sunxi] " Julian Calaby
2015-11-20 8:45 ` Marcus Weseloh
2015-11-20 10:12 ` Julian Calaby
2015-11-20 13:56 ` Marcus Weseloh
2015-11-20 16:12 ` Rob Herring
2015-11-20 16:45 ` Marcus Weseloh
2015-11-22 19:45 ` Maxime Ripard
2015-11-23 9:14 ` Marcus Weseloh
2015-11-20 16:03 ` Rob Herring
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=1447948422-4915-1-git-send-email-mweseloh42@gmail.com \
--to=mweseloh42@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®