From: Vitaly Bordug <vbordug@ru.mvista.com>
To: bwarren@qstreams.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Platform device style question
Date: Thu, 24 Aug 2006 22:06:25 +0400 [thread overview]
Message-ID: <20060824220625.515d9b3c@vitb.ru.mvista.com> (raw)
In-Reply-To: <1156441997.17977.44.camel@saruman.qstreams.net>
On Thu, 24 Aug 2006 13:53:17 -0400
Ben Warren <bwarren@qstreams.com> wrote:
> Hello,
>
> A 'newbie-to-platform-devices' question:
>
> In a patch that Kumar just sent for a compact flash device, the resource
> data (I/O addresses, IRQ # etc.) are retrieved from the platform system.
> I guess I can either modify the device tree in U-boot by adding
> additional nodes, or instantiate a platform device in Linux __init code
> based on static information. The former gives the advantage of having
> the bootloader pass the info to the OS. (Somebody please correct me if
> I'm off-base here!)
>
I'd suggest to make a look at LDD concerning linux device model...
For platform device, there's no need to cope with u-boot at all. You'll prolly need to
register the respective platform device from the board-specific code, with proper name
and driver's board-specific platform info. You may have a look at arch/ppc/syslib/ppc_sys.c about static
PD definitions usage.
> Are device trees meant to only contain information about the CPU and
> tightly-coupled peripherals, or is it considered OK-form to also include
> board-level hardware info? I guess they can really hold anything, but
> I'm trying to figure out the original intent.
>
I'd make sense to figure out the platform device bus before digging into device trees. It's slightly
different stuff, for similar aim, but anyway... Actually you do not strictly need devtree to cope with
your case afaiu.
> regards,
> Ben
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
--
Sincerely,
Vitaly
next prev parent reply other threads:[~2006-08-24 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 17:53 Platform device style question Ben Warren
2006-08-24 18:06 ` Vitaly Bordug [this message]
2006-08-24 18:43 ` Ben Warren
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=20060824220625.515d9b3c@vitb.ru.mvista.com \
--to=vbordug@ru.mvista.com \
--cc=bwarren@qstreams.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