From: gregory.clement@free-electrons•com (Gregory CLEMENT)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v6] spi: orion.c: Add direct access mode
Date: Thu, 16 Jun 2016 11:23:08 +0200 [thread overview]
Message-ID: <87d1nhbi83.fsf@free-electrons.com> (raw)
In-Reply-To: <5717715D.6030701@denx.de> (Stefan Roese's message of "Wed, 20 Apr 2016 14:09:01 +0200")
Hi Stefan,
On mer., avril 20 2016, Stefan Roese <sr@denx•de> wrote:
>> As you don't submit any patch for the dtsi, I assume that you expect
>> that this part will be done at board level. In this case as I wrote
>> above we are sure that all the board continue working without any need
>> to test them.
>
> No, this won't work without any changes to the Armada dtsi /
> dts files. As the SPI controller node needs to get moved
> for this 'reg' property to work (suggestion from Arnd).
>
> I've submitted 2 patches for the dtsi / dts files a short while
> ago:
>
> http://www.spinics.net/lists/arm-kernel/msg495524.html
> http://www.spinics.net/lists/arm-kernel/msg495523.html
>
> When this SPI driver patch gets accepted, I'll send an updated
> patchset for the dtsi / dts files.
Unless I am wrong the SPI driver patch got accepted, but I didn't see an
updated patchset for the dtsi / dts files. Did I miss it?
Else would you ming to send them? Then I will be able to apply them on
the mvebu tree.
Thanks,
Gregory
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2016-06-16 9:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 10:11 [PATCH v6] spi: orion.c: Add direct access mode Stefan Roese
2016-04-20 11:58 ` Gregory CLEMENT
2016-04-20 12:09 ` Stefan Roese
2016-06-16 9:23 ` Gregory CLEMENT [this message]
2016-06-16 9:42 ` Stefan Roese
2016-05-02 6:47 ` Stefan Roese
2016-05-02 7:28 ` Arnd Bergmann
2016-05-02 10:33 ` Stefan Roese
2016-05-02 15:40 ` 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=87d1nhbi83.fsf@free-electrons.com \
--to=gregory.clement@free-electrons$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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