From: Russell King <rmk+kernel@armlinux.org.uk>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-media@vger.kernel.org
Subject: [PATCH v3 3/7] drm/i2c: tda998x: move CEC device initialisation later
Date: Mon, 09 Apr 2018 13:16:22 +0100 [thread overview]
Message-ID: <E1f5Vig-0002LV-Ju@rmk-PC.armlinux.org.uk> (raw)
In-Reply-To: <20180409121529.GA31403@n2100.armlinux.org.uk>
We no longer use the CEC client to access the CEC part itself, so we can
move this later in the initialisation sequence.
Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
---
drivers/gpu/drm/i2c/tda998x_drv.c | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/i2c/tda998x_drv.c b/drivers/gpu/drm/i2c/tda998x_drv.c
index 2a99930f1bda..7f2762fab5c9 100644
--- a/drivers/gpu/drm/i2c/tda998x_drv.c
+++ b/drivers/gpu/drm/i2c/tda998x_drv.c
@@ -1489,9 +1489,6 @@ static int tda998x_create(struct i2c_client *client, struct tda998x_priv *priv)
priv->cec_addr = 0x34 + (client->addr & 0x03);
priv->current_page = 0xff;
priv->hdmi = client;
- priv->cec = i2c_new_dummy(client->adapter, priv->cec_addr);
- if (!priv->cec)
- return -ENODEV;
/* wake up the device: */
cec_write(priv, REG_CEC_ENAMODS,
@@ -1578,6 +1575,12 @@ static int tda998x_create(struct i2c_client *client, struct tda998x_priv *priv)
cec_write(priv, REG_CEC_RXSHPDINTENA, CEC_RXSHPDLEV_HPD);
}
+ priv->cec = i2c_new_dummy(client->adapter, priv->cec_addr);
+ if (!priv->cec) {
+ ret = -ENODEV;
+ goto fail;
+ }
+
/* enable EDID read irq: */
reg_set(priv, REG_INT_FLAGS_2, INT_FLAGS_2_EDID_BLK_RD);
@@ -1594,14 +1597,14 @@ static int tda998x_create(struct i2c_client *client, struct tda998x_priv *priv)
ret = tda998x_get_audio_ports(priv, np);
if (ret)
- goto err_audio;
+ goto fail;
if (priv->audio_port[0].format != AFMT_UNUSED)
tda998x_audio_codec_init(priv, &client->dev);
return 0;
-err_audio:
+fail:
if (client->irq)
free_irq(client->irq, priv);
err_irq:
--
2.7.4
next prev parent reply other threads:[~2018-04-09 12:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 12:15 [PATCH v3 0/7] TDA998x CEC support Russell King - ARM Linux
2018-04-09 12:16 ` [PATCH v3 1/7] drm/i2c: tda998x: move mutex/waitqueue/timer/work init early Russell King
2018-04-09 12:16 ` [PATCH v3 2/7] drm/i2c: tda998x: fix error cleanup paths Russell King
2018-04-09 12:16 ` Russell King [this message]
2018-04-09 12:16 ` [PATCH v3 4/7] drm/i2c: tda998x: always disable and clear interrupts at probe Russell King
2018-04-09 12:16 ` [PATCH v3 5/7] drm/i2c: tda9950: add CEC driver Russell King
2018-04-20 15:31 ` Russell King - ARM Linux
2018-04-20 15:48 ` Hans Verkuil
2018-04-20 16:07 ` Russell King - ARM Linux
2018-04-24 9:27 ` Hans Verkuil
2018-04-09 12:16 ` [PATCH v3 6/7] drm/i2c: tda998x: add CEC support Russell King
2018-04-24 9:27 ` Hans Verkuil
2018-04-09 12:16 ` [PATCH v3 7/7] dt-bindings: tda998x: add the calibration gpio Russell King
2018-04-24 9:27 ` Hans Verkuil
2018-04-24 9:29 ` [PATCH v3 0/7] TDA998x CEC support Hans Verkuil
2018-04-24 9:42 ` Russell King - ARM Linux
2018-04-24 9:57 ` Hans Verkuil
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=E1f5Vig-0002LV-Ju@rmk-PC.armlinux.org.uk \
--to=rmk+kernel@armlinux.org.uk \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.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