linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* Example dts file
@ 2009-04-17 17:04 Eddie Dawydiuk
  2009-04-17 17:12 ` Grant Likely
  0 siblings, 1 reply; 3+ messages in thread
From: Eddie Dawydiuk @ 2009-04-17 17:04 UTC (permalink / raw)
  To: linuxppc-dev, Grant Likely

Hello,

I'm working on creating a dts file for a custom board based on the Yosemite AMCC 
440EP evaluation board. We have an FPGA connected to the PCI bus, and I'm a bit 
unsure how to describe this in the dts file. The FPGA implements an SD card 
core, RTC core, Nand core... Can anyone point me to an example dts file I can 
refer to?

I've read that I'm not required to describe every PCI device in the system. 
Although I'd like to eventually submit our changes for upstream support, so as 
far as I know I do need to specify all of these devices in the dts file, so 
drivers can parse the dts file to know what devices are present.

-- 
Best Regards,
________________________________________________________________
  Eddie Dawydiuk, Technologic Systems | voice:  (480) 837-5200
  16525 East Laser Drive 	     | fax:    (480) 837-5300
  Fountain Hills, AZ 85268            | web: www.embeddedARM.com

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Example dts file
  2009-04-17 17:04 Example dts file Eddie Dawydiuk
@ 2009-04-17 17:12 ` Grant Likely
  2009-04-18  0:40   ` David Gibson
  0 siblings, 1 reply; 3+ messages in thread
From: Grant Likely @ 2009-04-17 17:12 UTC (permalink / raw)
  To: Eddie Dawydiuk; +Cc: linuxppc-dev

On Fri, Apr 17, 2009 at 11:04 AM, Eddie Dawydiuk <eddie@embeddedarm.com> wrote:
> Hello,
>
> I'm working on creating a dts file for a custom board based on the Yosemite
> AMCC 440EP evaluation board. We have an FPGA connected to the PCI bus, and
> I'm a bit unsure how to describe this in the dts file. The FPGA implements
> an SD card core, RTC core, Nand core... Can anyone point me to an example
> dts file I can refer to?

If it is attached to the PCI bus, then you don't need to describe it
in the .dts file.  PCI can reliably probe for devices.  Your driver
should know what devices are present based on the PCI vendor and
device IDs.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Example dts file
  2009-04-17 17:12 ` Grant Likely
@ 2009-04-18  0:40   ` David Gibson
  0 siblings, 0 replies; 3+ messages in thread
From: David Gibson @ 2009-04-18  0:40 UTC (permalink / raw)
  To: Grant Likely; +Cc: linuxppc-dev, Eddie Dawydiuk

On Fri, Apr 17, 2009 at 11:12:43AM -0600, Grant Likely wrote:
> On Fri, Apr 17, 2009 at 11:04 AM, Eddie Dawydiuk <eddie@embeddedarm.com> wrote:
> > Hello,
> >
> > I'm working on creating a dts file for a custom board based on the Yosemite
> > AMCC 440EP evaluation board. We have an FPGA connected to the PCI bus, and
> > I'm a bit unsure how to describe this in the dts file. The FPGA implements
> > an SD card core, RTC core, Nand core... Can anyone point me to an example
> > dts file I can refer to?
> 
> If it is attached to the PCI bus, then you don't need to describe it
> in the .dts file.  PCI can reliably probe for devices.  Your driver
> should know what devices are present based on the PCI vendor and
> device IDs.

However, for onboard PCI devices it's often necessary to have a node
giving at least the interrupt routing information, because this can't
generally be probed by PCI.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-04-18  0:41 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-04-17 17:04 Example dts file Eddie Dawydiuk
2009-04-17 17:12 ` Grant Likely
2009-04-18  0:40   ` David Gibson

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).