From: Rob Herring <robh@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
mchehab@kernel.org, hverkuil-cisco@xs4all.nl,
Heiko Stuebner <heiko.stuebner@theobroma-systems.com>,
dafna.hirschfeld@collabora.com, helen.koike@collabora.com,
ezequiel@collabora.com, robh+dt@kernel.org,
Laurent.pinchart@ideasonboard.com, linux-media@vger.kernel.org
Subject: Re: [PATCH v6 02/10] dt-bindings: media: rkisp1: fix pclk clock-name
Date: Mon, 12 Jul 2021 14:04:58 -0600 [thread overview]
Message-ID: <20210712200458.GA2397368@robh.at.kernel.org> (raw)
In-Reply-To: <20210618130238.4171196-3-heiko@sntech.de>
On Fri, 18 Jun 2021 15:02:30 +0200, Heiko Stuebner wrote:
> From: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
>
> Having a clock name as "pclk_isp" suggests really hard a remnant from
> the vendor kernel.
>
> Right now no driver _and_ no devicetree actually uses this clock name
> so there is still time to fix that naming.
>
> Therefore drop the "_isp" suffix and only name it pclk.
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
> ---
> Documentation/devicetree/bindings/media/rockchip-isp1.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-07-12 20:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 13:02 [PATCH v6 0/7] rkisp1 support for px30 Heiko Stuebner
2021-06-18 13:02 ` [PATCH v6 01/10] media: rockchip: rkisp1: remove unused irq variable Heiko Stuebner
2021-06-18 13:02 ` [PATCH v6 02/10] dt-bindings: media: rkisp1: fix pclk clock-name Heiko Stuebner
2021-07-12 20:04 ` Rob Herring [this message]
2021-06-18 13:02 ` [PATCH v6 03/10] dt-bindings: media: rkisp1: document different irq possibilities Heiko Stuebner
2021-07-12 20:05 ` Rob Herring
2021-06-18 13:02 ` [PATCH v6 04/10] media: rockchip: rkisp1: allow separate interrupts Heiko Stuebner
2021-06-18 13:02 ` [PATCH v6 05/10] media: rockchip: rkisp1: make some isp-param functions variable Heiko Stuebner
2021-06-20 7:21 ` Dafna Hirschfeld
2021-07-12 20:43 ` Laurent Pinchart
2021-06-18 13:02 ` [PATCH v6 06/10] media: rockchip: rkisp1: make some isp-stats " Heiko Stuebner
2021-06-20 7:22 ` Dafna Hirschfeld
2021-07-12 20:44 ` Laurent Pinchart
2021-06-18 13:02 ` [PATCH v6 07/10] media: rockchip: rkisp1: add prefixes for v10 specific parts Heiko Stuebner
2021-06-18 13:02 ` [PATCH v6 08/10] media: rockchip: rkisp1: add support for v12 isp variants Heiko Stuebner
2021-06-20 7:26 ` Dafna Hirschfeld
2021-07-12 20:47 ` Laurent Pinchart
2021-06-18 13:02 ` [PATCH v6 09/10] dt-bindings: media: rkisp1: document px30 isp compatible Heiko Stuebner
2021-07-12 20:06 ` Rob Herring
2021-06-18 13:02 ` [PATCH v6 10/10] media: rockchip: rkisp1: add support for px30 isp version Heiko Stuebner
2021-07-12 20:40 ` [PATCH v6 0/7] rkisp1 support for px30 Laurent Pinchart
2021-07-12 20:46 ` Heiko Stübner
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=20210712200458.GA2397368@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=dafna.hirschfeld@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@collabora.com \
--cc=heiko.stuebner@theobroma-systems.com \
--cc=heiko@sntech.de \
--cc=helen.koike@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).