From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH 1/4] ARM: DT: Add SMDKV310 machine with device tree support.
Date: Mon, 7 Feb 2011 16:15:55 +0100 [thread overview]
Message-ID: <201102071615.55652.arnd@arndb.de> (raw)
In-Reply-To: <1296998250-21856-2-git-send-email-thomas.abraham-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
On Sunday 06 February 2011, Thomas Abraham wrote:
> diff --git a/arch/arm/mach-s5pv310/mach-smdkv310-dt.c b/arch/arm/mach-s5pv310/mach-smdkv310-dt.c
> new file mode 100644
> index 0000000..367fdb1
> --- /dev/null
> +++ b/arch/arm/mach-s5pv310/mach-smdkv310-dt.c
> @@ -0,0 +1,101 @@
> +/* linux/arch/arm/mach-s5pv310/mach-smdkv310.c
The file name in the comment doesn't match. I normally recommend not putting
it in the comment at all so you don't need to change it when moving or
copying the file.
A comment along the lines of "s5pv310 platform with device tree enabled" is
more helpful to the reader anyway.
> +static void __init smdkv310_map_io(void)
> +{
> + s5p_init_io(NULL, 0, S5P_VA_CHIPID);
> + s3c24xx_init_clocks(24000000);
> + s3c24xx_init_uarts(smdkv310_uartcfgs, ARRAY_SIZE(smdkv310_uartcfgs));
> +}
There is very little here that is really platform specific, right?
Is this going to increase? If not, it might be good to read out the
data (S5P_VA_CHIPID, 24000000, smdkv310_uartcfgs) from the device tree
as well before passing them down. No need to do it right away, but it
would be good to know the direction in which we're heading.
Maybe add a comment like /* TODO: read these from the device tree */
or similar.
Arnd
next prev parent reply other threads:[~2011-02-07 15:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 13:17 [PATCH 0/4] Add basic device tree support for Samsung's SMDKV310 machine Thomas Abraham
[not found] ` <1296998250-21856-1-git-send-email-thomas.abraham-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-02-06 13:17 ` [PATCH 1/4] ARM: DT: Add SMDKV310 machine with device tree support Thomas Abraham
[not found] ` <1296998250-21856-2-git-send-email-thomas.abraham-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-02-07 6:41 ` Grant Likely
2011-02-07 15:15 ` Arnd Bergmann [this message]
2011-02-06 13:17 ` [PATCH 2/4] ARM: DT: Add a basic dts file for SMDKV310 machine Thomas Abraham
[not found] ` <1296998250-21856-3-git-send-email-thomas.abraham-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-02-07 0:04 ` David Gibson
2011-02-07 19:24 ` Rob Herring
[not found] ` <4D5046DC.8010503-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-02-07 19:34 ` Meador Inge
2011-02-13 6:11 ` Grant Likely
2011-02-07 6:54 ` Grant Likely
2011-02-06 13:17 ` [PATCH 3/4] ARM: DT: Add support for probing platform bus on " Thomas Abraham
2011-02-06 13:17 ` [PATCH 4/4] watchdog: s3c2410: Add support for device tree based probe Thomas Abraham
[not found] ` <1296998250-21856-5-git-send-email-thomas.abraham-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-02-07 19:27 ` Rob Herring
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=201102071615.55652.arnd@arndb.de \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
/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.