From: Krzysztof Kozlowski <krzk@kernel.org>
To: shunxi zhang <ot_shunxi.zhang@mediatek.com>,
alexandre.belloni@bootlin.com, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com, lee@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/1] rtc: mediatek: Add mt6685 RTC driver
Date: Thu, 31 Oct 2024 17:05:00 +0100 [thread overview]
Message-ID: <754e12d4-6bfa-4417-afbf-8d1353ea3ade@kernel.org> (raw)
In-Reply-To: <2ad5ebf6-fb64-4647-b9c9-c274e59fa49f@kernel.org>
On 31/10/2024 16:58, Krzysztof Kozlowski wrote:
>> + regmap_write(rtc->regmap, RG_RTC_32K_CK_PDN_CLR, RG_RTC_32K_CK_PDN_MASK);
>> + regmap_write(rtc->regmap, RG_RTC_MCLK_PDN_CLR, RG_RTC_MCLK_PDN_MASK);
>> + counter++;
>> + mdelay(1);
>> + mutex_unlock(&rtc->clk_lock);
>> +}
>> +
>> +static void power_down_mclk(struct mt6685_rtc *rtc)
>> +{
>> + mutex_lock(&rtc->clk_lock);
>> + counter--;
>> + if (counter < 0) {
>> + //dump_stack();
>> + pr_info("mclk_counter[%d]\n", counter);
>
> Oh man... So many wrong things. This applies to entire code:
> 1. Drop dead code. All dead code.
>
> 2. Do not use pr_xxx but dev_xxx
>
> 3. Drop all such useless printks because your driver is supposed to be
> silent.
>
> 4. Implement proper clock handling instead of reimplementing it yourself
> with some counters.
... clock handling or runtime PM, depending what this thing here really is.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-31 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 13:58 [PATCH 1/1] rtc: mediatek: Add mt6685 RTC driver shunxi zhang
2024-10-31 15:58 ` Krzysztof Kozlowski
2024-10-31 16:05 ` Krzysztof Kozlowski [this message]
2024-12-27 10:44 ` Shunxi Zhang (章顺喜)
2024-10-31 15:59 ` Krzysztof Kozlowski
2024-10-31 17:24 ` Alexandre Belloni
2024-10-31 19:50 ` [PATCH] " Markus Elfring
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=754e12d4-6bfa-4417-afbf-8d1353ea3ade@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=ot_shunxi.zhang@mediatek.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;
as well as URLs for NNTP newsgroup(s).