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-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH 2/3] staging: media: max96712: enable extra debug register for max96724
Date: Thu, 19 Dec 2024 18:09:23 +0100 [thread overview]
Message-ID: <20241219170923.GC3377144@ragnatech.se> (raw)
In-Reply-To: <20241219150644.64507-3-laurentiu.palcu@oss.nxp.com>
Hello Laurentiu,
Thanks for your work.
On 2024-12-19 17:06:42 +0200, Laurentiu Palcu wrote:
> The current implementation has the register disabled since it is not
> documented in the MAX96724 RM. However, in the chip's user's guide [1],
> in the Video Pattern Generator section, the register is documented and
> it appears to work just fine. Before the change I was experiencing
> approx 10fps when streaming, after: 30.3fps.
>
> [1] https://www.analog.com/media/en/technical-documentation/user-guides/max96724fr-user-guide.pdf
>
> Signed-off-by: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
> ---
> drivers/staging/media/max96712/max96712.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/staging/media/max96712/max96712.c b/drivers/staging/media/max96712/max96712.c
> index 5228f9ec60859..682ebd20851f7 100644
> --- a/drivers/staging/media/max96712/max96712.c
> +++ b/drivers/staging/media/max96712/max96712.c
> @@ -462,6 +462,7 @@ static const struct max96712_info max96712_info_max96712 = {
>
> static const struct max96712_info max96712_info_max96724 = {
> .dpllfreq = 1200,
> + .have_debug_extra = true,
This flag was added as I could not find the register in the MAX96724
datasheet I had access to at the time. As you now prove the register
exists in the user's guide and that it works I think a better solution
is to remove the 'have_debug_extra' flag all together then set it for
both supported devices.
> };
>
> static const struct of_device_id max96712_of_table[] = {
> --
> 2.44.1
>
--
Kind Regards,
Niklas Söderlund
next prev parent reply other threads:[~2024-12-19 17:09 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 [this message]
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 ` [PATCH 0/3] staging: media: max96712: a few, mainly cosmetic, changes Niklas Söderlund
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=20241219170923.GC3377144@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