From: Stephen Boyd <sboyd@kernel.org>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
mturquette@baylibre.com
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
edward-jw.yang@mediatek.com, johnson.wang@mediatek.com,
wenst@chromium.org, miles.chen@mediatek.com,
chun-jie.chen@mediatek.com, rex-bc.chen@mediatek.com,
jose.exposito89@gmail.com, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH v1 0/6] MediaTek Frequency Hopping: MT6795/8173/92/95
Date: Wed, 25 Jan 2023 18:07:32 -0800 [thread overview]
Message-ID: <5036f36916e12429d6f853049a2e5836.sboyd@kernel.org> (raw)
In-Reply-To: <20221222155147.158837-1-angelogioacchino.delregno@collabora.com>
Quoting AngeloGioacchino Del Regno (2022-12-22 07:51:41)
> This series adds support for Frequency Hopping (FHCTL) on more MediaTek
> SoCs, specifically, MT6795, MT8173, MT8192 and MT8195.
>
> In order to support older platforms like MT6795 and MT8173 it was
> necessary to add a new register layout that is ever-so-slightly
> different from the one that was previously introduced for MT8186.
>
> Since the new layout refers to older SoCs, the one valid for MT8186
> and newer SoCs was renamed to be a "v2" layout, while the new one
> for older chips gets the "v1" name.
>
> Note: These commits won't change any behavior unless FHCTL gets
> explicitly enabled and configured in devicetrees.
Can you resend this? It conflicts with your latest cleanup series.
next prev parent reply other threads:[~2023-01-26 2:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 15:51 [PATCH v1 0/6] MediaTek Frequency Hopping: MT6795/8173/92/95 AngeloGioacchino Del Regno
2022-12-22 15:51 ` [PATCH v1 1/6] clk: mediatek: fhctl: Add support for older fhctl register layout AngeloGioacchino Del Regno
2022-12-22 15:51 ` [PATCH v1 2/6] dt-bindings: clock: mediatek,mt8186-fhctl: Support MT6795, MT8173/92/95 AngeloGioacchino Del Regno
2022-12-22 20:32 ` Rob Herring
2022-12-22 15:51 ` [PATCH v1 3/6] clk: mediatek: mt6795: Add support for frequency hopping through FHCTL AngeloGioacchino Del Regno
2022-12-22 15:51 ` [PATCH v1 4/6] clk: mediatek: mt8173: " AngeloGioacchino Del Regno
2022-12-22 15:51 ` [PATCH v1 5/6] clk: mediatek: mt8192: " AngeloGioacchino Del Regno
2022-12-22 15:51 ` [PATCH v1 6/6] clk: mediatek: mt8195: " AngeloGioacchino Del Regno
2022-12-22 15:54 ` [PATCH v1 0/6] MediaTek Frequency Hopping: MT6795/8173/92/95 AngeloGioacchino Del Regno
2023-01-26 2:07 ` Stephen Boyd [this message]
2023-01-26 8:42 ` AngeloGioacchino Del Regno
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=5036f36916e12429d6f853049a2e5836.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chun-jie.chen@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=edward-jw.yang@mediatek.com \
--cc=johnson.wang@mediatek.com \
--cc=jose.exposito89@gmail.com \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=miles.chen@mediatek.com \
--cc=mturquette@baylibre.com \
--cc=rex-bc.chen@mediatek.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).