From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Jon Smirl <jonsmirl-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [PATCH] i2c driver for Maxim max9485 audio clock generator chip
Date: Wed, 22 Oct 2008 08:38:47 +0200 [thread overview]
Message-ID: <20081022083847.5216472c@hyperion.delvare> (raw)
In-Reply-To: <9e4733910810211657s5e25e391p5ca6e6f672d115c5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, 21 Oct 2008 19:57:09 -0400, Jon Smirl wrote:
> On Tue, Oct 21, 2008 at 4:36 AM, Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org> wrote:
> > Honestly I don't see any value in this driver. There's nothing you can
> > do with it that you couldn't already do without it.
>
> I need a driver so that my device tree will bind and tell me the i2c
> address of the device.
This is rubbish. It's perfectly fine to let the I2C device be
instantiated from the device tree without having a driver that binds to
it. The device tree and the instantiated device, not the driver, tell
you the I2C address of the device.
> We may also build a device in the future with two of these chips.
I fail to see how it matters.
--
Jean Delvare
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-10-22 6:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 3:02 [PATCH] i2c driver for Maxim max9485 audio clock generator chip Jon Smirl
2008-10-21 8:36 ` Jean Delvare
[not found] ` <20081021103607.78ffb4da-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-10-21 23:57 ` Jon Smirl
[not found] ` <9e4733910810211657s5e25e391p5ca6e6f672d115c5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-10-22 6:38 ` Jean Delvare [this message]
[not found] ` <20081022083847.5216472c-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-10-22 16:38 ` Jon Smirl
2008-10-21 8:45 ` Ben Dooks
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=20081022083847.5216472c@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=jonsmirl-Re5JQEeQqe8AvxtiuMwx3w@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