From: Daniel Silverstone <dsilvers-Y5A6D6n0/KfQXOPxS62xeg@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW@public.gmane.org,
ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org
Subject: Re: [PATCH] I2C: Rename struct s3c2410_platform_i2c to s3c_platform_i2c
Date: Thu, 12 Feb 2009 14:24:40 +0000 [thread overview]
Message-ID: <1234448680.9457.38.camel@petitemort> (raw)
In-Reply-To: <20090212150527.2d8031ad-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
On Thu, 2009-02-12 at 15:05 +0100, Jean Delvare wrote:
> > The I2C driver currently known as i2c-s3c2410 is now used by
> > several different s3cXXXX SoCs. As such, this patch renames the
> > platform data to be SoC agnostic.
> This is Ben's call, not mine, but I tend to discourage that kind of
> changes. For one thing, they cost more than then bring. And for
> another, they may need to be reverted if incompatible hardware appears
> in the future.
The same I2C controller is found throughout Samsung's s3c24xx and 64xx
range. I doubt they'll introduce wildly incompatible peripherals in the
same range.
> Personally, I read "s3c2410" in these structure names as "S3C 2410 and
> compatible", so it looks perfectly right to me, I don't see this as
> something which needs to be changed.
Whereas I see it as "s3c2410" or at most liberal, "s3c241x". Given
there's a family of 10 or more chips which all use this i2c controller,
only 4 of which could plausibly be thought of as a 2410 (2410, 2412,
2413, 2416) it seems disingenuously named as-is. The confusion which
could ensue (and indeed *does* ensue with some of our customers) seems
worth trying to avoid.
D.
--
Daniel Silverstone http://www.simtec.co.uk/
PGP mail accepted and encouraged. Key Id: 2BC8 4016 2068 7895
prev parent reply other threads:[~2009-02-12 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 13:49 [PATCH] I2C: Rename struct s3c2410_platform_i2c to s3c_platform_i2c Daniel Silverstone
2009-02-12 14:05 ` Jean Delvare
[not found] ` <20090212150527.2d8031ad-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-02-12 14:24 ` Daniel Silverstone [this message]
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=1234448680.9457.38.camel@petitemort \
--to=dsilvers-y5a6d6n0/kfqxopxs62xeg@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox