linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Matt Sealey" <matt@genesi-usa.com>
Cc: linuxppc-dev@ozlabs.org, i2c@lm-sensors.org
Subject: Re: [PATCH 3/3] Add device tree compatible aliases to i2c drivers
Date: Wed, 23 Jan 2008 15:30:27 -0500	[thread overview]
Message-ID: <9e4733910801231230o234a1422u1bf857498b819a02@mail.gmail.com> (raw)
In-Reply-To: <4797A127.8070401@genesi-usa.com>

On 1/23/08, Matt Sealey <matt@genesi-usa.com> wrote:
>
>
> Jon Smirl wrote:
> > --- a/drivers/i2c/chips/tps65010.c
> > +++ b/drivers/i2c/chips/tps65010.c
> > @@ -571,6 +571,10 @@ static const struct i2c_device_id tps65010_id[] = {
> >       { "tps65011", TPS65011 },
> >       { "tps65012", TPS65012 },
> >       { "tps65013", TPS65013 },
> > +     OF_ID("ti,tps65010", TPS65010)
> > +     OF_ID("ti,tps65011", TPS65011)
> > +     OF_ID("ti,tps65012", TPS65012)
> > +     OF_ID("ri,tps65013", TPS65013)
> >       { },
>
> ti, ti, ti, ri?
>
> > --- a/drivers/rtc/rtc-ds1307.c
> > +++ b/drivers/rtc/rtc-ds1307.c
> > @@ -129,6 +129,12 @@ static const struct i2c_device_id ds1307_id[] = {
> >       { "ds1339", ds_1339 },
> >       { "ds1340", ds_1340 },
> >       { "m41t00", m41t00 },
> > +     OF_ID("dallas,ds1307", ds_1307)
> > +     OF_ID("dallas,ds1337", ds_1337)
> > +     OF_ID("dallas,ds1338", ds_1338)
> > +     OF_ID("dallas,ds1339", ds_1339)
> > +     OF_ID("dallas,ds1340", ds_1340)
> > +     OF_ID("stm,m41t00", m41t00)
> >       {},
> >  };
>
> The convention is to use the stock ticker, capitalized, if a company
> has one, I guess dallas is MXIM these days, but dallas is a good
> substitute based on the fact that most people still remember Dallas
> clock chips and so on from the Ancient Days. STMicroelectronics is STM.
> I couldn't care less about case sensitivity, but the stock ticker
> thing was always a good idea.. it gives a sort of grounding in reality
> for the manufacturer names.

I'll put in whatever the Open Firmware police tell me to. We just all
need to come to an agreement.


> Are we still following this convention or are the names of devices
> simply arbitrarily defined by Linux kernel developers now?
>
> --
> Matt Sealey <matt@genesi-usa.com>
> Genesi, Manager, Developer Relations
>


-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2008-01-23 20:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23  2:09 [PATCH 1/3] Rename i2c-mpc to i2c-mpc-drv in preparation for breaking out common code Jon Smirl
2008-01-23  2:09 ` [PATCH 2/3] Convert PowerPC MPC i2c to of_platform_driver from platform_driver Jon Smirl
2008-01-23  3:11   ` Stephen Rothwell
2008-01-23  4:18     ` Jon Smirl
2008-01-23 14:31   ` Jon Loeliger
2008-01-23 14:40     ` Jon Smirl
2008-01-23  2:09 ` [PATCH 3/3] Add device tree compatible aliases to i2c drivers Jon Smirl
2008-01-23 20:18   ` Matt Sealey
2008-01-23 20:30     ` Jon Smirl [this message]
2008-02-01  7:32     ` David Gibson
2008-01-25  0:32   ` [i2c] " Olof Johansson
2008-01-25  0:33     ` Scott Wood
2008-01-25  0:48       ` Jon Smirl
2008-01-25  0:38     ` Jon Smirl
2008-01-23  2:46 ` [PATCH 1/3] Rename i2c-mpc to i2c-mpc-drv in preparation for breaking out common code Stephen Rothwell
2008-01-23  2:50   ` Jon Smirl
2008-01-23  3:02     ` Grant Likely
2008-01-23  3:09       ` Jon Smirl
  -- strict thread matches above, loose matches on Subject: below --
2008-01-28 14:42 [PATCH 0/3] Implement device tree based i2c module loading on mpc5200 powerpc Jon Smirl
2008-01-28 14:42 ` [PATCH 3/3] Add device tree compatible aliases to i2c drivers Jon Smirl
2008-01-28 17:10   ` Jon Loeliger

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=9e4733910801231230o234a1422u1bf857498b819a02@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=i2c@lm-sensors.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=matt@genesi-usa.com \
    /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).