From: Akihiro TSUKADA <tskd08@gmail.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.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: Tue, 06 Jan 2015 21:32:24 +0900 [thread overview]
Message-ID: <54ABD5D8.20408@gmail.com> (raw)
In-Reply-To: <20150105162947.4ebc553f@concha.lan>
On 2015年01月06日 03:29, Mauro Carvalho Chehab wrote:
> Em Mon, 05 Jan 2015 23:36:00 +0900
>> 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.
I guess you meant dvbdev instead of dmxdev,
but still I'm afraid that media_entity for a tuner module is not
registered like FE(demod),dmxdev,net,ca, because dvb_frontend_register()
registers just a demod (or a whole FE module) for now.
Tuner subdevices don't have their own device nodes to be passed to
dvb_register_media_device() in the first place,
So I think we need to define MEDIA_ENT_T_DVB_SUBDEV{,_TUNER}
and register a media_entity of type:MEDIA_ENT_T_DVB_SUBDEV_TUNER,
if a separate tuner chip is used.
(with {major,minor} of the parent FE dev?)
If we can distinguish if a separate tuner subdev is used or not
by looking into "fe", then we might be able to register
the subdev from within dvb_register_[media_]device().
But if we cannot know from "fe",
dvb_i2c_attach_tuner() looks to be a good place.
Further, when a DTV board has multiple tuners and/or multiple demods
and the link between them can be dynamically configurable,
(via media controller API or a new DVB ioctl?),
then a tuner subdev can be unused and connected to no demod,
so we cannot identify all tuner subdevs from the demod ("fe") anyway.
> 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.
if we add dvb_adapter.mdev and a user sets the pointer,
then we can retrieve mdev in all the registering functions
(dvb_register_frontend, dvb_{dmxdev,net,ca_en50221}_init),
as all of them take a dvb_adapter parameter.
or is it possible that the FE,demux,net,ca under one DVB adapter
belong to different mdev's and each of them must keep its parent mdev
separately?
regards,
akihiro
next prev parent reply other threads:[~2015-01-06 12:32 UTC|newest]
Thread overview: 10+ 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
[not found] ` <cover.1420127255.git.mchehab-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
2015-01-01 15:51 ` [PATCH 4/5] dvb core: add media controller support for the demod Mauro Carvalho Chehab
2015-01-01 15:51 ` Mauro Carvalho Chehab
2015-01-05 14:36 ` Akihiro TSUKADA
2015-01-05 18:29 ` Mauro Carvalho Chehab
2015-01-06 12:32 ` Akihiro TSUKADA [this message]
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=54ABD5D8.20408@gmail.com \
--to=tskd08@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mchehab@osg.samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.