public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Gordon Bos <gordon@bosvangennip.nl>
To: Gregory CLEMENT <gregory.clement@free-electrons.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Russell King <linux@arm.linux.org.uk>,
	devicetree@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
	Jason Cooper <jason@lakedaemon.net>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 1/1] arm: Fix unavailable MTD userland devices on Excito B3 boards
Date: Sat, 07 Feb 2015 16:04:59 +0100	[thread overview]
Message-ID: <54D6299B.70707@bosvangennip.nl> (raw)
In-Reply-To: <54D484D8.8090801@free-electrons.com>

[-- Attachment #1: Type: text/plain, Size: 2831 bytes --]

Hi,

I've had some further discussion on this with another B3 owner.
According to an old patch that Excito corporation built for kernel
version 2.6 the flash memory is in fact a ||Numonyx MP25P16
The driver however must be m25p80.

It would therefore seem cleaner to just correct the driver reference
and leave the label as is. The patch thus becomes:

Signed-off-by: Gordon Bos <gordon@bosvangennip.nl>
---
  arch/arm/boot/dts/kirkwood-b3.dts | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/kirkwood-b3.dts b/arch/arm/boot/dts/kirkwood-b3.dts
index c9247f8..5c6e8d3 100644
--- a/arch/arm/boot/dts/kirkwood-b3.dts
+++ b/arch/arm/boot/dts/kirkwood-b3.dts
@@ -74,7 +74,7 @@
  			m25p16@0 {
  				#address-cells = <1>;
  				#size-cells = <1>;
-				compatible = "st,m25p16";
+				compatible = "st,m25p80";
  				reg = <0>;
  				spi-max-frequency = <40000000>;
  				mode = <0>;
---

Regards,
Gordon Bos


On 02/06/2015 10:09 AM, Gregory CLEMENT wrote:
> Hi Gordon,
>
>
> On 06/02/2015 09:45, Gordon Bos wrote:
>> Excito B3 boards use SPI flash for booting and several userland
>> functions require access to this flash memory, including power down
>> control. However /proc/mtd shows an empty list and the userland
>> tools respond with "device not found".
> The change in arm/boot/dts don't go through the device tree subsystem
> but through the arm-soc one. Especially it it is only a fix and if
> you don't introduce or modifying a binding. For this kind of patch
> you should cc the mvebu maintainers (I added the others one)
>
> However it seems that the get_maintainer.pl script is misleading on this
> point we should maybe be updating the MAINTAINERS file.
>
>> Change driver reference for spi@10600 to M25P80
>>
>> Verified on my own Excito B3
> This change looks OK for me however it is too late to merge it
> and it will be part of the next merge window.
>
> Andrew, as you initially wrote this dts would you have a look on it?
>
> As it is a fix we will also apply to the stable branches. It would
> help if you could tell us since when this bug is present.
>
>
> Thanks,
>
> Gregory
>
>
>> Signed-off-by: Gordon Bos <gordon@bosvangennip.nl>
>> ---
>>   arch/arm/boot/dts/kirkwood-b3.dts | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/kirkwood-b3.dts b/arch/arm/boot/dts/kirkwood-b3.dts
>> index c9247f8..4b1e414 100644
>> --- a/arch/arm/boot/dts/kirkwood-b3.dts
>> +++ b/arch/arm/boot/dts/kirkwood-b3.dts
>> @@ -71,10 +71,10 @@
>>   		spi@10600 {
>>   			status = "okay";
>>   
>> -			m25p16@0 {
>> +			m25p80@0 {
>>   				#address-cells = <1>;
>>   				#size-cells = <1>;
>> -				compatible = "st,m25p16";
>> +				compatible = "st,m25p80";
>>   				reg = <0>;
>>   				spi-max-frequency = <40000000>;
>>   				mode = <0>;
>>
>


[-- Attachment #2: Type: text/html, Size: 3752 bytes --]

  reply	other threads:[~2015-02-07 15:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06  8:45 [PATCH 1/1] arm: Fix unavailable MTD userland devices on Excito B3 boards Gordon Bos
     [not found] ` <1423212311-10793-1-git-send-email-gordon-PMRpws9CsXpfxmBXdGbrbQ@public.gmane.org>
2015-02-06  9:09   ` Gregory CLEMENT
2015-02-07 15:04     ` Gordon Bos [this message]
     [not found]       ` <54D6299B.70707-PMRpws9CsXpfxmBXdGbrbQ@public.gmane.org>
2015-02-07 16:09         ` Andrew Lunn
2015-02-07 17:15           ` Gordon Bos
     [not found]             ` <54D64820.7020002-PMRpws9CsXpfxmBXdGbrbQ@public.gmane.org>
2015-02-07 17:36               ` Andrew Lunn
2015-02-07 18:22                 ` Gordon Bos
     [not found]                   ` <54D657D5.3010709-PMRpws9CsXpfxmBXdGbrbQ@public.gmane.org>
2015-02-07 18:40                     ` Andrew Lunn
2015-02-07 19:59                       ` Gordon Bos
     [not found]                         ` <54D66EB2.2030006-PMRpws9CsXpfxmBXdGbrbQ@public.gmane.org>
2015-02-07 20:25                           ` Andrew Lunn
2015-02-07 16:37         ` Andrew Lunn

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=54D6299B.70707@bosvangennip.nl \
    --to=gordon@bosvangennip.nl \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=gregory.clement@free-electrons.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jason@lakedaemon.net \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.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