linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Akihiro TSUKADA <tskd08@gmail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [PATCH 4/5] dvb core: add media controller support for the demod
Date: Mon, 5 Jan 2015 16:29:47 -0200	[thread overview]
Message-ID: <20150105162947.4ebc553f@concha.lan> (raw)
In-Reply-To: <54AAA150.7000109@gmail.com>

Em Mon, 05 Jan 2015 23:36:00 +0900
Akihiro TSUKADA <tskd08@gmail.com> escreveu:

> On 2015年01月02日 00:51, Mauro Carvalho Chehab wrote:
> >  /*
> > @@ -416,6 +418,11 @@ struct dvb_frontend {
> >  	struct dvb_frontend_ops ops;
> >  	struct dvb_adapter *dvb;
> >  	struct i2c_client *fe_cl;
> > +#if defined(CONFIG_MEDIA_CONTROLLER)
> > +	struct media_device *mdev;
> > +	struct media_entity demod_entity;
> > +#endif
> > +
> 
> I understood that this patch was invalidated by the updated patch series:
> "dvb core: add basic suuport for the media controller",
> and now the demod_entity is registered in dvbdev.c::dvb_register_device()
> via dvb_frontend_register(). Is that right?

Yes. 

> And if so,
> Shouldn't only the (tuner) subdevices be registered separately
> in dvb_i2c_attach_tuner(), instead of dvb_i2c_attach_fe()?

No, it seems better to let dmxdev to register. That means that even
the non-converted I2C drivers, plus the non-I2C drivers may benefit
from the Media controller as well.

> (and it would be simpler if "mdev" can be accessed
> like dvb_fe_get_mdev() {return fepriv->dvbdev->mdev;},
> instead of having a cached value in dvb_frontend.)

Yeah, we could map this way, but that would require to add an extra
parameter to the fe register function, with has already too much
parameters. So, as it already uses an struct to pass parameters into
it, I decided to just re-use it.

> sorry if I'm totally wrong,
> I don't have an experience with media controller API.
> 
> regards,
> akihiro
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 

Cheers,
Mauro

  reply	other threads:[~2015-01-05 18:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01 15:51 [RFC PATCH 0/5] mb96a20s:use DVB core I2C binding and add media controller support Mauro Carvalho Chehab
2015-01-01 15:51 ` [PATCH 1/5] mb86a20s: remove unused debug modprobe parameter Mauro Carvalho Chehab
2015-01-01 15:51 ` [PATCH 2/5] mb86a20s: convert it to I2C binding model Mauro Carvalho Chehab
2015-01-01 15:51 ` [PATCH 3/5] mb86a20s: remove two uneeded macros Mauro Carvalho Chehab
2015-01-01 15:51 ` [PATCH 4/5] dvb core: add media controller support for the demod Mauro Carvalho Chehab
2015-01-05 14:36   ` Akihiro TSUKADA
2015-01-05 18:29     ` Mauro Carvalho Chehab [this message]
2015-01-06 12:32       ` Akihiro TSUKADA
2015-01-01 15:51 ` [PATCH 5/5] cx231xx: add media controller support for mb86a20s boards 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=20150105162947.4ebc553f@concha.lan \
    --to=mchehab@osg.samsung.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=tskd08@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).