From: Kumar Gala <galak@kernel.crashing.org>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, i2c@lm-sensors.org
Subject: Re: [PATCH 3/5] powerpc: Document device nodes for I2C devices.
Date: Thu, 17 May 2007 11:39:22 -0500 [thread overview]
Message-ID: <FFBD3A3A-ADBE-4DC8-A1A1-4163367244D5@kernel.crashing.org> (raw)
In-Reply-To: <464C800C.20400@freescale.com>
On May 17, 2007, at 11:17 AM, Scott Wood wrote:
> Kumar Gala wrote:
>>> diff --git a/Documentation/powerpc/booting-without-of.txt b/
>>> Documentation/powerpc/booting-without-of.txt
>>> index b49ce16..67026ad 100644
>>> --- a/Documentation/powerpc/booting-without-of.txt
>>> +++ b/Documentation/powerpc/booting-without-of.txt
>>> @@ -1257,6 +1257,8 @@ platforms are moved over to use the
>>> flattened- device-tree model.
>>>
>>> e) I2C
>>>
>>> + e1) I2C Controller
>>> +
>>> Required properties :
>>>
>>> - device_type : Should be "i2c"
>>> @@ -1277,6 +1279,10 @@ platforms are moved over to use the
>>> flattened-device-tree model.
>>> a digital filter sampling rate register
>>> - fsl5200-clocking : boolean; if defined, indicated that
>>> this device
>>> uses the FSL 5200 clocking mechanism.
>>> + - #address-cells : should exist and be 1 if I2C devices are
>>> declared
>>> + in the device tree.
>>> + - #size-cells : should exist and be 0 if I2C devices are
>>> declared
>>> + in the device tree.
>> As I've stated before, we need a bus number as well so we can
>> handle things like I2C switches and muxes.
>
> Is this something we handle now? If not, then it's really not
> within the scope of this patchset. If so, how am I breaking it?
We don't handle i2c devices in the dev tree today. If you are going
to propose a solution it should work for all cases that people are
aware of even if linux doesn't support the functionality.
If only some subset of cases are handled what good is the device tree
to a user? They will just have to figure out if their usage is
supported or not and if not find some other solution that works for
them.
- k
next prev parent reply other threads:[~2007-05-17 16:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 14:38 [PATCH 3/5] powerpc: Document device nodes for I2C devices Scott Wood
2007-05-17 16:12 ` Kumar Gala
2007-05-17 16:17 ` Scott Wood
2007-05-17 16:39 ` Kumar Gala [this message]
2007-05-17 16:47 ` Scott Wood
2007-05-17 17:21 ` Kumar Gala
2007-05-17 18:29 ` Scott Wood
2007-05-18 15:15 ` [i2c] " Jean Delvare
2007-05-18 16:24 ` Kumar Gala
2007-05-18 16:35 ` Scott Wood
2007-05-18 17:10 ` Kumar Gala
2007-05-18 17:17 ` Scott Wood
2007-05-18 17:33 ` Kumar Gala
2007-05-18 17:55 ` Scott Wood
2007-05-20 11:53 ` Jean Delvare
2007-05-21 14:57 ` Scott Wood
2007-05-19 0:04 ` Matt Sealey
2007-05-19 0:17 ` Segher Boessenkool
2007-05-19 13:41 ` Matt Sealey
2007-05-19 16:25 ` Segher Boessenkool
2007-05-20 14:53 ` Matt Sealey
2007-05-20 15:48 ` Segher Boessenkool
2007-05-27 9:48 ` Matt Sealey
2007-05-20 11:42 ` Jean Delvare
2007-05-18 20:07 ` Segher Boessenkool
2007-05-17 19:18 ` Segher Boessenkool
2007-05-17 19:32 ` Scott Wood
2007-05-17 19:44 ` Segher Boessenkool
2007-05-17 21:15 ` Scott Wood
2007-05-18 15:27 ` [i2c] " Jean Delvare
2007-05-18 15:58 ` Scott Wood
2007-05-18 16:29 ` Kumar Gala
2007-05-18 16:31 ` Jean Delvare
2007-05-18 16:56 ` Kumar Gala
2007-05-18 19:00 ` David Brownell
2007-05-18 15:19 ` Jean Delvare
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=FFBD3A3A-ADBE-4DC8-A1A1-4163367244D5@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=i2c@lm-sensors.org \
--cc=linuxppc-dev@ozlabs.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).