From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by ozlabs.org (Postfix) with ESMTP id 1C716DDDFB for ; Thu, 4 Oct 2007 09:33:38 +1000 (EST) Received: by wa-out-1112.google.com with SMTP id m28so5937716wag for ; Wed, 03 Oct 2007 16:33:38 -0700 (PDT) Message-ID: <9e4733910710031633v3bb409c9j32b345e12396c1b0@mail.gmail.com> Date: Wed, 3 Oct 2007 19:33:37 -0400 From: "Jon Smirl" To: "Bruce_Leonard@selinc.com" Subject: Re: Device tree and external RTC In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 10/3/07, 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