From: Greg KH <greg@kroah.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: abelvesa@kernel.org, mturquette@baylibre.com, sboyd@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH] clk: imx: imx93: introduce clk_bypassed module parameter
Date: Thu, 4 May 2023 18:10:42 +0900 [thread overview]
Message-ID: <2023050410-rejoin-vocation-8560@gregkh> (raw)
In-Reply-To: <20230504085506.504474-1-peng.fan@oss.nxp.com>
On Thu, May 04, 2023 at 04:55:06PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> With the clk names specified in clk_bypassed module parameter, give
> user an option to bypass the clk from managing them by Linux kernel.
As I said on another email, no, please do not add new module parameters
for drivers, this is not the 1990s
Also, another comment below:
> @@ -310,6 +357,8 @@ static int imx93_clocks_probe(struct platform_device *pdev)
>
> for (i = 0; i < ARRAY_SIZE(root_array); i++) {
> root = &root_array[i];
> + if (unlikely(imx_clk_bypass_check(root->name)))
> + continue;
Only ever use likely/unlikely if you can measure the difference. Here
on a probe function, you can not, this is not needed at all, the
compiler and CPU will do a better job over time than you can guess at
this.
But as this change isn't needed, this shouldn't be an issue either.
thanks,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-05-04 9:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 8:55 [PATCH] clk: imx: imx93: introduce clk_bypassed module parameter Peng Fan (OSS)
2023-05-04 9:10 ` Greg KH [this message]
2023-05-04 9:17 ` Peng Fan
2023-05-04 9:30 ` Krzysztof Kozlowski
2023-05-04 9:34 ` Peng Fan
2023-05-04 10:04 ` Ahmad Fatoum
2023-05-04 11:37 ` Peng Fan
2023-05-04 11:01 ` Krzysztof Kozlowski
2023-05-04 11:39 ` Peng Fan
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=2023050410-rejoin-vocation-8560@gregkh \
--to=greg@kroah.com \
--cc=abelvesa@kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@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