Re: omap3505: HECC support and DT ?

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

 



On 12/11/2014 08:44 AM, Jean-Michel Hautbois wrote:
> Hi !
> 
> I have a custom board with a AM3505.
> I am trying to use linux 3.18 and I have difficulties making it work.
> What is needed in order to get it declared in DT ?
usually look at examples of an board file closely resembling the one
that you are working on and look at the commit that introduced it..
usually just Makefile and dts is needed.

> Is it still needed to have a board-am3517-myboard.c ?

ideally not. even for devices that are yet to be "dtfied" they
platform data goes to arch/arm/mach-omap2/pdata-quirks.c

See arch/arm/boot/dts/am3517-craneboard.dts as an example.

> 
> I have a few drivers like that I need to bring up (a Micrel KSZ8873
> for example) where the drivers exist, but a DT binding seems to be
> missing.

without checking the status of micrel driver in question, generically
speaking: not all drivers in linux kernel have been converted to
device tree. if your board uses one such driver, it is usually
strongly recommended to convert such a driver to DT and then integrate.

> But I may have missed the information, hence my question :).


-- 
Regards,
Nishanth Menon
--
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