From: Jochen Friedrich <jochen@scram.de>
To: Jean Delvare <khali@linux-fr.org>
Cc: Scott Wood <scottwood@freescale.com>,
Kumar Gala <galak@kernel.crashing.org>,
Vitaly Bordug <vitb@kernel.crashing.org>,
linux-kernel@vger.kernel.org,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
i2c@lm-sensors.org
Subject: Re: [PATCHv4 2.6.25] i2c: adds support for i2c bus on Freescale CPM1/CPM2 controllers
Date: Fri, 22 Feb 2008 12:16:16 +0100 [thread overview]
Message-ID: <47BEAF00.50106@scram.de> (raw)
In-Reply-To: <20080221130520.12b01553@hyperion.delvare>
Hi Jean,
>> +/*
>> + * Wait for patch from Jon Smirl
>> + * #include "powerpc-common.h"
>> + */
>
> It doesn't make sense to merge this comment upstream.
I know you don't like the patch from Jon Smirl and you also explained your reasons.
Fortunately, I2c no longer uses numeric device IDs but names. So what are the alternatives?
1. modify the I2c subsystem to accept OF names additionally to I2c names (proposed by Jon smirl).
2. record the I2c name in the dts tree, either as seperate tag (like linux,i2c-name="<i2c-name>")
or as additional compatible entry (like compatible="...", "linux,<i2c-name>").
3. use a glue layer with a translation map.
What is the preferred way to do this?
Thanks,
Jochen
WARNING: multiple messages have this Message-ID (diff)
From: Jochen Friedrich <jochen@scram.de>
To: Jean Delvare <khali@linux-fr.org>
Cc: linux-kernel@vger.kernel.org,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
i2c@lm-sensors.org, Scott Wood <scottwood@freescale.com>
Subject: Re: [PATCHv4 2.6.25] i2c: adds support for i2c bus on Freescale CPM1/CPM2 controllers
Date: Fri, 22 Feb 2008 12:16:16 +0100 [thread overview]
Message-ID: <47BEAF00.50106@scram.de> (raw)
In-Reply-To: <20080221130520.12b01553@hyperion.delvare>
Hi Jean,
>> +/*
>> + * Wait for patch from Jon Smirl
>> + * #include "powerpc-common.h"
>> + */
>
> It doesn't make sense to merge this comment upstream.
I know you don't like the patch from Jon Smirl and you also explained your reasons.
Fortunately, I2c no longer uses numeric device IDs but names. So what are the alternatives?
1. modify the I2c subsystem to accept OF names additionally to I2c names (proposed by Jon smirl).
2. record the I2c name in the dts tree, either as seperate tag (like linux,i2c-name="<i2c-name>")
or as additional compatible entry (like compatible="...", "linux,<i2c-name>").
3. use a glue layer with a translation map.
What is the preferred way to do this?
Thanks,
Jochen
next prev parent reply other threads:[~2008-02-22 11:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 12:54 [PATCHv4 2.6.25] i2c: adds support for i2c bus on Freescale CPM1/CPM2 controllers Jochen Friedrich
2008-01-31 12:54 ` Jochen Friedrich
2008-02-21 12:05 ` Jean Delvare
2008-02-21 12:05 ` Jean Delvare
2008-02-22 11:16 ` Jochen Friedrich [this message]
2008-02-22 11:16 ` Jochen Friedrich
2008-02-23 12:43 ` Jean Delvare
2008-02-23 12:43 ` Jean Delvare
2008-03-25 18:46 ` Jochen Friedrich
2008-03-25 18:46 ` Jochen Friedrich
2008-03-26 0:41 ` Stephen Rothwell
2008-03-26 0:41 ` Stephen Rothwell
2008-02-23 21:28 ` Olof Johansson
2008-02-23 21:28 ` Olof Johansson
2008-02-24 15:16 ` Jochen Friedrich
2008-02-24 15:16 ` Jochen Friedrich
2008-02-24 18:15 ` Olof Johansson
2008-02-24 18:15 ` Olof Johansson
2008-02-25 16:48 ` Jochen Friedrich
2008-02-25 16:48 ` Jochen Friedrich
2008-02-24 16:19 ` Jon Smirl
2008-02-24 16:19 ` Jon Smirl
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=47BEAF00.50106@scram.de \
--to=jochen@scram.de \
--cc=galak@kernel.crashing.org \
--cc=i2c@lm-sensors.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
--cc=vitb@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.