From: R Sricharan <r.sricharan@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/7] ARM: OMAP4+: Change the PRCM structure prototype common for all Socs
Date: Fri, 1 Feb 2013 12:17:15 +0530 [thread overview]
Message-ID: <510B64F3.8010602@ti.com> (raw)
In-Reply-To: <510A9E73.4040800@ti.com>
On Thursday 31 January 2013 10:10 PM, Tom Rini wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 01/31/2013 12:52 AM, R Sricharan wrote:
>> The current PRCM structure prototype directly matches the hardware
>> register layout. So there is a need to change this for every new
>> silicon revision which has register space changes.
>>
>> Avoiding this by making the prototye generic and populating the
>> register addresses seperately for all Socs.
>>
>> Signed-off-by: R Sricharan <r.sricharan@ti.com>
> [snip]
>> arch/arm/cpu/armv7/omap4/prcm-regs.c | 267 ++++++++++++
>> arch/arm/cpu/armv7/omap5/prcm-regs.c | 278
>> +++++++++++++
>
> These two are missing license information, please fix.
>
Sorry for missing this. Will send a V2
> Otherwise, I like the concept and I think it all looks fine. We stay
> about the same, binary size wise with all of this, correct?
>
Yes,i checked this after the change.The spl size for OMAP4 is still
29KB and less than the limit (32KB). The size is never an issue with OMAP5
Regards,
Sricharan
next prev parent reply other threads:[~2013-02-01 6:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 5:51 [U-Boot] [PATCH 0/7] ARM: OMAP4+: Cleanup clocks, control and emif code R Sricharan
2013-01-31 5:51 ` [U-Boot] [PATCH 1/7] ARM: OMAP4+: emif: Detect SDRAM from SDRAM config register R Sricharan
2013-01-31 16:29 ` Tom Rini
2013-02-01 6:30 ` R Sricharan
2013-02-01 14:37 ` Tom Rini
2013-01-31 5:52 ` [U-Boot] [PATCH 2/7] ARM: OMAP4+: Change the PRCM structure prototype common for all Socs R Sricharan
2013-01-31 16:40 ` Tom Rini
2013-02-01 6:47 ` R Sricharan [this message]
2013-01-31 5:52 ` [U-Boot] [PATCH 3/7] ARM: OMAP4+: Cleanup the clocks layer R Sricharan
2013-01-31 16:42 ` Tom Rini
2013-01-31 5:52 ` [U-Boot] [PATCH 4/7] ARM: OMAP4+: Clean up the pmic code R Sricharan
2013-01-31 17:01 ` Tom Rini
2013-02-01 6:49 ` R Sricharan
2013-01-31 5:52 ` [U-Boot] [PATCH 5/7] ARM: OMAP4+: Cleanup emif specific files R Sricharan
2013-01-31 17:03 ` Tom Rini
2013-01-31 5:52 ` [U-Boot] [PATCH 6/7] ARM: OMAP4+: Make control module register structure generic R Sricharan
2013-01-31 17:05 ` Tom Rini
2013-01-31 5:52 ` [U-Boot] [PATCH 7/7] ARM: OMAP5: Clean up iosettings code R Sricharan
2013-01-31 17:06 ` Tom Rini
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=510B64F3.8010602@ti.com \
--to=r.sricharan@ti.com \
--cc=u-boot@lists.denx.de \
/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