From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Bruce_Leonard@selinc.com" <Bruce_Leonard@selinc.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Device tree and external RTC
Date: Wed, 3 Oct 2007 19:33:37 -0400 [thread overview]
Message-ID: <9e4733910710031633v3bb409c9j32b345e12396c1b0@mail.gmail.com> (raw)
In-Reply-To: <OF5A3A8901.AAC62E29-ON88257369.007F3E0B-88257369.007FC5D0@selinc.com>
On 10/3/07, Bruce_Leonard@selinc.com <Bruce_Leonard@selinc.com> wrote:
> I still think I've got a valid question about the device tree. Isn't the
> purpose of the device tree to completely describe the HW to the kernel?
> Shouldn't I be able to add a child node to the i2c node describing the
> M41T00 RTC and have the kernel figure out that there's an RTC hanging off
> the I2C bus? Or am I completely off base here?
I am having the same question about audio codecs. ALSA soc support is
designed to automatically load the right drivers depending on the
hardware in the device. Doesn't the device tree need to include the
codec chips? These chips are hooked up with various combinations of
i2s, ac97 and i2c.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-10-03 23:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 21:00 Device tree and external RTC Bruce_Leonard
2007-10-03 23:15 ` Bruce_Leonard
2007-10-03 23:33 ` Jon Smirl [this message]
2007-10-04 0:59 ` linux ethernet problem jxnuxdy
2007-10-04 11:45 ` Valentine Barshak
2007-10-04 9:29 ` Device tree and external RTC Guennadi Liakhovetski
2007-10-04 18:17 ` Bruce_Leonard
2007-10-04 19:52 ` Guennadi Liakhovetski
2007-10-04 11:21 ` Peter Korsgaard
2007-10-04 18:25 ` Bruce_Leonard
2007-10-05 10:45 ` Guennadi Liakhovetski
2007-10-05 19:37 ` Bruce_Leonard
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=9e4733910710031633v3bb409c9j32b345e12396c1b0@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=Bruce_Leonard@selinc.com \
--cc=linuxppc-embedded@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).