From: Kartik Rajput <kkartik@nvidia.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: alexandre.belloni@bootlin.com, thierry.reding@gmail.com,
jonathanh@nvidia.com, linux-rtc@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtc: tegra: Add ACPI support
Date: Tue, 21 Oct 2025 12:06:56 +0530 [thread overview]
Message-ID: <e03ab196-c204-4e2f-b69e-400b464e3d21@nvidia.com> (raw)
In-Reply-To: <aO9Vmfm6jPplEQca@smile.fi.intel.com>
Hi Andy,
Thanks for reviewing the patch!
On 15/10/25 13:34, Andy Shevchenko wrote:
> External email: Use caution opening links or attachments
>
>
> On Fri, Sep 19, 2025 at 04:42:32PM +0530, Kartik Rajput wrote:
>> Add ACPI support for Tegra RTC, which is available on Tegra241 and
>> Tegra410. Both Tegra241 and Tegra410 use the same ACPI ID 'NVDA0280'.
>> The RTC clock is configured by UEFI before the kernel boots.
>
> ...
>
>> +#include <linux/acpi.h>
>
> No use.
>
Ack.
> ...
>
>> +static const struct acpi_device_id tegra_rtc_acpi_match[] = {
>> + { "NVDA0280", 0 },
>
> Drop redundant ', 0' part.
>
Ack.
>> + { }
>> +};
>
> ...
>
>> + if (is_of_node(dev_fwnode(&pdev->dev))) {
>
> Simple dev_of_node() will work here
>
Ack.
>> + info->clk = devm_clk_get(&pdev->dev, NULL);
>> + if (IS_ERR(info->clk))
>> + return PTR_ERR(info->clk);
>>
>> + ret = clk_prepare_enable(info->clk);
>> + if (ret < 0)
>> + return ret;
>> + }
>
> ...
>
>> disable_clk:
>> - clk_disable_unprepare(info->clk);
>> + if (is_of_node(dev_fwnode(&pdev->dev)))
>> + clk_disable_unprepare(info->clk);
>
> Redundant change. CLK APIs are NULL aware.
>
Ack. I will drop this check.
> ...
>
>> - clk_disable_unprepare(info->clk);
>> + if (is_of_node(dev_fwnode(&pdev->dev)))
>> + clk_disable_unprepare(info->clk);
>
> Ditto.
>
Ack.
> --
> With Best Regards,
> Andy Shevchenko
>
>
Thanks,
Kartik
prev parent reply other threads:[~2025-10-21 6:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 11:12 Kartik Rajput
2025-09-20 2:09 ` kernel test robot
2025-10-15 8:04 ` Andy Shevchenko
2025-10-21 6:36 ` Kartik Rajput [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=e03ab196-c204-4e2f-b69e-400b464e3d21@nvidia.com \
--to=kkartik@nvidia.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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®