public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Ralph Metzler <rjkm@metzlerbros.de>
Cc: <linux-media@vger.kernel.org>
Subject: Re: [dvb] Question on dvb-core re-structure
Date: Thu, 10 Jan 2013 15:16:46 -0200	[thread overview]
Message-ID: <20130110151646.14ff8fe4@redhat.com> (raw)
In-Reply-To: <20718.58869.396398.764373@morden.metzler>

Em Thu, 10 Jan 2013 17:01:57 +0100
Ralph Metzler <rjkm@metzlerbros.de> escreveu:

> Mauro Carvalho Chehab writes:
>  > Em Thu, 10 Jan 2013 13:49:52 +0200
>  > "Hamad Kadmany" <hkadmany@codeaurora.org> escreveu:
>  > 
>  > > On 01/10/2013 1:13 PM, Antti Palosaari wrote:
>  > > > 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.
> 
> 
> 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. 

What we're doing on such cases is to put the common stuff under drivers/media/common
and the bus-specific (or platform-specific) code under drivers/media/pci,
drivers/media/usb, drivers/media/mmc, etc. There are, currenlty, 3 drivers
like that: saa7146 (the common code were always stored at /common), b2c2 and siano.

Cheers,
Mauro

  reply	other threads:[~2013-01-10 17:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 10:44 [dvb] Question on dvb-core re-structure Hamad Kadmany
2013-01-10 11:13 ` Antti Palosaari
2013-01-10 11:49   ` Hamad Kadmany
2013-01-10 14:13     ` Mauro Carvalho Chehab
2013-01-10 16:01       ` Ralph Metzler
2013-01-10 17:16         ` Mauro Carvalho Chehab [this message]
2013-01-10 14:05 ` Mauro Carvalho Chehab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130110151646.14ff8fe4@redhat.com \
    --to=mchehab@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=rjkm@metzlerbros.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox