From: "Maxime Ripard" <mripard@kernel.org>
To: "Dave Stevenson" <dave.stevenson@raspberrypi.com>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
"Hans Verkuil" <hverkuil@xs4all.nl>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Maxime Ripard" <mripard@kernel.org>,
"Maxime Ripard" <mripard@redhat.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>
Subject: Re: [PATCH 0/4] media: tc358743: Additional link freq, and better validation
Date: Thu, 12 Jun 2025 12:54:01 +0000 [thread overview]
Message-ID: <c3c62b98dfc2fcbfa018bf683e5abf60@kernel.org> (raw)
In-Reply-To: <20250611-media-tc358743-v1-0-708556026f9d@raspberrypi.com>
On Wed, 11 Jun 2025 19:37:12 +0100, Dave Stevenson wrote:
> I've had these patches on our Raspberry Pi downstream kernel since
> I tried upstreaming them back in 2017 [1].
> Maxime's asked me to repost them as he's trying to use tc358743 with
> mainline in RGB mode[2], and is hitting exactly the problems I had
> written them to solve.
>
> [ ... ]
Tested-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
prev parent reply other threads:[~2025-06-12 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 18:37 [PATCH 0/4] media: tc358743: Additional link freq, and better validation Dave Stevenson
2025-06-11 18:37 ` [PATCH 1/4] media: tc358743: Add support for 972Mbit/s link freq Dave Stevenson
2025-06-11 18:37 ` [PATCH 2/4] media: tc358743: Increase FIFO trigger level to 374 Dave Stevenson
2025-06-11 18:37 ` [PATCH 3/4] media: tc358743: Check I2C succeeded during probe Dave Stevenson
2025-06-11 18:37 ` [PATCH 4/4] media: tc358743: Return an appropriate colorspace from tc358743_set_fmt Dave Stevenson
2025-06-12 12:54 ` Maxime Ripard [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=c3c62b98dfc2fcbfa018bf683e5abf60@kernel.org \
--to=mripard@kernel.org \
--cc=dave.stevenson@raspberrypi.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mripard@redhat.com \
--cc=p.zabel@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).