From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-renesas-soc@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>, Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/bridge: ti-sn65dsi86: Check bridge connection failure
Date: Tue, 18 Mar 2025 22:00:31 +0100 [thread overview]
Message-ID: <Z9ne78KhxfKYgnh_@ninjato> (raw)
In-Reply-To: <20250318204133.GC22890@pendragon.ideasonboard.com>
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
Hi Laurent,
> > Read out and check the ID registers, so we can bail out if I2C
> > communication does not work or if the device is unknown.
>
> What's the advantage of that, what are you trying to guard against ?
That a random chip at address 0x2c will be used.
> > Tested on a
> > Renesas GrayHawk board (R-Car V4M) by using a wrong I2C address and by
> > not enabling RuntimePM for the device.
>
> What do you mean by not enabling runtime PM for the device ?
I left out pm_runtime_get() before regmap_read_bulk().
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-03-18 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 15:52 [PATCH v3] drm/bridge: ti-sn65dsi86: Check bridge connection failure Wolfram Sang
2025-03-18 15:59 ` Wolfram Sang
2025-03-18 17:56 ` Doug Anderson
2025-03-24 16:37 ` Doug Anderson
2025-03-18 20:41 ` Laurent Pinchart
2025-03-18 21:00 ` Wolfram Sang [this message]
2025-03-24 16:40 ` Laurent Pinchart
2025-03-24 17:17 ` Doug Anderson
2025-03-24 17:30 ` Laurent Pinchart
2025-03-24 17:35 ` Doug Anderson
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=Z9ne78KhxfKYgnh_@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.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 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.