From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Default machine include placements
Date: Mon, 25 Jan 2010 12:04:54 +0000 [thread overview]
Message-ID: <20100125120454.GD16340@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100125115344.GS26562@trinity.fluff.org>
On Mon, Jan 25, 2010 at 11:53:44AM +0000, Ben Dooks wrote:
> > I personally think that the proliferation of mach-s* directories for
> > Samsung is becoming a problem in itself - some of these directories
> > contain next to nothing, and others are duplications with minimal
> > changes.
> >
> > For example, the differences between s3c6400 and s3c6410 are minimal,
> > yet they have most of the contained non-board code duplicated.
>
> I would disagree on that, most of the common s3c6400 and s3c6410 is
> contained in plat-s3c64xx with the machine directories containing the
> cpu sepcific initialisation bits, such as the changes in the ARM CLKDIV
> the VIC popuilation and the extra devices that the s3c6410 have.
You may disagree, but my comment was based upon diffing the two
directories, and comparing mach-s3c6400/s3c6400.c with mach-s3c6410/cpu.c:
First, comparing the common files between the two directories:
-char *s3c6400_hsmmc_clksrcs[4] = {
+char *s3c6410_hsmmc_clksrcs[4] = {
...
-void s3c6400_setup_sdhci_cfg_card(struct platform_device *dev,
- void __iomem *r,
- struct mmc_ios *ios,
- struct mmc_card *card)
+
+void s3c6410_setup_sdhci0_cfg_card(struct platform_device *dev,
+ void __iomem *r,
+ struct mmc_ios *ios,
+ struct mmc_card *card)
...
+ /* don't need to alter anything acording to card-type */
+
+ writel(S3C64XX_SDHCI_CONTROL4_DRIVE_9mA, r + S3C64XX_SDHCI_CONTROL4);
+
And s3c6400.c vs cpu.c, taking account of the different prefixes used
for variables and function names (so s3c6410 -> s3c6400):
+#include <plat/s3c6400.h>
+
+/* Initial IO mappings */
+
+static struct map_desc s3c6400_iodesc[] __initdata = {
+};
+
+/* s3c6400_map_io
+ *
+ * register the standard cpu IO areas
+*/
...
- /* setup SDHCI */
+ iotable_init(s3c6400_iodesc, ARRAY_SIZE(s3c6400_iodesc));
+ /* initialise device information early */
...
+ s3c_i2c1_setname("s3c2440-i2c");
...
- s3c6400_register_clocks(S3C6400_CLKDIV0_ARM_MASK);
+ s3c6400_register_clocks(S3C6410_CLKDIV0_ARM_MASK);
...
- /* VIC0 does not have IRQS 5..7,
- * VIC1 is fully populated. */
- s3c64xx_init_irq(~0 & ~(0xf << 5), ~0);
+ /* VIC0 is missing IRQ7, VIC1 is fully populated. */
+ s3c64xx_init_irq(~0 & ~(1 << 7), ~0);
...
- printk("S3C6400: Initialising architecture\n");
+ printk("S3C6410: Initialising architecture\n");
next prev parent reply other threads:[~2010-01-25 12:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 4:02 Default machine include placements Ben Dooks
2010-01-25 10:05 ` Russell King - ARM Linux
2010-01-25 10:28 ` Ben Dooks
2010-01-25 10:32 ` Daniel Silverstone
2010-01-25 10:44 ` Ben Dooks
2010-01-25 10:49 ` Daniel Silverstone
2010-01-25 10:55 ` Ben Dooks
2010-01-25 11:19 ` Russell King - ARM Linux
2010-01-25 11:53 ` Ben Dooks
2010-01-25 12:04 ` Russell King - ARM Linux [this message]
2010-01-25 13:54 ` Ben Dooks
2010-01-25 14:59 ` Russell King - ARM Linux
2010-01-25 21:48 ` Ben Dooks
2010-01-25 14:03 ` Ben Dooks
2010-01-25 10:57 ` Mark Brown
2010-01-25 10:49 ` Ben Dooks
2010-01-25 11:01 ` Russell King - ARM Linux
2010-01-25 11:44 ` Ben Dooks
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=20100125120454.GD16340@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).