From: John Keeping <jkeeping@inmusicbrands.com>
To: Michael Tretter <m.tretter@pengutronix.de>,
linux-media@vger.kernel.org, Jacob Chen <jacob-chen@iotwrt.com>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] media: rockchip: rga: fix offset lookup
Date: Sat, 10 Aug 2024 14:00:36 +0100 [thread overview]
Message-ID: <ZrdkdA-RJOqZNcUT-jkeeping@inmusicbrands.com> (raw)
In-Reply-To: <ZrYoT7HmTc7OT2Y4@pengutronix.de>
Hi Michael,
On Fri, Aug 09, 2024 at 04:31:43PM +0200, Michael Tretter wrote:
> On Tue, 06 Aug 2024 10:48:41 +0100, John Keeping wrote:
> > The rot_mir_point_matrix is arranged with the rotation values in rows
> > and mirror settings in the columns. Fix the order of indexing to match
> > this so that the correct values are used.
>
> The table and indexing is correct. The rows (second index) contain the
> mirror modes and the columns (first index) contain the rotation modes,
> and the table and the indexing are correct. If you read the columns, the
> corner moves clockwise, but if you read the rows, the corner moves in a
> z or s form, indicating that these are the mirror modes.
>
> It's probably worth documenting, how the table works.
>
> However, there is a mixup of the arguments between the call to
> rga_lookup_draw_pos() and the use in the function.
>
> The function definition is
>
> static struct rga_addr_offset *
> rga_lookup_draw_pos(struct rga_corners_addr_offset * offsets,
> u32 rotate_mode, u32 mirr_mode)
>
> but it is called as
>
> rga_lookup_draw_pos(&offsets, mir_mode, rot_mode);
>
> I think, fixing the order of the arguments in the function call is the
> correct fix to your observed bug.
Ah, yes. I'm not sure how I missed that.
I have confirmed your suggested change works and will send an updated
patch.
Thanks,
John
> >
> > Signed-off-by: John Keeping <jkeeping@inmusicbrands.com>
> > ---
> > drivers/media/platform/rockchip/rga/rga-hw.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/media/platform/rockchip/rga/rga-hw.c b/drivers/media/platform/rockchip/rga/rga-hw.c
> > index 11c3d72347572..b7d51ddb10fa4 100644
> > --- a/drivers/media/platform/rockchip/rga/rga-hw.c
> > +++ b/drivers/media/platform/rockchip/rga/rga-hw.c
> > @@ -97,7 +97,7 @@ static struct rga_addr_offset *rga_lookup_draw_pos(struct
> > if (!offsets)
> > return NULL;
> >
> > - switch (rot_mir_point_matrix[rotate_mode][mirr_mode]) {
> > + switch (rot_mir_point_matrix[mirr_mode][rotate_mode]) {
> > case LT:
> > return &offsets->left_top;
> > case LB:
> > --
> > 2.45.2
prev parent reply other threads:[~2024-08-10 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 9:48 [PATCH] media: rockchip: rga: fix offset lookup John Keeping
2024-08-09 8:45 ` Hans Verkuil
2024-08-09 14:31 ` Michael Tretter
2024-08-10 13:00 ` John Keeping [this message]
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=ZrdkdA-RJOqZNcUT-jkeeping@inmusicbrands.com \
--to=jkeeping@inmusicbrands.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=heiko@sntech.de \
--cc=jacob-chen@iotwrt.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=m.tretter@pengutronix.de \
--cc=mchehab@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