From: Stephen Boyd <sboyd@kernel•org>
To: Chen-Yu Tsai <wenst@chromium•org>,
Chun-Jie Chen <chun-jie.chen@mediatek•com>
Cc: Matthias Brugger <matthias.bgg@gmail•com>,
Nicolas Boichat <drinkcat@chromium•org>,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org, linux-mediatek@lists•infradead.org,
linux-clk@vger•kernel.org, srv_heupstream@mediatek•com,
Project_Global_Chrome_Upstream_Group@mediatek•com
Subject: Re: [v1] clk: mediatek: use en_mask as a pure div_en_mask
Date: Thu, 06 Jan 2022 18:34:50 -0800 [thread overview]
Message-ID: <20220107023451.7C52CC36AEB@smtp.kernel.org> (raw)
In-Reply-To: <CAGXv+5G5vnOuW46q7b7m6BDS+R4vCLJehrofjfv95uOFbwyzEg@mail.gmail.com>
Quoting Chen-Yu Tsai (2021-11-09 22:59:37)
> Hi,
>
> On Wed, Nov 10, 2021 at 10:23 AM Chun-Jie Chen
> <chun-jie.chen@mediatek•com> wrote:
> >
> > We no longer allow en_mask to be a combination of
> > pll_en_bit and div_en_mask, so remove pll_en_bit(bit0)
> > from en_mask to make en_mask a pure en_mask that only
> > used for pll dividers.
>
> AFAICT this looks like it continues the work done in commit 7cc4e1bbe300
> ("clk: mediatek: Fix asymmetrical PLL enable and disable control") and
> commit f384c44754b7 ("clk: mediatek: Add configurable enable control to
> mtk_pll_data").
>
> It would be nice if you could mention this in your commit log to provide
> more context.
Please resend.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-01-07 2:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 2:22 [v1] clk: mediatek: use en_mask as a pure div_en_mask Chun-Jie Chen
2021-11-10 6:59 ` Chen-Yu Tsai
2022-01-07 2:34 ` Stephen Boyd [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=20220107023451.7C52CC36AEB@smtp.kernel.org \
--to=sboyd@kernel$(echo .)org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek$(echo .)com \
--cc=chun-jie.chen@mediatek$(echo .)com \
--cc=drinkcat@chromium$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-clk@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mediatek@lists$(echo .)infradead.org \
--cc=matthias.bgg@gmail$(echo .)com \
--cc=srv_heupstream@mediatek$(echo .)com \
--cc=wenst@chromium$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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