Where is place of arch independed companion chips?
Hi Greg,
While I write driver for SM501 CC (which have graphics controller, USB MASTER/SLAVE, AC97, UART, SPI and VIDEO CAPTURE onboard), I bumped with next ambiguity:
Where is a place of this chip's Kconfig/drivers in
kernel config/drivers tree? May be create new node in drivers subtree? Or put it under graphics node (since it's main function of this CC)?
AFAIK, this is not one such multifunctional monster in the world, so somebody bumped with this problem again in future.
Signature · 2 lines
Regards Andrey Volkov
Quoted 8 lines · Andrey Volkov
Hi Greg,
While I write driver for SM501 CC (which have graphics controller, USB MASTER/SLAVE, AC97, UART, SPI and VIDEO CAPTURE onboard), I bumped with next ambiguity:
Where is a place of this chip's Kconfig/drivers in
kernel config/drivers tree? May be create new node in drivers subtree? Or put it under graphics node (since it's main function of this CC)?
You will have to split your driver (graphics under drivers/video, usb under drivers/usb, ac97 under sound, video capture under drivers/media, etc.
Tony
Hi Tony,
Quoted 12 lines · Antonino A. Daplas
Quoted 8 lines · Andrey Volkov
Hi Greg,
While I write driver for SM501 CC (which have graphics controller, USB MASTER/SLAVE, AC97, UART, SPI and VIDEO CAPTURE onboard), I bumped with next ambiguity:
Where is a place of this chip's Kconfig/drivers in
kernel config/drivers tree? May be create new node in drivers subtree? Or put it under graphics node (since it's main function of this CC)?
Quoted 3 lines
You will have to split your driver (graphics under
drivers/video, usb underdrivers/usb, ac97 under sound, video capture underdrivers/media, etc.
Yes, it was first what I try, BUT - all these drivers have common code (as bus driver, in my case) and some of private headers. And problem exactly in this code. This code NOT video/audio....., this code is abstract bus driver, and doesn't fall under some exist kernel tree node :(.
Signature · 2 lines
Regards Andrey Volkov
Quoted 9 lines · Andrey Volkov
Hi Greg,
While I write driver for SM501 CC (which have graphics controller, USB MASTER/SLAVE, AC97, UART, SPI and VIDEO CAPTURE onboard), I bumped with next ambiguity:
Where is a place of this chip's Kconfig/drivers in
kernel config/drivers tree? May be create new node in drivers subtree? Or put it under graphics node (since it's main function of this CC)?
Quoted 5 lines
AFAIK, this is not one such multifunctional monster in the world, so somebody bumped with this problem again in future.
Good question. I was about to submit a patch that created drivers/platform because the toplevel driver for MQ11xx is a platform_device driver. Any thoughts on this?
Jamey
Quoted 11 lines · Jamey Hicks
Quoted 9 lines · Andrey Volkov
Hi Greg,
While I write driver for SM501 CC (which have graphics controller, USB MASTER/SLAVE, AC97, UART, SPI and VIDEO CAPTURE onboard), I bumped with next ambiguity:
Where is a place of this chip's Kconfig/drivers in
kernel config/drivers tree? May be create new node in drivers subtree? Or put it under graphics node (since it's main function of this CC)?
Quoted 8 lines
Quoted 5 lines
AFAIK, this is not one such multifunctional monster in the world, so somebody bumped with this problem again in future.
Good question. I was about to submit a patch that created
drivers/platformbecause the toplevel driver for MQ11xx is aplatform_devicedriver. Any thoughts on this?
drivers/platform sounds good to me.
thanks,
greg k-h
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 20 lines · Greg KH
Quoted 18 lines · Jamey Hicks
Quoted 14 lines · Andrey Volkov
Hi Greg,
While I write driver for SM501 CC (which have graphics controller, USB MASTER/SLAVE, AC97, UART, SPI and VIDEO CAPTURE onboard), I bumped with next ambiguity:
Where is a place of this chip's Kconfig/drivers in
kernel config/drivers tree? May be create new node in drivers subtree? Or put it under graphics node (since it's main function of this CC)?AFAIK, this is not one such multifunctional monster in the world, so somebody bumped with this problem again in future.
Quoted 6 lines
Quoted 3 lines
Good question. I was about to submit a patch that created
drivers/platformbecause the toplevel driver for MQ11xx is aplatform_devicedriver. Any thoughts on this?
drivers/platformsounds good to me.
May be better drivers/chipset?
Because "platform" imply only platform_device drivers, but, SM501 as ex., could be connected through PCI too.
Signature · 2 lines
Regards Andrey Volkov
Quoted 5 lines · Greg KH
Quoted 3 lines
Good question. I was about to submit a patch that created
drivers/platformbecause the toplevel driver for MQ11xx is aplatform_devicedriver. Any thoughts on this?
drivers/platformsounds good to me.
In another thread (about the ucb1x00) we came up with the idea of drivers/mfd (mfd = multi function devices).
The core and platform specific parts would live here with suitable clear naming and the subsection specific parts that were separable would live in the appropriate place within the kernel.
Just another idea to add to the mix and removes the dilemma of a multifunction device with isn't platform based...
Richard
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Hi!
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
While I write driver for SM501 CC (which have graphics controller, USB MASTER/SLAVE, AC97, UART, SPI and VIDEO CAPTURE onboard), I bumped with next ambiguity:
Where is a place of this chip's Kconfig/drivers in
kernel config/drivers tree? May be create new node in drivers subtree? Or put it under graphics node (since it's main function of this CC)?AFAIK, this is not one such multifunctional monster in the world, so somebody bumped with this problem again in future.
Quoted 5 lines
Quoted 3 lines
Good question. I was about to submit a patch that created
drivers/platformbecause the toplevel driver for MQ11xx is aplatform_devicedriver. Any thoughts on this?
drivers/platformsounds good to me.
We have some problems with ucb1x00 chip on some small systems; originally we wanted it to go into drivers/misc, but that sounded wrong. Latest idea was drivers/mfd (multi functional devices)...
Pavel
Signature · 8 lines
teflon -- maybe it is a trademark, but it should not be. ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Quoted 12 lines · Richard Purdie
Quoted 5 lines · Greg KH
Quoted 3 lines
Good question. I was about to submit a patch that created
drivers/platformbecause the toplevel driver for MQ11xx is aplatform_devicedriver. Any thoughts on this?
drivers/platformsounds good to me.In another thread (about the ucb1x00) we came up with the idea of
drivers/mfd(mfd = multi function devices).
Quoted 7 lines
The core and platform specific parts would live here with suitable clear naming and the subsection specific parts that were separable would live in the appropriate place within the kernel.
Just another idea to add to the mix and removes the dilemma of a multifunction device with isn't platform based...
drivers/mfd as drivers/mfd, I have not objections. Who will send the patch first?
--
Regards
Andrey Volkov
P.S. Tony, Greg, may be it will someone from you? (I've in mind sn/ subdir)
Quoted 19 lines · --- Richard Purdie
Quoted 1 line · Greg KH
Quoted 1 line
Good question. I was about to submit a patch
that created
Quoted 1 line
Quoted 1 line
drivers/platformbecause the toplevel driver forMQ11xx is a
Quoted 3 lines
Quoted 1 line
platform_devicedriver. Any thoughts on this?
drivers/platformsounds good to me.In another thread (about the ucb1x00) we came up with the idea of
drivers/mfd(mfd = multi function devices).The core and platform specific parts would live here with suitable clear
naming and the subsection specific parts that were separable would live
in the appropriate place within the kernel.
Quoted 3 lines
Just another idea to add to the mix and removes the dilemma of a
multifunction device with isn't platform based...
This is where my sugguestion on the ucb1x00 comess in (although it seems to have ot lost as I have had no reply :-( ). To repeat myself:
I was thinking of something like driver/bus into which we might also be able to put the I2C and LL3 buses. The only problem is that this might leave some parts of the multi function chip homeless (if they can't find a home in other subsystems).
I need to do more homework ;-), but
I think we need a bus driver (I need to see what the bus subsystem offers) (IP block specific, platform and arch independent), a core driver to register busses and clients, and client drivers.
Mark
Quoted 11 lines
Richard
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
___________________________________________________________
To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com