From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: kstewart@linuxfoundation.org, linux-kernel@vger.kernel.org,
rfontana@redhat.com, tglx@linutronix.de,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-media@vger.kernel.org
Subject: Re: [Linux-kernel-mentees] [PATCH] media: dvb_dummy_fe.c: add members to dvb_dummy_fe_state
Date: Mon, 2 Dec 2019 01:49:38 -0300 [thread overview]
Message-ID: <13629649-f363-4787-e88b-784f8309bfcd@gmail.com> (raw)
In-Reply-To: <20191201090733.2bd8c2c4@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 1592 bytes --]
Hi Mauro, thanks for checking out my work!
> please don't add fields at the
> struct while they're not used, as this makes harder for reviewers to be
> sure that we're not adding bloatware at the code.
OK.
> Please remember that
> we want one logical change per patch.
>
> It means that, if you add a state->frontend_status at the driver, the
> patch should implement the entire logic for it.
I will keep this in mind.
> static int dvb_dummy_fe_sleep(struct dvb_frontend* fe)
> {
> +
> + struct dvb_dummy_fe_state *state = fe->demodulator_priv;
> +
> + state->sleeping = true;
> +
> Hmm...what's the sense of adding it? Where are you setting it to false?
> Where are you using the sleeping state?
I noted some drivers seem to instruct the hardware into a low power state. Take helene, for instance:
static int helene_sleep(struct dvb_frontend *fe)
{
struct helene_priv *priv = fe->tuner_priv;
dev_dbg(&priv->i2c->dev, "%s()\n", __func__);
helene_enter_power_save(priv);
return 0;
}
static int helene_enter_power_save(struct helene_priv *priv)
{
dev_dbg(&priv->i2c->dev, "%s()\n", __func__);
if (priv->state == STATE_SLEEP)
return 0;
/* Standby setting for CPU */
helene_write_reg(priv, 0x88, 0x0);
/* Standby setting for internal logic block */
helene_write_reg(priv, 0x87, 0xC0);
priv->state = STATE_SLEEP;
return 0;
}
As we are emulating some piece of hardware I thought it would be enough to add a simple bool to indicate that the device was sleeping.
This patch was a bit convoluted on my part. Let's iron out the issues you pointed out in v2.
- Daniel.
[-- Attachment #1.2: Type: text/html, Size: 2141 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2019-12-02 4:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-30 4:54 [Linux-kernel-mentees] [PATCH] media: dvb_dummy_fe.c: add members to dvb_dummy_fe_state Daniel W. S. Almeida
2019-12-01 8:07 ` Mauro Carvalho Chehab
2019-12-02 4:49 ` Daniel W. S. Almeida [this message]
2019-12-02 5:50 ` 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=13629649-f363-4787-e88b-784f8309bfcd@gmail.com \
--to=dwlsalmeida@gmail.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfontana@redhat.com \
--cc=tglx@linutronix.de \
/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