Question on dvb-core re-structure

Hi,

With the new structure of dvb-core (moved up one directory), previous DVB/ATSC adapters were moved to media/usb, media/pci and media/mmc.

For SoC that supports integrated DVB functionality, where should the adapter's code be located in the new structure? I don't see it fit any of the above three options.

I could guess that even for the SoCs there is some bus used internally. If it is not one of those already existing, then create new directly just

Hi,

With the new structure of dvb-core (moved up one directory), previous DVB/ATSC adapters were moved to media/usb, media/pci and media/mmc.

For SoC that supports integrated DVB functionality, where should the adapter's code be located in the new structure? I don't see it fit any of the above three options.

Quoted 2 lines

I could guess that even for the SoCs there is some bus used internally. If it is not one of those already existing, then create new directly just

like one of those existing and put it there.

Thanks for the answer. I just wanted to clarify - it's integrated into the chip and accessed via memory mapped registers, so I'm not sure which category to give the new directory (parallel to pci/mms/usb). Should I just put the adapter's sources directory directly under media directory?

Em Thu, 10 Jan 2013 13:49:52 +0200
"Hamad Kadmany" <[email protected]> escreveu:

Quoted 9 lines · Antti Palosaari

Quoted 2 lines

I could guess that even for the SoCs there is some bus used internally. If it is not one of those already existing, then create new directly just

like one of those existing and put it there.

Thanks for the answer. I just wanted to clarify - it's integrated into the chip and accessed via memory mapped registers, so I'm not sure which category to give the new directory (parallel to pci/mms/usb). Should I just put the adapter's sources directory directly under media directory?

That's the case of all other drivers under drivers/media/platform: they're IP blocks inside the SoC chip. I think that all arch-dependent drivers are there.

The menu needs to be renamed to "Media platform drivers" when the first DVB driver arrives there (it currently says V4L, as there's no DVB driver there yet). Feel free to add such patch on your patch series at the time you submit your driver, if nobody else submit any DVB platform driver earlier than yours.

Quoted 17 lines · Mauro Carvalho Chehab

Em Thu, 10 Jan 2013 13:49:52 +0200
"Hamad Kadmany" <[email protected]> escreveu:

Quoted 9 lines · Antti Palosaari

Quoted 2 lines

I could guess that even for the SoCs there is some bus used internally. If it is not one of those already existing, then create new directly just

like one of those existing and put it there.

Thanks for the answer. I just wanted to clarify - it's integrated into the chip and accessed via memory mapped registers, so I'm not sure which category to give the new directory (parallel to pci/mms/usb). Should I just put the adapter's sources directory directly under media directory?

That's the case of all other drivers under drivers/media/platform: they're IP blocks inside the SoC chip. I think that all arch-dependent drivers are there.

Quoted 5 lines

The menu needs to be renamed to "Media platform drivers" when the first DVB driver arrives there (it currently says V4L, as there's no DVB driver there yet). Feel free to add such patch on your patch series at the time you submit your driver, if nobody else submit any DVB platform driver earlier than yours.

What about DVB cores which can be used via different busses?
E.g. ddbridge initially only used PCIe. Now we also use the same function blocks (I2C, DVB input, etc.) connected to a SoC via an EBI (extension bus interface) and register it as a platform device. Because a lot of code can be shared I do not want to split it over several directories.