From: YP WU <yp.wu@mediatek.com>
To: <mchehab@kernel.org>
Cc: <Jason-BF.Huang@mediatek.com>, <Lecopzer.Chen@mediatek.com>,
<francis.lee@mediatek.com>, <gustavoars@kernel.org>,
<hverkuil-cisco@xs4all.nl>, <leo.hsiao@mediatek.com>,
<linux-kernel@vger.kernel.org>, <linux-media@vger.kernel.org>,
<yp.wu@mediatek.com>
Subject: Re: How to use "DTV_FE_CAPABILITY" command for Frontend.h of Linux DVB
Date: Thu, 2 Sep 2021 19:03:47 +0800 [thread overview]
Message-ID: <20210902110347.14939-1-yp.wu@mediatek.com> (raw)
In-Reply-To: <20210715095933.63dbcd31@coco.lan>
Hello, Mr.Mauro,
Frist of all, thanks for your reply and Sorry to reply late.
We know that everything is controlled by /dev/dvb/frontend.
It is assumed that the device node "dvb/frontend0", "dvb/frontend1" and "dvb/frontend2" use the input signal from the same satellite antenna. In addition, "dvb/frontend0", "dvb/frontend1", and "dvb/frontend2" are premised on receiving broadcast signals at the same time under the condition that the same voltage is always supplied to the satellite antenna.
Therefore, Our TV uses an HW circuit equipped with only one LNB IC.
Since only one LNB IC is installed, the design policy of including and controlling the same LNB IC in "dvb/frontend0", "dvb/frontend1" and "dvb/frontend2" is complicated and difficult to understand. It is more simpler and easier to design to separate the LNB IC into "dvb/frontend3" and control the LNB IC from "dvb0.frontend3". Therefore, we want to separate LNB to different device node.
BRs,
YP
next prev parent reply other threads:[~2021-09-02 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 6:15 YP WU
2021-06-23 7:33 ` Mauro Carvalho Chehab
2021-07-02 9:28 ` YP WU
2021-07-09 15:47 ` YP WU
2021-07-15 7:59 ` Mauro Carvalho Chehab
2021-09-02 11:03 ` YP WU [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-14 9:40 YP WU
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=20210902110347.14939-1-yp.wu@mediatek.com \
--to=yp.wu@mediatek.com \
--cc=Jason-BF.Huang@mediatek.com \
--cc=Lecopzer.Chen@mediatek.com \
--cc=francis.lee@mediatek.com \
--cc=gustavoars@kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=leo.hsiao@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
/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
all inboxes | Powered by JetHome®