From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: tthayer@opensource.altera.com
Cc: broonie@kernel.org, grant.likely@linaro.org, jkosina@suse.cz,
pawel.moll@arm.com, robh+dt@kernel.org, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, dinguyen@opensource.altera.com,
linux-doc@vger.kernel.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, tthayer.linux@gmail.com,
axel.lin@ingics.com, baruch@tkos.co.il, jg1.han@samsung.com,
galak@codeaurora.org
Subject: Re: [RFC/PATCH 0/2] spi: spi-dw: Select 16b or 32b register access
Date: Wed, 04 Mar 2015 23:02:06 +0200 [thread overview]
Message-ID: <1425502926.14897.187.camel@linux.intel.com> (raw)
In-Reply-To: <1425501075-17081-1-git-send-email-tthayer@opensource.altera.com>
On Wed, 2015-03-04 at 14:31 -0600, tthayer@opensource.altera.com wrote:
> From: Thor Thayer <tthayer@opensource.altera.com>
>
> The Altera Arria10 SoC requires 32 bit accesses to peripherals.
Accordingly to what I can read here [1] the IP block is DW_apb_ssi. So,
I don't see any needs for those patches.
The thing which might be needed is to implement DMA support for that
chip.
[1] http://www.altera.com/literature/hb/arria-10/hps.html
> The
> DesignWare SPI peripheral registers are on 32bit boundaries so this
> patch is minimal. Function pointers are used to select 32bit access
> or 16bit accesses.
>
> Thor Thayer (2):
> dt-binding: spi: spi-dw: Select 16b or 32b access for Designware SPI
> spi: dw-spi: Pointers select 16b vs. 32b DesignWare access
>
> Documentation/devicetree/bindings/spi/spi-dw.txt | 1 +
> drivers/spi/spi-dw-mmio.c | 7 +++-
> drivers/spi/spi-dw.c | 38 +++++++++++++---------
> drivers/spi/spi-dw.h | 10 +++---
> 4 files changed, 35 insertions(+), 21 deletions(-)
>
--
Andy Shevchenko <andriy.shevchenko@intel.com>
Intel Finland Oy
prev parent reply other threads:[~2015-03-04 21:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 20:31 [RFC/PATCH 0/2] spi: spi-dw: Select 16b or 32b register access tthayer-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx
[not found] ` <1425501075-17081-1-git-send-email-tthayer-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
2015-03-04 20:31 ` [RFC/PATCH 1/2] dt-binding: spi: spi-dw: Select 16b or 32b access for Designware SPI tthayer-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx
2015-03-04 20:44 ` [RFC/PATCH 0/2] spi: spi-dw: Select 16b or 32b register access Andy Shevchenko
2015-03-04 22:01 ` Thor Thayer
[not found] ` <54F7809E.2010307-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
2015-03-05 10:43 ` Andy Shevchenko
[not found] ` <1425552233.14897.189.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-03-05 20:41 ` Thor Thayer
2015-03-05 21:54 ` Andy Shevchenko
2015-03-06 23:06 ` Thor Thayer
2015-03-04 20:31 ` [RFC/PATCH 2/2] spi: dw-spi: Pointers select 16b vs. 32b DesignWare access tthayer
2015-03-04 20:55 ` Andy Shevchenko
[not found] ` <1425502525.14897.185.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-03-04 22:07 ` Thor Thayer
2015-03-04 21:02 ` Andy Shevchenko [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=1425502926.14897.187.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=axel.lin@ingics.com \
--cc=baruch@tkos.co.il \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@opensource.altera.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jg1.han@samsung.com \
--cc=jkosina@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=tthayer.linux@gmail.com \
--cc=tthayer@opensource.altera.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;
as well as URLs for NNTP newsgroup(s).