From: Franklin S Cooper Jr <fcooper@ti.com>
To: <linux-spi@vger.kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
Franklin S Cooper Jr <fcooper@ti.com>
Subject: [PATCH 0/4] spi: davinci: Improve prescaler limit support
Date: Tue, 14 Jul 2015 14:45:23 -0500 [thread overview]
Message-ID: <1436903127-6777-1-git-send-email-fcooper@ti.com> (raw)
Currently the prescale limit is treated as a one size fits all value even
though their are differences depending on the SOC. This patchset insures
that the proper prescale limit is used for each platform/SOC.
Franklin S Cooper Jr (4):
spi: davinci: Set prescale value based on register value
spi: davinci: Choose correct pre-scaler limit based on SOC
ARM: davinci: Set proper SPI prescale limit value
ARM: dts: keystone: Add ti,keystone-spi for SPI
.../devicetree/bindings/spi/spi-davinci.txt | 2 +
arch/arm/boot/dts/keystone.dtsi | 6 +--
arch/arm/mach-davinci/devices-da8xx.c | 2 +
arch/arm/mach-davinci/dm355.c | 1 +
arch/arm/mach-davinci/dm365.c | 1 +
drivers/spi/spi-davinci.c | 50 +++++++++++++++++-----
include/linux/platform_data/spi-davinci.h | 1 +
7 files changed, 50 insertions(+), 13 deletions(-)
--
1.9.1
next reply other threads:[~2015-07-14 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 19:45 Franklin S Cooper Jr [this message]
2015-07-14 19:45 ` [PATCH 1/4] spi: davinci: Set prescale value based on register value Franklin S Cooper Jr
2015-07-14 19:45 ` [PATCH 2/4] spi: davinci: Choose correct pre-scaler limit based on SOC Franklin S Cooper Jr
2015-07-14 19:45 ` [PATCH 3/4] ARM: davinci: Set proper SPI prescale limit value Franklin S Cooper Jr
2015-07-14 19:45 ` [PATCH 4/4] ARM: dts: keystone: Add ti,keystone-spi for SPI Franklin S Cooper Jr
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=1436903127-6777-1-git-send-email-fcooper@ti.com \
--to=fcooper@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.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®