From: Neil Armstrong <narmstrong@baylibre.com>
To: Nicolas Belin <nbelin@baylibre.com>,
andrzej.hajda@intel.com, robert.foss@linaro.org
Cc: devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Laurent.pinchart@ideasonboard.com,
jonas@kwiboo.se, jernej.skrabec@gmail.com
Subject: Re: [PATCH 2/3] drm: bridge: it66121: Fix the register page length
Date: Fri, 18 Mar 2022 09:34:19 +0100 [thread overview]
Message-ID: <ae37bbcc-14b9-8024-c10f-7a71bd90ff0e@baylibre.com> (raw)
In-Reply-To: <20220316135733.173950-3-nbelin@baylibre.com>
On 16/03/2022 14:57, Nicolas Belin wrote:
> Set the register page length or window length to
> 0x100 according to the documentation.
>
> Fixes: 988156dc2fc9 ("drm: bridge: add it66121 driver")
> Signed-off-by: Nicolas Belin <nbelin@baylibre.com>
> ---
> drivers/gpu/drm/bridge/ite-it66121.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/bridge/ite-it66121.c b/drivers/gpu/drm/bridge/ite-it66121.c
> index 06b59b422c69..64912b770086 100644
> --- a/drivers/gpu/drm/bridge/ite-it66121.c
> +++ b/drivers/gpu/drm/bridge/ite-it66121.c
> @@ -227,7 +227,7 @@ static const struct regmap_range_cfg it66121_regmap_banks[] = {
> .selector_mask = 0x1,
> .selector_shift = 0,
> .window_start = 0x00,
> - .window_len = 0x130,
> + .window_len = 0x100,
> },
> };
>
The documentation we have access to at [1] is confusing:
Reg00 ~ Reg2F are accessible in any register bank.
Reg30~ RegFF are accessible in register bank0
Reg130~ Reg1BF are accessible in register bank1. These are HDMI packet registers.
But indeed it means:
- Reg00 ~ Reg2F: are always accessible, whether bank0 or bank1 is set
- Reg30~ RegFF: only when bank0 is set
- Reg130~ Reg1BF: only when bank0 is set at Reg30~ RegF range
So 0x100 is the right window_len here.
Acked-by: Neil Armstrong <narmstrong@baylibre.com>
[1] https://rockchip.fr/radxa/IT66121_Register_List_Release_V1.0.pdf
next prev parent reply other threads:[~2022-03-18 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 13:57 [PATCH 0/3] drm: bridge: it66121: Add audio support Nicolas Belin
2022-03-16 13:57 ` [PATCH 1/3] dt-bindings: display: " Nicolas Belin
2022-03-23 20:06 ` Rob Herring
2022-03-16 13:57 ` [PATCH 2/3] drm: bridge: it66121: Fix the register page length Nicolas Belin
2022-03-18 8:34 ` Neil Armstrong [this message]
2022-03-16 13:57 ` [PATCH 3/3] drm: bridge: it66121: Add audio support Nicolas Belin
2022-03-18 8:44 ` Neil Armstrong
2023-08-25 10:58 ` [3/3] " Nishanth Menon
2022-03-24 8:53 ` [PATCH 0/3] " Neil Armstrong
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=ae37bbcc-14b9-8024-c10f-7a71bd90ff0e@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andrzej.hajda@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=nbelin@baylibre.com \
--cc=robert.foss@linaro.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
all inboxes | Powered by JetHome®