From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] spi: kirkwood_spi: Add support for multiple chip-selects on MVEBU
Date: Wed, 6 Apr 2016 14:31:37 +0200 [thread overview]
Message-ID: <570501A9.5030005@denx.de> (raw)
In-Reply-To: <CAD6G_RSPc2vXYBke_ywy7x1oHMpD2xf5eS_XkHFeC-6AOt_A+g@mail.gmail.com>
On 06.04.2016 14:25, Jagan Teki wrote:
> On 6 April 2016 at 17:24, Stefan Roese <sr@denx.de> wrote:
>> Currently only chip-select 0 is supported by the kirkwood SPI driver.
>> The Armada XP / 38x SoCs also use this driver and support multiple chip
>> selects. This patch adds support for multiple CS on MVEBU.
>>
>> The register definitions are restructured a bit with this patch. Grouping
>> them to the corresponding registers.
>>
>> Signed-off-by: Stefan Roese <sr@denx.de>
>> Cc: Luka Perkov <luka.perkov@sartura.hr>
>> Cc: Jagan Teki <jteki@openedev.com>
>> ---
>> v3:
>> - Remove unnecessary #ifdef
>
> Does this mean dm for this driver will operate only for MVEBU now?
Not sure. The Kirkwood platform has not been ported to DM yet. But
I can't see anything right now that should prevent Kirkwood to
using this driver also once its ported to DM. Not sure why I had
this #ifdef in this patch - its been a while since I first started
this patch.
Are you okay with this patch now? If yes, should I push it via the
Marvell repository?
Thanks,
Stefan
next prev parent reply other threads:[~2016-04-06 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 11:54 [U-Boot] [PATCH v3] spi: kirkwood_spi: Add support for multiple chip-selects on MVEBU Stefan Roese
2016-04-06 12:25 ` Jagan Teki
2016-04-06 12:31 ` Stefan Roese [this message]
2016-04-06 13:31 ` Jagan Teki
2016-04-06 13:43 ` Stefan Roese
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=570501A9.5030005@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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