From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] staging: media: max96712: a few, mainly cosmetic, changes
Date: Thu, 19 Dec 2024 18:14:37 +0100 [thread overview]
Message-ID: <20241219171437.GE3377144@ragnatech.se> (raw)
In-Reply-To: <20241219150644.64507-1-laurentiu.palcu@oss.nxp.com>
Hello Laurentiu,
On 2024-12-19 17:06:40 +0200, Laurentiu Palcu wrote:
> Hi,
>
> This is in preparation for bringing our downstream max96724 work into
> the max96712 driver. The changes in this patch-set are mainly cosmetic
> to increase readability, with one exception related to the PCLK debug
> register which appears to exist in MAX96724 as well(see VPG section in
> users guide [1]).
>
> Unfortunately, I couldn't find any max96712 reference manual anywhere to
> make sure the registers match between the 2 chips, nor I have a max96712
> to test with.
I have tested this series with both MAX96712 and MAX96724 and I can
capture the test patterns correctly. For the series,
Tested-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
>
> However, since the max96724 compatible was added here, according to the
> commit
>
> 6c872b782ae ("media: staging: max96712: Add support for MAX96724")
>
> the chips are "almost identical". So, I used max96724 register and
> field descriptions instead. Someone with a max96712 RM may want to
> double-check though.
>
> Thanks,
> Laurentiu
>
> [1] https://www.analog.com/media/en/technical-documentation/user-guides/max96724fr-user-guide.pdf
>
> Laurentiu Palcu (3):
> staging: media: max96712: fix typo
> staging: media: max96712: enable extra debug register for max96724
> staging: media: max96712: add some register and field definitions
>
> drivers/staging/media/max96712/max96712.c | 210 +++++++++++++++++-----
> 1 file changed, 165 insertions(+), 45 deletions(-)
>
> --
> 2.44.1
>
--
Kind Regards,
Niklas Söderlund
prev parent reply other threads:[~2024-12-19 17:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 15:06 [PATCH 0/3] staging: media: max96712: a few, mainly cosmetic, changes Laurentiu Palcu
2024-12-19 15:06 ` [PATCH 1/3] staging: media: max96712: fix typo Laurentiu Palcu
2024-12-19 17:06 ` Niklas Söderlund
2025-01-06 8:28 ` Dan Carpenter
2024-12-19 15:06 ` [PATCH 2/3] staging: media: max96712: enable extra debug register for max96724 Laurentiu Palcu
2024-12-19 17:09 ` Niklas Söderlund
2024-12-20 9:01 ` Laurentiu Palcu
2024-12-19 15:06 ` [PATCH 3/3] staging: media: max96712: add some register and field definitions Laurentiu Palcu
2024-12-19 17:10 ` Niklas Söderlund
2024-12-19 17:14 ` Niklas Söderlund [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=20241219171437.GE3377144@ragnatech.se \
--to=niklas.soderlund@ragnatech.se \
--cc=gregkh@linuxfoundation.org \
--cc=laurentiu.palcu@oss.nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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