From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Rodolfo Giometti <giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org,
Kumar Gala
<galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH][UPDATE] i2c: Add support for virtual I2C adapters
Date: Thu, 29 May 2008 13:54:51 +0200 [thread overview]
Message-ID: <20080529135451.7aa9ffde@hyperion.delvare> (raw)
In-Reply-To: <20080528133015.GS9698-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
Hi Rodolfo,
On Wed, 28 May 2008 15:30:15 +0200, Rodolfo Giometti wrote:
> I'd like to know why the patches at:
>
> http://lists.linuxcoding.com/kernel/2006-q1/msg32516.html
>
> have never been applied to the main kernel tree.
There are two main reasons:
1* Nobody reviewed the patches in question. I don't even remember
seeing test reports about these patches, but this could as well be my
defective memory. A patch affecting i2c-core definitely needs good
review and testing before it can go upstream.
2* When this patch was sent, the i2c subsystem was still using the
legacy model where device drivers have to probe for and instantiate
their devices themselves. This model is fundamentally incompatible with
a generic for of I2C multiplexing support. So I didn't pay too much
attention to attempts to support multiplexing of i2c adapters because I
suspected it would be ugly at best. Now that we have new-style i2c
device/driver binding which follows the device driver model, it's
probably the right time to think about multiplexing support again.
Another reason, I guess, is that I do not have any system with a
multiplexed I2C bus myself, so I can't test the code and I also lack
personal motivation to push this forward.
There are still some cleanups needed in i2c-core, most notably with
respect to duplication and locking, and ideally I'd like to see it done
before we add multiplexing support, but admittedly there is no roadmap
so I can't make this a mandatory requirement.
> I'd like to use them and maybe I can update them to the latest kernel
> version for submission. :)
You are welcome to update and resubmit the patch, however I suspect
that what is needed is more than that. The code was written with the
legacy model in mind, while we want to support primarily (and maybe
even exclusively) the new-style binding model.
--
Jean Delvare
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
prev parent reply other threads:[~2008-05-29 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 13:30 [PATCH][UPDATE] i2c: Add support for virtual I2C adapters Rodolfo Giometti
[not found] ` <20080528133015.GS9698-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
2008-05-28 22:53 ` Ben Dooks
[not found] ` <20080528225325.GA6226-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2008-05-29 12:03 ` Rodolfo Giometti
2008-05-29 11:54 ` Jean Delvare [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=20080529135451.7aa9ffde@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org \
--cc=giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@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