From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Max Weng <max_weng@compal.corp-partner.google.com>,
linux-kernel@vger.kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
matthias.bgg@gmail.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2] arm64: dts: mediatek: mt8186: add FHCTL node
Date: Tue, 24 Sep 2024 10:46:10 +0200 [thread overview]
Message-ID: <69fcaf74-ddf5-4bd8-8f0b-3d1a1793c0f7@collabora.com> (raw)
In-Reply-To: <20240923144728.870285-1-max_weng@compal.corp-partner.google.com>
Il 23/09/24 16:47, Max Weng ha scritto:
> From: max_weng <max_weng@compal.corp-partner.google.com>
>
> add FHCTL device node for Frequency Hopping and Spread Spectrum clock function.
>
> Change-Id: I7f9f2991978df7d5d3a6a8bc78f6f443f2f0460d
Please remove the useless Change-Id tag, this means nothing upstream, after which,
on V3:
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Signed-off-by: Max Weng <max_weng@compal.corp-partner.google.com>
> ---
> Change frome v1 to v2
> * Modify the commit description
> arch/arm64/boot/dts/mediatek/mt8186.dtsi | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8186.dtsi b/arch/arm64/boot/dts/mediatek/mt8186.dtsi
> index 148c332018b0..d3c3c2a40adc 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8186.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8186.dtsi
> @@ -29,6 +29,13 @@ aliases {
> rdma1 = &rdma1;
> };
>
> + fhctl: fhctl@1000ce00 {
> + compatible = "mediatek,mt8186-fhctl";
> + clocks = <&apmixedsys CLK_APMIXED_TVDPLL>;
> + reg = <0 0x1000ce00 0 0x200>;
> + status = "disabled";
> + };
> +
> cci: cci {
> compatible = "mediatek,mt8186-cci";
> clocks = <&mcusys CLK_MCU_ARMPLL_BUS_SEL>,
prev parent reply other threads:[~2024-09-24 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 14:47 Max Weng
2024-09-24 8:46 ` AngeloGioacchino Del Regno [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=69fcaf74-ddf5-4bd8-8f0b-3d1a1793c0f7@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=max_weng@compal.corp-partner.google.com \
--cc=robh@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®