From: Andreas Schwab <schwab@linux-m68k.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [RFC/PATCH] i2c/powermac: Improve detection of devices from device-tree
Date: Mon, 18 Jun 2012 14:57:08 +0200 [thread overview]
Message-ID: <m28vfkvkuz.fsf@igel.home> (raw)
In-Reply-To: <1340014606.2372.13.camel@pasglop> (Benjamin Herrenschmidt's message of "Mon, 18 Jun 2012 20:16:46 +1000")
Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
> This patch adds a number of workarounds for broken Apple device-trees
> mostly around sound chips. It handles creating the missing audio codec
> devices and works around various issues with missing addresses or
> missing compatible properties.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
>
> Andreas, this is what I've been cooking up today. Still mostly untested
> though, so handle with care :-) But it gives you the basic premises.
Sucessfully tested on PowerBook6,7 and PowerMac7,3 (both tas3004, the
latter with the deq workaround).
These are the remaining failures on PowerMac7,3:
i2c i2c-5: No i2c address for /ht@0,f2000000/pci@1/mac-io@7/i2c@18000/i2c-modem
i2c i2c-6: i2c-powermac: modalias failure on /u3@0,f8000000/i2c@f8001000/cereal@1c0
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-06-18 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 10:16 [RFC/PATCH] i2c/powermac: Improve detection of devices from device-tree Benjamin Herrenschmidt
2012-06-18 12:57 ` Andreas Schwab [this message]
2012-06-18 20:51 ` Benjamin Herrenschmidt
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=m28vfkvkuz.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.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).