All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Figa <tomasz.figa@gmail.com>
To: Sachin Kamat <sachin.kamat@linaro.org>,
	Andreas Oberritter <obi@saftware.de>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>, Tomasz Figa <t.figa@samsung.com>,
	Kukjin Kim <kgene.kim@samsung.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/1] ARM: EXYNOS: Map SYSRAM address through DT
Date: Wed, 05 Mar 2014 16:57:35 +0100	[thread overview]
Message-ID: <5317496F.5050702@gmail.com> (raw)
In-Reply-To: <CAK9yfHw2adag+J1B=te4QvTG-PMJzvbrMe7NwFZsUGJrJFjmSA@mail.gmail.com>



On 05.03.2014 16:36, Sachin Kamat wrote:
> On 5 March 2014 18:56, Andreas Oberritter <obi@saftware.de> wrote:
>> On 05.03.2014 09:23, Sachin Kamat wrote:
>>>> diff --git a/arch/arm/boot/dts/exynos4210-universal_c210.dts b/arch/arm/boot/dts/exynos4210-universal_c210.dts
>>>> index d2e3f5f5916d..3ca3fb6aa5f4 100644
>>>> --- a/arch/arm/boot/dts/exynos4210-universal_c210.dts
>>>> +++ b/arch/arm/boot/dts/exynos4210-universal_c210.dts
>>>> @@ -28,6 +28,11 @@
>>>>                  bootargs = "console=ttySAC2,115200N8 root=/dev/mmcblk0p5 rw rootwait earlyprintk panic=5 maxcpus=1";
>>>>          };
>>>>
>>>> +       sysram@02020000 {
>>                    ^
>>>> +               compatible = "samsung,exynos4210-sysram";
>>>> +               reg = <0x02025000 0x1000>;
>>                            ^
>>>> +       };
>>>> +
>>
>> Shouldn't these two addresses match?
>
> Ideally they should. However in this case, this particular board uses
> older revision
> of the SoC which has a different register address. I did not want to
> create a compatible
> string just for this (exceptional) case alone and hence did it this
> way to override the reg. address.
> Other option was not to have the register address in the node name.

What about overriding status of sysram@02020000 node to "disabled" and 
adding a new sysram@02025000 node in universal C210 dts?

However, I'm still a bit concerned about using such platform and 
use-case specific compatible strings here. SYSRAM is basically a normal 
SRAM memory and usually just some specific areas of it are reserved for 
special purposes.

Best regards,
Tomasz

WARNING: multiple messages have this Message-ID (diff)
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: EXYNOS: Map SYSRAM address through DT
Date: Wed, 05 Mar 2014 16:57:35 +0100	[thread overview]
Message-ID: <5317496F.5050702@gmail.com> (raw)
In-Reply-To: <CAK9yfHw2adag+J1B=te4QvTG-PMJzvbrMe7NwFZsUGJrJFjmSA@mail.gmail.com>



On 05.03.2014 16:36, Sachin Kamat wrote:
> On 5 March 2014 18:56, Andreas Oberritter <obi@saftware.de> wrote:
>> On 05.03.2014 09:23, Sachin Kamat wrote:
>>>> diff --git a/arch/arm/boot/dts/exynos4210-universal_c210.dts b/arch/arm/boot/dts/exynos4210-universal_c210.dts
>>>> index d2e3f5f5916d..3ca3fb6aa5f4 100644
>>>> --- a/arch/arm/boot/dts/exynos4210-universal_c210.dts
>>>> +++ b/arch/arm/boot/dts/exynos4210-universal_c210.dts
>>>> @@ -28,6 +28,11 @@
>>>>                  bootargs = "console=ttySAC2,115200N8 root=/dev/mmcblk0p5 rw rootwait earlyprintk panic=5 maxcpus=1";
>>>>          };
>>>>
>>>> +       sysram at 02020000 {
>>                    ^
>>>> +               compatible = "samsung,exynos4210-sysram";
>>>> +               reg = <0x02025000 0x1000>;
>>                            ^
>>>> +       };
>>>> +
>>
>> Shouldn't these two addresses match?
>
> Ideally they should. However in this case, this particular board uses
> older revision
> of the SoC which has a different register address. I did not want to
> create a compatible
> string just for this (exceptional) case alone and hence did it this
> way to override the reg. address.
> Other option was not to have the register address in the node name.

What about overriding status of sysram at 02020000 node to "disabled" and 
adding a new sysram at 02025000 node in universal C210 dts?

However, I'm still a bit concerned about using such platform and 
use-case specific compatible strings here. SYSRAM is basically a normal 
SRAM memory and usually just some specific areas of it are reserved for 
special purposes.

Best regards,
Tomasz

  reply	other threads:[~2014-03-05 15:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20  6:05 [PATCH 1/1] ARM: EXYNOS: Map SYSRAM address through DT Sachin Kamat
2014-02-20  6:05 ` Sachin Kamat
2014-03-05  8:23 ` Sachin Kamat
2014-03-05  8:23   ` Sachin Kamat
2014-03-05 13:26   ` Andreas Oberritter
2014-03-05 13:26     ` Andreas Oberritter
2014-03-05 15:36     ` Sachin Kamat
2014-03-05 15:36       ` Sachin Kamat
2014-03-05 15:57       ` Tomasz Figa [this message]
2014-03-05 15:57         ` Tomasz Figa

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=5317496F.5050702@gmail.com \
    --to=tomasz.figa@gmail.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=obi@saftware.de \
    --cc=sachin.kamat@linaro.org \
    --cc=t.figa@samsung.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 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.