All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Xin Ji" <xji@analogixsemi.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
	dri-devel@lists.freedesktop.org, robh@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: drm/bridge: anx7625: Add right justify property
Date: Tue, 18 Aug 2026 02:12:19 +0000	[thread overview]
Message-ID: <20260818021219.DCA4A1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260818020559.961335-1-xji@analogixsemi.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Adding a vendor-specific DT property for audio interface format bypasses standard ASoC DAI format negotiation.
--

--- Patch [1]: [PATCH 1/2] dt-bindings: drm/bridge: anx7625: Add right justify property ---
Please note that due to recitation restrictions, I cannot quote the original
patch code directly. The review below is provided as a free-form summary of
the findings.

commit c7f75f4b785470ba45b421324266273f5142da0b
Author: Xin Ji <xji@analogixsemi.com>

dt-bindings: drm/bridge: anx7625: Add right justify property

This commit adds a new boolean property to the analogix,anx7625 device tree
bindings. The property controls whether the driver enables the audio right
justify function for the data stream.

[Severity: Medium]
Does adding a vendor-specific devicetree property for the audio interface
format bypass the standard ASoC DAI format negotiation?

The standard hdmi-codec framework already supports right justified formats
using the existing DAI format structures, which are normally passed dynamically
to the driver's hw_params callback based on standard sound card properties.

Creating a custom property like analogix,audio-right-justify-enable hardcodes
this configuration statically in the devicetree, which creates a permanent ABI.
Should this driver instead rely on the standard hdmi-codec API to handle the
DAI format negotiation rather than introducing a custom vendor property?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260818020559.961335-1-xji@analogixsemi.com?part=1

      parent reply	other threads:[~2026-08-18  2:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18  2:05 [PATCH 1/2] dt-bindings: drm/bridge: anx7625: Add right justify property Xin Ji
2026-08-18  2:05 ` [PATCH 2/2] drm: anx7625: add I2S input stream right justified control Xin Ji
2026-08-18  2:13   ` sashiko-bot
2026-08-18  2:12 ` sashiko-bot [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=20260818021219.DCA4A1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=xji@analogixsemi.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.