From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Peter Rosin <peda@axentia.se>
Subject: Re: [PATCH v1 2/2] drm/i2c: tda998x: remove indirect reg_read/_write() calls
Date: Fri, 21 Jun 2019 16:20:52 +0100 [thread overview]
Message-ID: <20190621152052.ja2adc7usqsgyu62@shell.armlinux.org.uk> (raw)
In-Reply-To: <20190527191552.10413-2-TheSven73@gmail.com>
On Mon, May 27, 2019 at 03:15:52PM -0400, Sven Van Asbroeck wrote:
> -static void
> -reg_set(struct tda998x_priv *priv, u16 reg, u8 val)
> +static int
> +reg_set(struct regmap *regmap, u16 reg, u8 val)
I don't see the point of making this return an 'int' - you don't modify
any of the callsites to check the returned value, so returning a value
is not useful.
> {
> - regmap_update_bits(priv->regmap, reg, val, val);
> + return regmap_update_bits(regmap, reg, val, val);
> }
>
> -static void
> -reg_clear(struct tda998x_priv *priv, u16 reg, u8 val)
> +static int
> +reg_clear(struct regmap *regmap, u16 reg, u8 val)
Same here.
> @@ -685,16 +655,18 @@ static void tda998x_detect_work(struct work_struct *work)
> static irqreturn_t tda998x_irq_thread(int irq, void *data)
> {
> struct tda998x_priv *priv = data;
> - u8 sta, cec, lvl, flag0, flag1, flag2;
> + struct regmap *regmap = priv->regmap;
> + u8 sta, cec, lvl;
> + unsigned int flag0, flag1, flag2;
> bool handled = false;
>
> sta = cec_read(priv, REG_CEC_INTSTATUS);
> if (sta & CEC_INTSTATUS_HDMI) {
> cec = cec_read(priv, REG_CEC_RXSHPDINT);
> lvl = cec_read(priv, REG_CEC_RXSHPDLEV);
> - flag0 = reg_read(priv, REG_INT_FLAGS_0);
> - flag1 = reg_read(priv, REG_INT_FLAGS_1);
> - flag2 = reg_read(priv, REG_INT_FLAGS_2);
> + regmap_read(regmap, REG_INT_FLAGS_0, &flag0);
> + regmap_read(regmap, REG_INT_FLAGS_1, &flag1);
> + regmap_read(regmap, REG_INT_FLAGS_2, &flag2);
Not particularly enamoured by this...
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2019-06-21 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 19:15 [PATCH v1 1/2] drm/i2c: tda998x: access chip registers via a regmap Sven Van Asbroeck
2019-05-27 19:15 ` [PATCH v1 2/2] drm/i2c: tda998x: remove indirect reg_read/_write() calls Sven Van Asbroeck
2019-06-21 15:20 ` Russell King - ARM Linux admin [this message]
2019-06-21 15:15 ` [PATCH v1 1/2] drm/i2c: tda998x: access chip registers via a regmap Russell King - ARM Linux admin
2019-06-21 21:13 ` Sven Van Asbroeck
2019-06-21 22:06 ` Russell King - ARM Linux admin
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=20190621152052.ja2adc7usqsgyu62@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=thesven73@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