From: Stephen Boyd <sboyd@kernel.org>
To: Rahul Tanwar <rtanwar@maxlinear.com>,
linux-clk@vger.kernel.org, mturquette@baylibre.com,
yzhu@maxlinear.com
Cc: linux-kernel@vger.kernel.org, linux-lgm-soc@maxlinear.com,
Rahul Tanwar <rtanwar@maxlinear.com>
Subject: Re: [PATCH v4 1/4] clk: mxl: Switch from direct readl/writel based IO to regmap based IO
Date: Mon, 17 Oct 2022 15:28:43 -0700 [thread overview]
Message-ID: <20221017222845.2F688C433D6@smtp.kernel.org> (raw)
In-Reply-To: <2610331918206e0e3bd18babb39393a558fb34f9.1665642720.git.rtanwar@maxlinear.com>
Quoting Rahul Tanwar (2022-10-12 23:48:30)
> Earlier version of driver used direct io remapped register read
> writes using readl/writel. But we need secure boot access which
> is only possible when registers are read & written using regmap.
> This is because the security bus/hook is written & coupled only
> with regmap layer.
>
> Switch the driver from direct readl/writel based register accesses
> to regmap based register accesses.
>
> Additionally, update the license headers to latest status.
>
> Reviewed-by: Yi xin Zhu <yzhu@maxlinear.com>
> Signed-off-by: Rahul Tanwar <rtanwar@maxlinear.com>
> ---
Applied to clk-next
next prev parent reply other threads:[~2022-10-17 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 6:48 [PATCH v4 0/4] Modify MxL's CGU clk driver to make it secure boot compatible Rahul Tanwar
2022-10-13 6:48 ` [PATCH v4 1/4] clk: mxl: Switch from direct readl/writel based IO to regmap based IO Rahul Tanwar
2022-10-17 22:28 ` Stephen Boyd [this message]
2022-10-13 6:48 ` [PATCH v4 2/4] clk: mxl: Remove redundant spinlocks Rahul Tanwar
2022-10-17 22:28 ` Stephen Boyd
2022-10-13 6:48 ` [PATCH v4 3/4] clk: mxl: Add option to override gate clks Rahul Tanwar
2022-10-17 22:28 ` Stephen Boyd
2022-10-13 6:48 ` [PATCH v4 4/4] clk: mxl: Fix a clk entry by adding relevant flags Rahul Tanwar
2022-10-17 22:29 ` Stephen Boyd
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=20221017222845.2F688C433D6@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lgm-soc@maxlinear.com \
--cc=mturquette@baylibre.com \
--cc=rtanwar@maxlinear.com \
--cc=yzhu@maxlinear.com \
/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®