Re: [PATCHv3 1/6] omap: prcm: switch to a chained IRQ handler mechanism

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Tero Kristo <t-kristo@xxxxxx> [110623 02:04]:
> On Thu, 2011-06-23 at 10:19 +0200, Tony Lindgren wrote:
> > 
> > Please note consider that this data will be coming from device
> > tree and will disappear from here. We won't be merging any new
> > data after v3.1 unless it comes from device tree. So this too
> > will need to be converted because we won't be able to add support
> > for new omaps otherwise.
> 
> This part I am not too sure what you mean with this. Do you have some
> info / examples about the device tree somewhere and how this data should
> be converted?

Well there's some minimal data in the devel-devicetree branch currently.
That allows you to play with it if, the last commit contains some
instructions for the devicetree append support.

Then there are tons of examples in arch/powerpc/boot/dts. Basically
we'll have something like omap34xx.dts included into the board .dts
file. So your prcm interrupt data would live in the omap34xx.dts as
would 34xx specific mux data. Then the board specific .dts contains
the configured pins etc.

Just something to consider for organizing the code so you don't have
to change things around much after the device tree support is merged :)

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux