From: "Timur Tabi" <timur@freescale.com>
To: "Jochen Friedrich" <jochen@scram.de>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: I2C node in device tree breaks old-style drivers
Date: Wed, 30 Jul 2008 08:00:05 -0500 [thread overview]
Message-ID: <ed82fe3e0807300600n3f91a57bl823f639700d53a11@mail.gmail.com> (raw)
In-Reply-To: <48904863.7050902@scram.de>
On Wed, Jul 30, 2008 at 5:54 AM, Jochen Friedrich <jochen@scram.de> wrote:
> Hi Timur,
>
>> So my conclusion is that specifying an I2C node in the device tree *requires*
>> that the driver be new-style. Is there any way we can fix this? I'm not going
>> to have time to update the CS4270 driver to a new-style interface before the
>> 2.6.27 window closes.
>
> This conclusion is correct. One possible way to fix this is to add support for
> blacklisting to drivers/of/base.c (untested):
No need. I posted a patch to alsa-devel that makes the CS4270 a
new-style I2C driver. I'd hate to think that my driver is the only
I2C driver used on PowerPC systems that was outdated. :-)
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2008-07-30 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 19:43 I2C node in device tree breaks old-style drivers Timur Tabi
2008-07-30 10:54 ` Jochen Friedrich
2008-07-30 13:00 ` Timur Tabi [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=ed82fe3e0807300600n3f91a57bl823f639700d53a11@mail.gmail.com \
--to=timur@freescale.com \
--cc=jochen@scram.de \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).