From: Stefan Roese <sr-ynQEQJNshbs@public.gmane.org>
To: Gregory CLEMENT
<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Thomas Petazzoni
<thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH v6] spi: orion.c: Add direct access mode
Date: Thu, 16 Jun 2016 11:42:46 +0200 [thread overview]
Message-ID: <57627496.10302@denx.de> (raw)
In-Reply-To: <87d1nhbi83.fsf-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Hi Gregory,
On 16.06.2016 11:23, Gregory CLEMENT wrote:
> On mer., avril 20 2016, Stefan Roese <sr-ynQEQJNshbs@public.gmane.org> 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,
Correct. Its in linux-next now.
> but I didn't see an
> updated patchset for the dtsi / dts files. Did I miss it?
No, you didn't miss it.
> Else would you ming to send them? Then I will be able to apply them on
> the mvebu tree.
Its on my list. Thanks for reminding me. I'll get to working on this
next week and will send an updated patch series then.
Thanks,
Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: sr@denx.de (Stefan Roese)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6] spi: orion.c: Add direct access mode
Date: Thu, 16 Jun 2016 11:42:46 +0200 [thread overview]
Message-ID: <57627496.10302@denx.de> (raw)
In-Reply-To: <87d1nhbi83.fsf@free-electrons.com>
Hi Gregory,
On 16.06.2016 11:23, Gregory CLEMENT wrote:
> 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,
Correct. Its in linux-next now.
> but I didn't see an
> updated patchset for the dtsi / dts files. Did I miss it?
No, you didn't miss it.
> Else would you ming to send them? Then I will be able to apply them on
> the mvebu tree.
Its on my list. Thanks for reminding me. I'll get to working on this
next week and will send an updated patch series then.
Thanks,
Stefan
next prev parent reply other threads:[~2016-06-16 9:42 UTC|newest]
Thread overview: 18+ 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 10:11 ` Stefan Roese
[not found] ` <1461147068-4829-1-git-send-email-sr-ynQEQJNshbs@public.gmane.org>
2016-04-20 11:58 ` Gregory CLEMENT
2016-04-20 11:58 ` Gregory CLEMENT
[not found] ` <87k2jswky0.fsf-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2016-04-20 12:09 ` Stefan Roese
2016-04-20 12:09 ` Stefan Roese
[not found] ` <5717715D.6030701-ynQEQJNshbs@public.gmane.org>
2016-06-16 9:23 ` Gregory CLEMENT
2016-06-16 9:23 ` Gregory CLEMENT
[not found] ` <87d1nhbi83.fsf-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2016-06-16 9:42 ` Stefan Roese [this message]
2016-06-16 9:42 ` Stefan Roese
2016-05-02 6:47 ` Stefan Roese
2016-05-02 6:47 ` Stefan Roese
[not found] ` <5726F7F3.9070700-ynQEQJNshbs@public.gmane.org>
2016-05-02 7:28 ` Arnd Bergmann
2016-05-02 7:28 ` Arnd Bergmann
2016-05-02 10:33 ` Stefan Roese
2016-05-02 10:33 ` Stefan Roese
2016-05-02 15:40 ` Mark Brown
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=57627496.10302@denx.de \
--to=sr-ynqeqjnshbs@public.gmane.org \
--cc=andrew-g2DYL2Zd6BY@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.