From: Segher Boessenkool <segher@kernel.crashing.org>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: [PATCH] powerpc: Add of_register_i2c_devices()
Date: Tue, 3 Jul 2007 01:10:47 +0200 [thread overview]
Message-ID: <0a3d0917402e24efbe6224c544ddd432@kernel.crashing.org> (raw)
In-Reply-To: <20070702224643.GA21539@ld0162-tx32.am.freescale.net>
>> AFAIK, i2c is not specified by OF standard. So, we are free to chose
>> any
>> "compatible" fields for our dts. Which we then would need to match
>> against
>> drivers. So, why not make this a 1-to-1 match? I.e.,
>> [OF] [I2C]
>> compatible <-> driver_name
>> model <-> type
>
> If we do this, then the compatible field should probably be preceded
> with
> "linux,", which would get stripped by of_register_i2c_devices(). This
> would only be an interim measure until we can figure out some sort of
> name registry via power.org. Once that happens, non-"linux,"
> compatible
> fields could be looked up in an OF-to-linux table, or there could be a
> way for i2c devices to specify OF matches in addition to driver name.
Why even think of doing this? Just put the bloody name of
the device in the "compatible" property and match on that.
What is so hard about this?
If the answer is "the Linux I2C stuff is badly structured",
well, you know what to do :-)
Segher
next prev parent reply other threads:[~2007-07-02 23:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 19:20 [PATCH] powerpc: Add of_register_i2c_devices() Guennadi Liakhovetski
2007-07-01 23:36 ` Kumar Gala
2007-07-02 11:56 ` Segher Boessenkool
2007-07-02 12:03 ` Segher Boessenkool
2007-07-02 20:11 ` Guennadi Liakhovetski
2007-07-02 22:46 ` Scott Wood
2007-07-02 23:10 ` Segher Boessenkool [this message]
2007-07-02 23:06 ` Segher Boessenkool
2007-07-03 22:34 ` Guennadi Liakhovetski
2007-07-03 23:02 ` Segher Boessenkool
2007-07-04 5:28 ` Guennadi Liakhovetski
2007-07-04 12:19 ` Segher Boessenkool
2007-07-04 17:50 ` Guennadi Liakhovetski
2007-07-17 22:17 ` Guennadi Liakhovetski
2007-07-19 15:32 ` Segher Boessenkool
2007-07-19 22:07 ` Guennadi Liakhovetski
2007-07-20 7:26 ` Segher Boessenkool
2007-07-20 20:26 ` Guennadi Liakhovetski
2007-07-31 22:55 ` Segher Boessenkool
2007-08-01 5:41 ` Guennadi Liakhovetski
2007-08-01 8:18 ` Segher Boessenkool
2007-08-01 20:36 ` Guennadi Liakhovetski
2007-08-01 20:42 ` Scott Wood
2007-08-07 22:32 ` [PATCH] powerpc: fix i2c device string format Guennadi Liakhovetski
2007-08-09 19:45 ` Segher Boessenkool
2007-08-09 20:46 ` Guennadi Liakhovetski
2007-08-10 17:44 ` Segher Boessenkool
2007-08-15 6:23 ` Paul Mackerras
2007-08-15 19:15 ` Guennadi Liakhovetski
2007-08-15 21:29 ` Scott Wood
2007-08-15 22:23 ` Guennadi Liakhovetski
2007-08-16 0:36 ` Stephen Rothwell
2007-07-03 0:42 ` [PATCH] powerpc: Add of_register_i2c_devices() Benjamin Herrenschmidt
2007-07-03 12:33 ` Segher Boessenkool
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=0a3d0917402e24efbe6224c544ddd432@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=g.liakhovetski@gmx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=scottwood@freescale.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).