From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PM / devfreq: Remove unused devm_devfreq_(un)register_notifier
Date: Sat, 7 Dec 2024 12:47:24 +0000 [thread overview]
Message-ID: <Z1RD3Ec1IJ2jY5TZ@gallifrey> (raw)
In-Reply-To: <20241207052209epcms1p45818db425ba84821003b6d735bc0e957@epcms1p4>
* MyungJoo Ham (myungjoo.ham@samsung.com) wrote:
> >* linux@treblig.org (linux@treblig.org) wrote:
> >> From: "Dr. David Alan Gilbert" <linux@treblig.org>
> >>
> >> devm_devfreq_register_notifier() and devm_devfreq_unregister_notifier()
> >> have been unused since 2019's
> >> commit 0ef7c7cce43f ("PM / devfreq: passive: Use non-devm notifiers")
> >>
> >> Remove them, and the helpers they used.
> >>
> >> Note, devm_devfreq_register_notifier() is still used as an example
> >> in Documentation/doc-guide/contributing.rst but that's just
> >> an example of an old doc bug rather than anything about the function
> >> itself.
> >>
> >> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
> >
> >Ping.
> >
> >Thanks,
> >
> >Dave
>
> When I search github, it appears that vendors are using this API.
Hmm OK.
Of course there's a lot of random junk on github, so it can be tricky
to know what's current/real/relevant.
> NVIDIA:
> https://github.com/NX-Development/android_kernel_nvidia_nvidia/blob/c9ade3b5e32a12b8cf6f33a632dc39209194e4e8/drivers/devfreq/governor_wmark_active.c#L624
>
> Samsung:
> https://github.com/Vaz15k/android_kernel_samsung_a54x/blob/8ac517c37c606746213064857dc240e99eba80d2/drivers/soc/samsung/exynos-llcgov.c#L107
>
> Realtek:
> https://github.com/BPI-SINOVOIP/BPI-M4-bsp/blob/25f5b88ec4ba34029f964693dc34028b26e6c67c/linux-rtk/drivers/devfreq/realtek/governor_rtk_ltl.c#L114
>
>
>
> Please don't remove ABIs used by vendors even if
> they didn't upstream their drivers.
Hmm OK.
Do you think they should be using this ABI or do they have the same bug as
is fixed in 0ef7c7cce43f ?
I guess they don't care.
Dave
> Cheers,
> MyungJoo.
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2024-12-07 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 2:13 [PATCH] PM / devfreq: Remove unused devm_devfreq_(un)register_notifier linux
2024-11-28 16:11 ` Dr. David Alan Gilbert
2024-12-07 5:22 ` MyungJoo Ham
2024-12-07 12:47 ` Dr. David Alan Gilbert [this message]
2024-12-08 12:52 ` Chanwoo Choi
2024-12-09 5:50 ` MyungJoo Ham
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=Z1RD3Ec1IJ2jY5TZ@gallifrey \
--to=linux@treblig.org \
--cc=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.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