All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Tim Surber <me@timsurber.de>,
	Shreeya Patel <shreeya.patel@collabora.com>,
	heiko@sntech.de, mchehab@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, mturquette@baylibre.com,
	sboyd@kernel.org, p.zabel@pengutronix.de,
	jose.abreu@synopsys.com, nelson.costa@synopsys.com,
	shawn.wen@rock-chips.com, nicolas.dufresne@collabora.com,
	hverkuil@xs4all.nl, hverkuil-cisco@xs4all.nl
Cc: kernel@collabora.com, linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org
Subject: Re: [RESEND PATCH v5 0/4] Add Synopsys DesignWare HDMI RX Controller
Date: Tue, 7 Jan 2025 10:27:26 +0300	[thread overview]
Message-ID: <a5226fac-2a5b-47f3-b32e-8662bf932bd4@collabora.com> (raw)
In-Reply-To: <fbb5016e-678c-4e54-a6a8-0ccaa2bdf45c@timsurber.de>

On 1/7/25 03:08, Tim Surber wrote:
> Hi Dmitry,
> 
> that was my fault, my build script did not copy over the new ATF properly.
> 
> Now it works, I will update with test results with many different
> resolutions/formats here soon.

Thanks for the quick update, please post the results once ready.

-- 
Best regards,
Dmitry


WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Tim Surber <me@timsurber.de>,
	Shreeya Patel <shreeya.patel@collabora.com>,
	heiko@sntech.de, mchehab@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, mturquette@baylibre.com,
	sboyd@kernel.org, p.zabel@pengutronix.de,
	jose.abreu@synopsys.com, nelson.costa@synopsys.com,
	shawn.wen@rock-chips.com, nicolas.dufresne@collabora.com,
	hverkuil@xs4all.nl, hverkuil-cisco@xs4all.nl
Cc: kernel@collabora.com, linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org
Subject: Re: [RESEND PATCH v5 0/4] Add Synopsys DesignWare HDMI RX Controller
Date: Tue, 7 Jan 2025 10:27:26 +0300	[thread overview]
Message-ID: <a5226fac-2a5b-47f3-b32e-8662bf932bd4@collabora.com> (raw)
In-Reply-To: <fbb5016e-678c-4e54-a6a8-0ccaa2bdf45c@timsurber.de>

On 1/7/25 03:08, Tim Surber wrote:
> Hi Dmitry,
> 
> that was my fault, my build script did not copy over the new ATF properly.
> 
> Now it works, I will update with test results with many different
> resolutions/formats here soon.

Thanks for the quick update, please post the results once ready.

-- 
Best regards,
Dmitry

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2025-01-07  7:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10 19:39 [RESEND PATCH v5 0/4] Add Synopsys DesignWare HDMI RX Controller Shreeya Patel
2024-12-10 19:39 ` Shreeya Patel
2024-12-10 19:39 ` [RESEND PATCH v5 1/4] MAINTAINERS: Add entry for Synopsys DesignWare HDMI RX Driver Shreeya Patel
2024-12-10 19:39   ` Shreeya Patel
2024-12-10 19:39 ` [RESEND PATCH v5 2/4] dt-bindings: media: Document bindings for HDMI RX Controller Shreeya Patel
2024-12-10 19:39   ` Shreeya Patel
2024-12-10 19:39 ` [RESEND PATCH v5 3/4] arm64: dts: rockchip: Add device tree support " Shreeya Patel
2024-12-10 19:39   ` Shreeya Patel
2024-12-10 19:39 ` [RESEND PATCH v5 4/4] media: platform: synopsys: Add support for HDMI input driver Shreeya Patel
2024-12-10 19:39   ` Shreeya Patel
2025-02-10 13:46   ` Hans Verkuil
2025-02-10 13:46     ` Hans Verkuil
2025-02-11 16:02     ` Dmitry Osipenko
2025-02-11 16:02       ` Dmitry Osipenko
2025-01-06  0:26 ` [RESEND PATCH v5 0/4] Add Synopsys DesignWare HDMI RX Controller Tim Surber
2025-01-06  0:26   ` Tim Surber
     [not found] ` <acb91a34-c0f8-4f03-8945-755b4e42dcf3@timsurber.de>
2025-01-06 11:22   ` Dmitry Osipenko
2025-01-06 11:22     ` Dmitry Osipenko
2025-01-07  0:08     ` Tim Surber
2025-01-07  0:08       ` Tim Surber
2025-01-07  7:27       ` Dmitry Osipenko [this message]
2025-01-07  7:27         ` Dmitry Osipenko
2025-01-08 23:17         ` Tim Surber
2025-01-08 23:17           ` Tim Surber
2025-01-14 11:37           ` Dmitry Osipenko
2025-01-14 11:37             ` Dmitry Osipenko
2025-01-14 14:16             ` Nicolas Dufresne
2025-01-14 14:16               ` Nicolas Dufresne
2025-01-19  2:14             ` Tim Surber
2025-01-19  2:14               ` Tim Surber
2025-01-23 11:21               ` Dmitry Osipenko
2025-01-23 11:21                 ` Dmitry Osipenko

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=a5226fac-2a5b-47f3-b32e-8662bf932bd4@collabora.com \
    --to=dmitry.osipenko@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=hverkuil@xs4all.nl \
    --cc=jose.abreu@synopsys.com \
    --cc=kernel@collabora.com \
    --cc=krzk+dt@kernel.org \
    --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=mchehab@kernel.org \
    --cc=me@timsurber.de \
    --cc=mturquette@baylibre.com \
    --cc=nelson.costa@synopsys.com \
    --cc=nicolas.dufresne@collabora.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=shawn.wen@rock-chips.com \
    --cc=shreeya.patel@collabora.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.