From: "Katsuhiro Suzuki" <suzuki.katsuhiro@socionext.com>
To: "'Mauro Carvalho Chehab'" <mchehab+samsung@kernel.org>,
"Suzuki, Katsuhiro/鈴木 勝博" <suzuki.katsuhiro@socionext.com>
Cc: <linux-media@vger.kernel.org>,
"Masami Hiramatsu" <masami.hiramatsu@linaro.org>,
"Jassi Brar" <jaswinder.singh@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] media: dvb-frontends: add Socionext SC1501A ISDB-S/T demodulator driver
Date: Thu, 5 Jul 2018 10:58:42 +0900 [thread overview]
Message-ID: <000401d41403$b33db490$19b91db0$@socionext.com> (raw)
In-Reply-To: <20180704135657.3fd607cb@coco.lan>
Hi Mauro,
> -----Original Message-----
> From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> Sent: Thursday, July 5, 2018 1:58 AM
> To: Suzuki, Katsuhiro/鈴木 勝博 <suzuki.katsuhiro@socionext.com>
> Cc: linux-media@vger.kernel.org; Masami Hiramatsu
<masami.hiramatsu@linaro.org>;
> Jassi Brar <jaswinder.singh@linaro.org>; linux-arm-kernel@lists.infradead.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v3] media: dvb-frontends: add Socionext SC1501A ISDB-S/T
> demodulator driver
>
> Hi Katsuhiro-san,
>
> Em Thu, 21 Jun 2018 12:17:48 +0900
> Katsuhiro Suzuki <suzuki.katsuhiro@socionext.com> escreveu:
>
> > This patch adds a frontend driver for the Socionext SC1501A series
> > and Socionext MN88443x ISDB-S/T demodulators.
>
> Sorry for taking so long to review it. We're missing a sub-maintainer
> for DVB, with would otherwise speed up reviews of DVB patches.
No problem, thank you for reviewing! I appreciate it.
> >
> > The maximum and minimum frequency of Socionext SC1501A comes from
> > ISDB-S and ISDB-T so frequency range is the following:
> > - ISDB-S (BS/CS110 IF frequency in kHz, Local freq 10.678GHz)
> > - Min: BS-1: 1032000 => 1032.23MHz
> > - Max: ND24: 2701000 => 2070.25MHz
> > - ISDB-T (in Hz)
> > - Min: ch13: 470000000 => 470.357857MHz
> > - Max: ch62: 770000000 => 769.927857MHz
>
> There is actually an error on that part of the driver. Right now,
> the DVB core expects Satellite frequencies (DVB-S, ISDB-S, ...)
> in kHz. For all other delivery systems, it is in Hz.
>
> It is this way due to historic reasons. While it won't be hard to
> change the core, that would require to touch all Satellite drivers.
>
> As there are very few frontend drivers that accept both Satellite
> and Terrestrial standards, what we do, instead, is to setup
> two frontends. See, for example, drivers/media/dvb-frontends/helene.c.
>
Thank you for describing it. I understand our device is rare case, and
the reason why Helene has Terrestrial and Satellite structures.
I'm using MN884434 device that has 2 cores. I want to setup DVB adapter
devices (/dev/dvb/adapter0/*) for our frontend system as the following:
- adapter0: for core 0, ISDB-T, ISDB-S
- adapter1: for core 1, ISDB-T, ISDB-S
But it seems one DVB adapter device support only ISDB-T or only ISDB-S
if I divide structures. So I define the adapters as the following:
- adapter0: for core 0, ISDB-T
- adapter1: for core 0, ISDB-S
- adapter2: for core 1, ISDB-T
- adapter3: for core 1, ISDB-S
Is this correct?
> ...
> > +static const struct dvb_frontend_ops sc1501a_ops = {
> > + .delsys = { SYS_ISDBS, SYS_ISDBT },
> > + .info = {
> > + .name = "Socionext SC1501A",
> > + .frequency_min = 1032000,
> > + .frequency_max = 770000000,
> > + .caps = FE_CAN_INVERSION_AUTO | FE_CAN_FEC_AUTO |
> > + FE_CAN_QAM_AUTO | FE_CAN_TRANSMISSION_MODE_AUTO |
> > + FE_CAN_GUARD_INTERVAL_AUTO | FE_CAN_HIERARCHY_AUTO,
> > + },
> > +
> > + .sleep = sc1501a_sleep,
> > + .set_frontend = sc1501a_set_frontend,
> > + .get_tune_settings = sc1501a_get_tune_settings,
> > + .read_status = sc1501a_read_status,
> > +};
>
> In other words, you'll need to declare two structs here, one for ISDB-T
> and another one for ISDB-S.
>
OK, I'm going to divide this structure for Terrestrial and Satellite. And
add attach functions same as Helene driver.
I'll send v4 patch.
> Yeah, I know that this sucks. If you are in the mood of touching the
> DVB core, I'm willing to consider a patch that would fix this, provided
> that it won't break backward compatibility with other drivers (or would
> convert the other satellite drivers to use the new way).
>
> Thanks,
> Mauro
Hmm, I don't know the details of DVB core, I try to investigate it.
Regards,
--
Katsuhiro Suzuki
next prev parent reply other threads:[~2018-07-05 1:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 3:17 [PATCH v3] media: dvb-frontends: add Socionext SC1501A ISDB-S/T demodulator driver Katsuhiro Suzuki
2018-07-04 16:58 ` Mauro Carvalho Chehab
2018-07-05 1:58 ` Katsuhiro Suzuki [this message]
2018-07-05 2:42 ` Mauro Carvalho Chehab
2018-07-05 5:43 ` Katsuhiro Suzuki
2018-07-06 0:27 ` Mauro Carvalho Chehab
2018-07-06 6:04 ` Katsuhiro Suzuki
2018-07-06 11:16 ` Mauro Carvalho Chehab
2018-07-09 2:04 ` Katsuhiro Suzuki
2018-07-09 13:59 ` Mauro Carvalho Chehab
2018-07-10 2:50 ` Katsuhiro Suzuki
2018-07-17 6:07 ` Katsuhiro Suzuki
2018-07-17 10:58 ` Mauro Carvalho Chehab
2018-07-18 0:39 ` Katsuhiro Suzuki
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='000401d41403$b33db490$19b91db0$@socionext.com' \
--to=suzuki.katsuhiro@socionext.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=masami.hiramatsu@linaro.org \
--cc=mchehab+samsung@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;
as well as URLs for NNTP newsgroup(s).