From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: "tony@atomide.com" <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"bcousson@baylibre.com" <bcousson@baylibre.com>,
Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 0/2] OMAP4+: Get rid of internal SRAM handling
Date: Wed, 28 Aug 2013 10:46:15 -0400 [thread overview]
Message-ID: <521E0D37.3010909@ti.com> (raw)
In-Reply-To: <521DFE5D.8070000@ti.com>
On Wednesday 28 August 2013 09:42 AM, Rajendra Nayak wrote:
> On Wednesday 28 August 2013 07:08 PM, Santosh Shilimkar wrote:
>> On Wednesday 28 August 2013 02:29 AM, Nayak, Rajendra wrote:
>>> On Tuesday 27 August 2013 06:55 PM, Santosh Shilimkar wrote:
>>>> + Paul,
>>>>
>>>> On Tuesday 27 August 2013 06:11 AM, Rajendra Nayak wrote:
>>>>> Make all OMAP DT only platforms (am33xx, am43xx, omap4 and omap5)
>>>>> use drivers/misc/sram.c driver instead of the omap internal
>>>>> implementation for SRAM handling.
>>>>>
>>>>> Rajendra Nayak (2):
>>>>> ARM: AM335x: Get rid of unused sram init function
>>>>> ARM: OMAP4+: Move SRAM data to DT
>>>>>
>>>>> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
>>>>> arch/arm/boot/dts/am4372.dtsi | 5 +++++
>>>>> arch/arm/boot/dts/omap4.dtsi | 5 +++++
>>>>> arch/arm/boot/dts/omap5.dtsi | 5 +++++
>>>>> arch/arm/configs/omap2plus_defconfig | 1 +
>>>>> arch/arm/mach-omap2/sram.c | 39 +---------------------------------
>>>>> arch/arm/mach-omap2/sram.h | 1 -
>>>>> 7 files changed, 22 insertions(+), 39 deletions(-)
>>>>>
>>>> Really nice to see the SRAM code getting moved now. Thanks
>>>> a lot Rajendra.
>>>>
>>>> - The sram_init() seems to be the post core init call.
>>>> Hope this is not a problem for SDRC init which needs to have
>>>> SRAM ready to update the DDR parameters.
>>>
>>> It should be fine given its needed only during core dvfs. Besides
>>> drivers/misc/sram.c is useful only on DT platforms, so for now OMAP2/3
>>> continue to use the omap specific sram handling.
>>>
>> Its used in early boot to initialize the DDR parameters and then
>> later these can be used based on whether core DVFS supported or
>> not. Look for _omap2_init_reprogram_sdrc() which has init
>> dependency with omap_sram_init().
>
> Right, I see that now. With this series (which addresses only DT platforms)
> we would still be fine with the omap2/3 sdrc usage.
>
Yep. When OMAP3 becomes DT only then this could become problem. Actually
the SDRC init can be moved bit further down to solve that one as well so
should be ok I guess.
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] OMAP4+: Get rid of internal SRAM handling
Date: Wed, 28 Aug 2013 10:46:15 -0400 [thread overview]
Message-ID: <521E0D37.3010909@ti.com> (raw)
In-Reply-To: <521DFE5D.8070000@ti.com>
On Wednesday 28 August 2013 09:42 AM, Rajendra Nayak wrote:
> On Wednesday 28 August 2013 07:08 PM, Santosh Shilimkar wrote:
>> On Wednesday 28 August 2013 02:29 AM, Nayak, Rajendra wrote:
>>> On Tuesday 27 August 2013 06:55 PM, Santosh Shilimkar wrote:
>>>> + Paul,
>>>>
>>>> On Tuesday 27 August 2013 06:11 AM, Rajendra Nayak wrote:
>>>>> Make all OMAP DT only platforms (am33xx, am43xx, omap4 and omap5)
>>>>> use drivers/misc/sram.c driver instead of the omap internal
>>>>> implementation for SRAM handling.
>>>>>
>>>>> Rajendra Nayak (2):
>>>>> ARM: AM335x: Get rid of unused sram init function
>>>>> ARM: OMAP4+: Move SRAM data to DT
>>>>>
>>>>> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
>>>>> arch/arm/boot/dts/am4372.dtsi | 5 +++++
>>>>> arch/arm/boot/dts/omap4.dtsi | 5 +++++
>>>>> arch/arm/boot/dts/omap5.dtsi | 5 +++++
>>>>> arch/arm/configs/omap2plus_defconfig | 1 +
>>>>> arch/arm/mach-omap2/sram.c | 39 +---------------------------------
>>>>> arch/arm/mach-omap2/sram.h | 1 -
>>>>> 7 files changed, 22 insertions(+), 39 deletions(-)
>>>>>
>>>> Really nice to see the SRAM code getting moved now. Thanks
>>>> a lot Rajendra.
>>>>
>>>> - The sram_init() seems to be the post core init call.
>>>> Hope this is not a problem for SDRC init which needs to have
>>>> SRAM ready to update the DDR parameters.
>>>
>>> It should be fine given its needed only during core dvfs. Besides
>>> drivers/misc/sram.c is useful only on DT platforms, so for now OMAP2/3
>>> continue to use the omap specific sram handling.
>>>
>> Its used in early boot to initialize the DDR parameters and then
>> later these can be used based on whether core DVFS supported or
>> not. Look for _omap2_init_reprogram_sdrc() which has init
>> dependency with omap_sram_init().
>
> Right, I see that now. With this series (which addresses only DT platforms)
> we would still be fine with the omap2/3 sdrc usage.
>
Yep. When OMAP3 becomes DT only then this could become problem. Actually
the SDRC init can be moved bit further down to solve that one as well so
should be ok I guess.
Regards,
Santosh
next prev parent reply other threads:[~2013-08-28 14:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 10:11 [PATCH 0/2] OMAP4+: Get rid of internal SRAM handling Rajendra Nayak
2013-08-27 10:11 ` Rajendra Nayak
2013-08-27 10:11 ` [PATCH 1/2] ARM: AM335x: Get rid of unused sram init function Rajendra Nayak
2013-08-27 10:11 ` Rajendra Nayak
2013-08-27 16:06 ` Dave Gerlach
2013-08-27 16:06 ` Dave Gerlach
2013-08-28 6:17 ` Rajendra Nayak
2013-08-28 6:17 ` Rajendra Nayak
2013-08-27 10:11 ` [PATCH 2/2] ARM: OMAP4+: Move SRAM data to DT Rajendra Nayak
2013-08-27 10:11 ` Rajendra Nayak
2013-08-27 11:23 ` Sekhar Nori
2013-08-27 11:23 ` Sekhar Nori
2013-08-28 6:23 ` Rajendra Nayak
2013-08-28 6:23 ` Rajendra Nayak
2013-08-28 10:24 ` Sekhar Nori
2013-08-28 10:24 ` Sekhar Nori
2013-08-29 11:02 ` Rajendra Nayak
2013-08-29 11:02 ` Rajendra Nayak
2013-09-03 13:56 ` Russ Dill
2013-09-03 13:56 ` Russ Dill
2013-09-03 14:35 ` Lucas Stach
2013-09-03 14:35 ` Lucas Stach
2013-09-03 15:07 ` Russ Dill
2013-09-03 15:07 ` Russ Dill
2013-08-27 13:25 ` [PATCH 0/2] OMAP4+: Get rid of internal SRAM handling Santosh Shilimkar
2013-08-27 13:25 ` Santosh Shilimkar
2013-08-28 6:29 ` Rajendra Nayak
2013-08-28 6:29 ` Rajendra Nayak
2013-08-28 13:38 ` Santosh Shilimkar
2013-08-28 13:38 ` Santosh Shilimkar
2013-08-28 13:42 ` Rajendra Nayak
2013-08-28 13:42 ` Rajendra Nayak
2013-08-28 14:46 ` Santosh Shilimkar [this message]
2013-08-28 14:46 ` Santosh Shilimkar
2013-10-08 18:34 ` Tony Lindgren
2013-10-08 18:34 ` Tony Lindgren
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=521E0D37.3010909@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=bcousson@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=tony@atomide.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.