From: Tom Rini <trini@konsulko.com>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: Kever Yang <kever.yang@rock-chips.com>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
u-boot@lists.denx.de, linux-amarula@amarulasolutions.com,
Simon Glass <sjg@chromium.org>, Lin Huang <hl@rock-chips.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Michael Trimarchi <michael@amarulasolutions.com>,
Arnaud Patard <arnaud.patard@rtp-net.org>,
Manoj Sai <abbaraju.manojsai@amarulasolutions.com>
Subject: Re: [PATCH] rockchip: Fix the broken Video out for rk3288 boards
Date: Fri, 6 Jan 2023 11:52:29 -0500 [thread overview]
Message-ID: <20230106165229.GZ3787616@bill-the-cat> (raw)
In-Reply-To: <20230102182345.31066-1-jagan@amarulasolutions.com>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
On Mon, Jan 02, 2023 at 11:53:45PM +0530, Jagan Teki wrote:
> Video out on RK3288 boards has been broken since from few
> releases due to the adding of reset support on vop but
> missed enabling DM_RESET on associated boards.
>
> This patch fixes those RK3288 boards.
>
> Cc: Simon Glass <sjg@chromium.org>
> Cc: Lin Huang <hl@rock-chips.com>
> Cc: Jernej Skrabec <jernej.skrabec@gmail.com>
> Cc: Michael Trimarchi <michael@amarulasolutions.com>
> Cc: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
> Fixes: <9749d2ea29e1> ("rockchip: video: vop: Add reset support")
> Reported-by: Manoj Sai <abbaraju.manojsai@amarulasolutions.com>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2023-01-06 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 18:23 [PATCH] rockchip: Fix the broken Video out for rk3288 boards Jagan Teki
2023-01-04 20:01 ` Simon Glass
2023-01-06 16:52 ` Tom Rini [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=20230106165229.GZ3787616@bill-the-cat \
--to=trini@konsulko.com \
--cc=abbaraju.manojsai@amarulasolutions.com \
--cc=arnaud.patard@rtp-net.org \
--cc=hl@rock-chips.com \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=michael@amarulasolutions.com \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.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).