From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Olli Salonen <olli.salonen@iki.fi>
Cc: Michael Ira Krufky <mkrufky@linuxtv.org>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCHv3 1/2] tda18250: support for new silicon tuner
Date: Wed, 1 Nov 2017 10:37:35 -0200 [thread overview]
Message-ID: <20171101103735.59e9c77c@vento.lan> (raw)
In-Reply-To: <CAAZRmGwuHRHxzvfQCBc+uTq+FCo6Z_2f_oT=H70TCpwQfouLvA@mail.gmail.com>
Em Mon, 30 Oct 2017 05:31:40 +0200
Olli Salonen <olli.salonen@iki.fi> escreveu:
> Hello Michael,
>
> Many thanks for taking the time to review the patches.
>
> On 27 October 2017 at 13:27, Michael Ira Krufky <mkrufky@linuxtv.org> wrote:
> >> +static int tda18250_sleep(struct dvb_frontend *fe)
> >> +{
> >> + struct i2c_client *client = fe->tuner_priv;
> >> + struct tda18250_dev *dev = i2c_get_clientdata(client);
> >> + int ret;
> >> +
> >> + dev_dbg(&client->dev, "\n");
> >> +
> >> + /* power down LNA */
> >> + ret = regmap_write_bits(dev->regmap, R0C_AGC11, 0x80, 0x00);
> >> + if (ret)
> >> + return ret;
> >> +
> >> + ret = tda18250_power_control(fe, TDA18250_POWER_STANDBY);
> >> + return ret;
> >> +}
> >
> > Do we know for sure if the IF_FREQUENCY is preserved after returning
> > from a sleep? It might be a good idea to set `dev->if_frequency = 0`
> > within `tda18250_sleep` to be sure that it gets set again on the next
> > tune, but you may want to check the specification first, if its
> > available.
> >
> > This is not a show-stopper -- We can merge this as-is and this can be
> > handled in a follow-up patch.
>
> I will look into this and send a patch on top of this one if needed.
>
> Thank you for pointing it out.
There is a show-stopper issue here, though: it lacks adding an
entry for the driver at MAINTAINERS file :-)
Please add it.
While here, please look at the checkpatch warnings:
WARNING: msleep < 20ms can sleep for up to 20ms; see Documentation/timers/timers-howto.txt
#746: FILE: drivers/media/tuners/tda18250.c:678:
+ msleep(5);
and the 80 column ones. I was unable to see, at the places it complained,
a reason why not limit the lines to 80 columns.
Regards,
Thanks,
Mauro
next prev parent reply other threads:[~2017-11-01 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 3:31 [PATCHv3 1/2] tda18250: support for new silicon tuner Olli Salonen
2017-11-01 12:37 ` Mauro Carvalho Chehab [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-02 13:00 olli.salonen
2017-10-27 10:42 ` Michael Ira Krufky
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=20171101103735.59e9c77c@vento.lan \
--to=mchehab@s-opensource.com \
--cc=linux-media@vger.kernel.org \
--cc=mkrufky@linuxtv.org \
--cc=olli.salonen@iki.fi \
/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.