From: Javier Martinez Canillas <javierm@redhat.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Radu Rendec <rrendec@redhat.com>,
robh@kernel.org, arnd@linaro.org, linux-kernel@vger.kernel.org,
Zhipeng Wang <zhipeng.wang_1@nxp.com>,
Maxime Ripard <mripard@kernel.org>,
javier@dowhile0.org, "Rafael J. Wysocki" <rafael@kernel.org>,
linux-pm@vger.kernel.org, andreas@kemnade.info
Subject: Re: [RFC PATCH] cpufreq: dt-platdev: Fix module autoloading
Date: Mon, 25 Nov 2024 08:43:11 +0100 [thread overview]
Message-ID: <87a5dn4v3k.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <20241125051504.nvw4lzr4emi2vpf7@vireshk-i7>
Viresh Kumar <viresh.kumar@linaro.org> writes:
Hello Viresh,
> On 22-11-24, 18:09, Javier Martinez Canillas wrote:
>> Agreed with this. Likely (1) is the easiest path and (2) would make the
>> driver more aligned with the rest of the kernel (that have a list of OF
>> device IDs to autoload / match instead of some custom logic).
>>
>> But I guess that (2) would be riskier, since not adding a platform that
>> uses v2 will cause a regression.
>
> I am inclined to go with (1) here and have applied a patch from Andreas Kemnade,
> which he sent sometime back. I have used your commit log though, since it was
> more descriptive.
>
That sounds good to me, thanks for solving this issue!
> --
> viresh
>
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
next prev parent reply other threads:[~2024-11-25 7:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 11:18 [RFC PATCH] cpufreq: dt-platdev: Fix module autoloading Javier Martinez Canillas
2024-11-21 7:11 ` Viresh Kumar
2024-11-21 8:52 ` Javier Martinez Canillas
2024-11-21 9:03 ` Viresh Kumar
2024-11-21 9:13 ` Javier Martinez Canillas
2024-11-22 16:16 ` Radu Rendec
2024-11-22 17:09 ` Javier Martinez Canillas
2024-11-25 5:15 ` Viresh Kumar
2024-11-25 7:43 ` Javier Martinez Canillas [this message]
2024-11-25 9:01 ` Maxime Ripard
2024-11-25 9:22 ` Javier Martinez Canillas
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=87a5dn4v3k.fsf@minerva.mail-host-address-is-not-set \
--to=javierm@redhat.com \
--cc=andreas@kemnade.info \
--cc=arnd@linaro.org \
--cc=javier@dowhile0.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rrendec@redhat.com \
--cc=viresh.kumar@linaro.org \
--cc=zhipeng.wang_1@nxp.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