Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: ZhuXiangyu <1194781887@qq.com>, Stephen Boyd <sboyd@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>
Cc: Brian Masney <bmasney+clk@redhat.com>,
	Jerome Brunet <jbrunet+clk@baylibre.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] clk: rockchip: add clock output/input switch driver
Date: Sat, 21 Nov 2026 12:03:56 +0100	[thread overview]
Message-ID: <729d5740-b611-4701-a293-447f940453ec@kernel.org> (raw)
In-Reply-To: <tencent_6DE9C8A75BC0B999E08A6DD1A67AC25C5705@qq.com>

On 21/11/2026 11:58, ZhuXiangyu wrote:
> Add a small driver for the Rockchip GRF-controlled clock output/input
> switch. It exposes a single gate bit as a clock, allowing the SAI MCLK
> pin direction to be controlled through the clock framework.
> 
> Tested on an RK3506B board with the ES8388 codec: this clock drives the
> I2S MCLK and audio playback works.
> 
> Tested-by: ZhuXiangyu <1194781887@qq.com>

No, this makes no sense. Please do not invent own stuff, like
author-testing-tags. Look how other people did it.

> Signed-off-by: ZhuXiangyu <1194781887@qq.com>
> ---

Best regards,
Krzysztof


      reply	other threads:[~2026-11-21 11:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20261121105856.1414984-1-1194781887@qq.com>
2026-11-21 10:58 ` [PATCH 2/2] clk: rockchip: add clock output/input switch driver ZhuXiangyu
2026-11-21 11:03   ` Krzysztof Kozlowski [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=729d5740-b611-4701-a293-447f940453ec@kernel.org \
    --to=krzk@kernel.org \
    --cc=1194781887@qq.com \
    --cc=bmasney+clk@redhat.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=jbrunet+clk@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=sboyd@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