mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Andy Yan <andy.yan@rock-chips.com>,
	kernel@collabora.com, linux-phy@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v2 1/3] phy: hdmi: Add optional FRL TxFFE config options
Date: Sun, 4 Oct 2026 00:33:40 +0300	[thread overview]
Message-ID: <3c0dc77b-b692-498e-aed6-aa97d827b2f4@collabora.com> (raw)
In-Reply-To: <asFoBih6P7Cr6Ute@parshuram>

Hi Vinod,

On 10/3/26 11:39 PM, Vinod Koul wrote:
> On 01-09-26, 22:55, Cristian Ciocaltea wrote:
>> During HDMI 2.1 FRL link training, the source and sink can negotiate a
>> Transmitter Feed-Forward Equalization (TxFFE) level to improve the
>> signal quality.  Starting from zero, the source may increment the TxFFE
>> level up to a maximum agreed during the LTS3 stage if the sink keeps
>> reporting FLT failures.  TxFFE adjustment is optional and only attempted
>> when both the source and the connected sink support it.
>>
>> Since the existing HDMI PHY configuration API covers the FRL rate/lane
>> selection only, provide the following fields to the frl sub-struct of
>> phy_configure_opts_hdmi:
>>
>> * ffe_level: the TxFFE level to apply, only meaningful when
>>   set_ffe_level is set.
>>
>> * set_ffe_level: a 1-bit flag that changes the semantics of the
>>   phy_configure() call, i.e. when set, the PHY driver must apply the new
>>   ffe_level and ignore the other frl related fields.
> 
> The ffe_level 0 implies it is disabled, so why should we use a flag for
> this? Rather use if value valid (non zero) logic to apply..?

That's not quite possible because level 0 is valid (and the default) according
to HDMI 2.1 spec. The source is expected to reset TxFFE to default whenever a
new FRL rate is set, hence the API shall be conformant. 

Regards,
Cristian

  reply	other threads:[~2026-10-03 21:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 19:55 [PATCH v2 0/3] phy: hdmi: Add FRL TxFFE level control Cristian Ciocaltea
2026-09-01 19:55 ` [PATCH v2 1/3] phy: hdmi: Add optional FRL TxFFE config options Cristian Ciocaltea
2026-10-03 20:39   ` Vinod Koul
2026-10-03 21:33     ` Cristian Ciocaltea [this message]
2026-09-01 19:55 ` [PATCH v2 2/3] phy: rockchip: samsung-hdptx: Handle PHY config after module reload Cristian Ciocaltea
2026-09-01 19:55 ` [PATCH v2 3/3] phy: rockchip: samsung-hdptx: Add support for FRL TxFFE level control Cristian Ciocaltea

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=3c0dc77b-b692-498e-aed6-aa97d827b2f4@collabora.com \
    --to=cristian.ciocaltea@collabora.com \
    --cc=andy.yan@rock-chips.com \
    --cc=heiko@sntech.de \
    --cc=kernel@collabora.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mani@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=vkoul@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

all inboxes | Powered by JetHome®