Re: Re: using headers for platform device outside of the staging tree

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

 



Am Dienstag, 25. Oktober 2011, 11:40:35 schrieb Greg KH:
> On Tue, Oct 25, 2011 at 12:26:54PM +0300, Dan Carpenter wrote:
> > On Tue, Oct 25, 2011 at 10:23:48AM +0200, Marc Dietrich wrote:
> > > Hi Greg,
> > > 
> > > i like to use the nvec driver with an arm soc board. What's the "usual" way
> > > to get> > 
> > > access to the platform data (in nvec.h)? I see three options:
> > > 	a) just add #include "../../../drivers/staging/nvec/nvec.h" to the board
> > > 	file as> > 
> > > long as the driver is still in staging and update it after the driver got
> > > blessed> 
> > Don't do this.
> > 
> > > 	b) create some standalone file in
> > > 	include/linux/platform_data/tegra_nvec.h with> > 
> > > just the platform data inside
> > 
> > Sounds good.  It's just the struct definitions that you need yes?
> 
> Yes, please do this, it's ok to have platform data for staging drivers
> in the platform_data include directory due to the issues for this type
> of problem.

ok, I may come up with a fouth solution which is using the device tree.

Thanks 

Marc

_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel


[Index of Archives]     [Linux Driver Backports]     [DMA Engine]     [Linux GPIO]     [Linux SPI]     [Video for Linux]     [Linux USB Devel]     [Linux Coverity]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux