From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/7] ARM: OMAP4+: Cleanup the clocks layer
Date: Thu, 31 Jan 2013 11:42:53 -0500 [thread overview]
Message-ID: <510A9F0D.5010304@ti.com> (raw)
In-Reply-To: <1359611525-19017-4-git-send-email-r.sricharan@ti.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/31/2013 12:52 AM, R Sricharan wrote:
> Currently there is quite a lot of code which is duplicated in the
> clocks code for OMAP 4 and 5 Socs. Avoiding this here by moving the
> clocks data to a SOC specific place and the sharing the common
> code.
>
> This helps in addition of a new Soc with minimal changes.
>
> Signed-off-by: R Sricharan <r.sricharan@ti.com>
Reviewed-by: Tom Rini <trini@ti.com>
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRCp8NAAoJENk4IS6UOR1WTDAP/2u9KQ/Y7eNzHL/yEHPhhuIw
JVXUopXjUk/ZtZWO3pQnb7JrioLqJbjuZfdvDbLxyfzJH5oJGLbQW59tKajS+zLn
sE47/n9bJZ58yF93HQzpqje8w6RfCZ0fgQAuzUg6IG5grTSUShbMNrwZfM4bZG5C
vTz41BUpt2pSb0epb33Q4tc4pz3jgq8FrNFDy7kO63GEGzbeAwxE553/Cylo8AJ/
kVDhNXm2zseGmrf/q4acBL5ryWXjd7WncDIAF8nY/N1nsv4Hcp7G3kykn9oe9zXM
GzX/OUN1R5nJ9aeHBiXhg1195quJAmHI8N4AC1ReeRjkI48Pv0xIT91VsMuvQApe
Rjoh4P/QMUuIJlZgWez0t4waoU9a5N4F/Svx/aRaJ/AgH4KallNoMRVzHvx4W9aT
+nc0GhGuHHdW57iSM2FdNgQc/E0Iu1VG1eNAdooKZcGDpKS1dIGWwfr4PSwP6Plp
QvkDZpBKN2wTqN/e35TA2R9rR6EZmLktB+xRUu4HH1VXpqpf+L+KY4DypTyNDgjz
ApWcC1Irb4617BM2WgbHh81X0XJ+CjAP+tq3RfKzZCl07lXXXjI561L5gXn0PtlH
DNQbmJiRJ7caN3bm6zEnY/Ap2NQ5FGQD4Fd7af9wFhQsFfCiHTqrlUrwMwdwkLJd
UDzXcWPPTvO1uRKyJQls
=fkAc
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-01-31 16:42 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
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 [this message]
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=510A9F0D.5010304@ti.com \
--to=trini@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