From: Ben Warren <bwarren@qstreams.com>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Platform device style question
Date: Thu, 24 Aug 2006 14:43:12 -0400 [thread overview]
Message-ID: <1156444992.17977.66.camel@saruman.qstreams.net> (raw)
In-Reply-To: <20060824220625.515d9b3c@vitb.ru.mvista.com>
Thanks Vitaly,
On Thu, 2006-08-24 at 22:06 +0400, Vitaly Bordug wrote:
> I'd suggest to make a look at LDD concerning linux device model...
Thanks. I'll read it again. My little brain absorbs this stuff very
slowly.
> 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.
My particular platform (MPC8349) gets its hardware info (CPU, IMMBAR,
PCI, I2C, SPI resources etc.) from an OF device tree that is generated
alongside U-boot and I guess embedded in the uImage file. (I apologize
if I'm getting my jargon mixed up here) The OF device tree idea seemed
like a slick way to abstract away some HW settings from Linux. I was
imagining writing board-side platform device registration that gets its
settings from the device tree, allowing a bit of re-use between similar
but not identical boards.
>
> 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.
I definitely have much learning to do. Thanks very much for the
pointers!
regards,
Ben
prev parent reply other threads:[~2006-08-24 18:43 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
2006-08-24 18:43 ` Ben Warren [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=1156444992.17977.66.camel@saruman.qstreams.net \
--to=bwarren@qstreams.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=vbordug@ru.mvista.com \
/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