linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gregory.clement@bootlin.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: armada388-clearfog: enable spi flash
Date: Thu, 28 Jun 2018 13:38:22 +0200	[thread overview]
Message-ID: <87o9fv6t01.fsf@bootlin.com> (raw)
In-Reply-To: <20180628111318.GF17271@n2100.armlinux.org.uk> (Russell King's message of "Thu, 28 Jun 2018 12:13:18 +0100")

Hi Russell King,
 
 On jeu., juin 28 2018, Russell King - ARM Linux <linux@armlinux.org.uk> wrote:

> On Thu, Jun 28, 2018 at 01:47:30PM +0300, Baruch Siach wrote:
>> Hi Russell,
>> 
>> On Thu, Jun 28, 2018 at 11:33:20AM +0100, Russell King - ARM Linux wrote:
>> > On Thu, Jun 28, 2018 at 01:07:59PM +0300, Baruch Siach wrote:
>> > > Thanks for reviewing.
>> > > 
>> > > On Thu, Jun 28, 2018 at 10:51:14AM +0100, Russell King - ARM Linux wrote:
>> > > > On Thu, Jun 28, 2018 at 10:13:35AM +0300, Baruch Siach wrote:
>> > > > > The SolidRun Armada 388 SOM has the SPI flash populated by default
>> > > > > unless the customer explicitly asks otherwise. Enable support by
>> > > > > default.
>> > > > 
>> > > > Are you sure about that - at least some of my boards do not have the
>> > > > SPI flash populated.
>> > > > 
>> > > > &spi1 {
>> > > >         /* The microsom has an optional W25Q32 on board, connected to CS0 */
>> > > > ...
>> > > > &spi1 {
>> > > >         /*
>> > > >          * Add SPI CS pins for clearfog:
>> > > >          * CS0: W25Q32 (not populated on uSOM)
>> > > 
>> > > I should update this line as well, I guess.
>> > > 
>> > > >          * CS1: PIC microcontroller (Pro models)
>> > > >          * CS2: mikrobus
>> > > >          */
>> > > > 
>> > > > I wouldn't have written "not populated on uSOM" without having first
>> > > > taken the uSOM off and physically checked.
>> > > 
>> > > Are these production SOMs or development/engineering samples?
>> > 
>> > I don't remember.
>> > 
>> > > Ilya Viten from the SolidRun commercial department told me that all production 
>> > > SOMs that were shipped to customers have the SPI flash populated.
>> > 
>> > Yes, Jon confirms that.
>> > 
>> > > This is just the default value for the common case.
>> > 
>> > Has it been tested with boards that don't have the SPI flash populated?
>> > That needs to happen to make sure that this doesn't cause a regression.
>> 
>> I don't have such a SOM handy. I can try to "produce" one next week.
>> 
>> I tested a modified DT with the 'reg' property set to 1 to simulate an 
>> unpopulated SPI flash. The driver probe seems to fail gracefully:
>> 
>>   m25p80 spi1.1: unrecognized JEDEC id bytes: ff, ff, ff
>> 
>> Is this test sufficient to ensure the safety of this patch?
>
> Yes, that's fine, thanks for checking.
>
> Acked-by: Russell King <rmk+kernel@armlinux.org.uk>
>
> Gregory, please add my acked-by to your hasty commit, thanks.

Done!

Thanks,

Gregory

>
> -- 
> RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
> FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
> According to speedtest.net: 8.21Mbps down 510kbps up

-- 
Gregory Clement, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com

      reply	other threads:[~2018-06-28 11:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28  7:13 [PATCH 1/2] ARM: dts: armada388-clearfog: enable spi flash Baruch Siach
2018-06-28  7:13 ` [PATCH 2/2] ARM: dts: armada388-clearfog: drop future changes disclaimer Baruch Siach
2018-06-28  8:22   ` Andrew Lunn
2018-06-28  8:33     ` Jon Nettleton
2018-06-28  8:47       ` Andrew Lunn
2018-06-28  9:11   ` Andrew Lunn
2018-06-28  9:33   ` Gregory CLEMENT
2018-06-28  9:31 ` [PATCH 1/2] ARM: dts: armada388-clearfog: enable spi flash Gregory CLEMENT
2018-06-28  9:52   ` Russell King - ARM Linux
2018-06-28  9:56     ` Gregory CLEMENT
2018-06-28  9:51 ` Russell King - ARM Linux
2018-06-28 10:07   ` Baruch Siach
2018-06-28 10:33     ` Russell King - ARM Linux
2018-06-28 10:47       ` Baruch Siach
2018-06-28 11:13         ` Russell King - ARM Linux
2018-06-28 11:38           ` Gregory CLEMENT [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=87o9fv6t01.fsf@bootlin.com \
    --to=gregory.clement@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).