From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 1/2] usb: dwc3: am62: Use HZ_PER_KHZ
Date: Mon, 17 Feb 2025 15:45:42 +0100 [thread overview]
Message-ID: <20250217144543.1777605-1-s.hauer@pengutronix.de> (raw)
Use HZ_PER_KHZ to make intention clear and drop now unnecessary comment.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
drivers/usb/dwc3/dwc3-am62.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/dwc3/dwc3-am62.c b/drivers/usb/dwc3/dwc3-am62.c
index fd7f5e54d2..7dac8981fb 100644
--- a/drivers/usb/dwc3/dwc3-am62.c
+++ b/drivers/usb/dwc3/dwc3-am62.c
@@ -203,7 +203,7 @@ static int dwc3_ti_probe(struct device *dev)
/* Calculate the rate code */
rate = clk_get_rate(am62->usb2_refclk);
- rate /= 1000; // To KHz
+ rate /= HZ_PER_KHZ;
for (i = 0; i < ARRAY_SIZE(dwc3_ti_rate_table); i++) {
if (dwc3_ti_rate_table[i] == rate)
break;
--
2.39.5
next reply other threads:[~2025-02-17 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 14:45 Sascha Hauer [this message]
2025-02-17 14:45 ` [PATCH 2/2] usb: dwc3: am62: set mode valid bit before probing children Sascha Hauer
2025-02-18 14:05 ` [PATCH 1/2] usb: dwc3: am62: Use HZ_PER_KHZ Sascha Hauer
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=20250217144543.1777605-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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