From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: dri-devel@lists.freedesktop.org, Rob Clark <robdclark@gmail.com>,
Dave Airlie <airlied@gmail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 26/28] drm/i2c: tda998x: code optimization
Date: Sun, 12 Jan 2014 09:45:33 +0000 [thread overview]
Message-ID: <20140112094533.GP15937@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140112092201.764fb09c@armhf>
On Sun, Jan 12, 2014 at 09:22:01AM +0100, Jean-Francois Moine wrote:
> On Sat, 11 Jan 2014 18:55:09 +0000
> Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
>
> > On Thu, Jan 09, 2014 at 12:07:25PM +0100, Jean-Francois Moine wrote:
> > > This patch reduces the number of I2C exchanges by setting many bits in
> > > one write and removing a useless write.
> > >
> > > Signed-off-by: Jean-Francois Moine <moinejf@free.fr>
> > > ---
> > > drivers/gpu/drm/i2c/tda998x_drv.c | 10 ++++------
> > > 1 file changed, 4 insertions(+), 6 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/i2c/tda998x_drv.c b/drivers/gpu/drm/i2c/tda998x_drv.c
> > > index 6b4f6d2..d3b3f3a 100644
> > > --- a/drivers/gpu/drm/i2c/tda998x_drv.c
> > > +++ b/drivers/gpu/drm/i2c/tda998x_drv.c
> > > @@ -751,10 +751,10 @@ tda998x_configure_audio(struct tda998x_priv *priv,
> > > }
> > >
> > > reg_write(priv, REG_AIP_CLKSEL, clksel_aip);
> > > - reg_clear(priv, REG_AIP_CNTRL_0, AIP_CNTRL_0_LAYOUT);
> > > + reg_clear(priv, REG_AIP_CNTRL_0, AIP_CNTRL_0_LAYOUT |
> >
> > This patch clearly hasn't even been build tested, so I doubt there's
> > much point reviewing this or the following patches. From a quick scan
> > of the following patches, this never got fixed so the following patches
> > can't have been build tested either.
>
> I don't see what can be the problem with this patch. It does not change
> anything in the logic. About testing, it is applied to my Cubox kernel
> for more than 4 months and everything works correctly.
>
> I will move the following comment a bit upwards. Maybe the code will be
> clearer.
You're replacing ");" with "|" here, which is not legal C. Parenthesis
must be balanced and statements must be terminated.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
next prev parent reply other threads:[~2014-01-12 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 11:07 [PATCH v2 26/28] drm/i2c: tda998x: code optimization Jean-Francois Moine
2014-01-11 18:55 ` Russell King - ARM Linux
2014-01-12 8:22 ` Jean-Francois Moine
2014-01-12 9:45 ` Russell King - ARM Linux [this message]
2014-01-12 10:14 ` Jean-Francois Moine
2014-01-12 10:37 ` Russell King - ARM Linux
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=20140112094533.GP15937@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moinejf@free.fr \
--cc=robdclark@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox