From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "allen-kh.cheng" <allen-kh.cheng@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
nfraprado@collabora.com
Cc: Project_Global_Chrome_Upstream_Group@mediatek.com,
chun-jie.chen@mediatek.com, devicetree@vger.kernel.org,
drinkcat@chromium.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
srv_heupstream@mediatek.com, Chen-Yu Tsai <wenst@chromium.org>,
Ryder Lee <ryder.lee@kernel.org>
Subject: Re: [PATCH v4 1/5] arm64: dts: mediatek: Correct uart clock of MT8192
Date: Thu, 13 Jan 2022 11:03:11 +0100 [thread overview]
Message-ID: <3eeea0ce-0551-1186-7011-9bda27d62b98@collabora.com> (raw)
In-Reply-To: <20220113065822.11809-2-allen-kh.cheng@mediatek.com>
Il 13/01/22 07:58, allen-kh.cheng ha scritto:
> From: Allen-KH Cheng <Allen-KH.Cheng@mediatek.com>
>
> When the initial devicetree for mt8192 was added in 48489980e27e ("arm64:
> dts: Add Mediatek SoC MT8192 and evaluation board dts and Makefile"), the
> clock driver for mt8192 was not yet upstream, so the clock property nodes
> were set to the clk26m clock as a placeholder.
>
> Given that the clock driver has since been added through 710573dee31b ("clk:
> mediatek: Add MT8192 basic clocks support"), as well as its dt-bindings
> through f35f1a23e0e1 ("clk: mediatek: Add dt-bindings of MT8192 clocks") and
> devicetree nodes through 5d2b897bc6f5 ("arm64: dts: mediatek: Add mt8192
> clock controllers"), fix the uart clock property to point to the actual
> clock.
>
> Signed-off-by: Allen-KH Cheng <Allen-KH.Cheng@mediatek.com>
> Reviewed-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2022-01-13 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220113065822.11809-1-allen-kh.cheng@mediatek.com>
[not found] ` <20220113065822.11809-6-allen-kh.cheng@mediatek.com>
2022-01-13 10:03 ` [PATCH v4 5/5] arm64: dts: mediatek: Correct system timer " AngeloGioacchino Del Regno
[not found] ` <20220113065822.11809-5-allen-kh.cheng@mediatek.com>
2022-01-13 10:03 ` [PATCH v4 4/5] arm64: dts: mediatek: Correct I2C " AngeloGioacchino Del Regno
[not found] ` <20220113065822.11809-4-allen-kh.cheng@mediatek.com>
2022-01-13 10:03 ` [PATCH v4 3/5] arm64: dts: mediatek: Correct Nor Flash " AngeloGioacchino Del Regno
[not found] ` <20220113065822.11809-3-allen-kh.cheng@mediatek.com>
2022-01-13 10:03 ` [PATCH v4 2/5] arm64: dts: mediatek: Correct SPI " AngeloGioacchino Del Regno
[not found] ` <20220113065822.11809-2-allen-kh.cheng@mediatek.com>
2022-01-13 10:03 ` AngeloGioacchino Del Regno [this message]
2022-01-13 16:07 ` [PATCH v4 0/5] Update MT8192 Clock Setting Matthias Brugger
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=3eeea0ce-0551-1186-7011-9bda27d62b98@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=chun-jie.chen@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.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=nfraprado@collabora.com \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=wenst@chromium.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®