public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Lee Jones <lee@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: sm501: Remove unused sm501_find_clock
Date: Fri, 9 May 2025 17:36:10 +0000	[thread overview]
Message-ID: <aB49Co-q19pf3yO0@gallifrey> (raw)
In-Reply-To: <20250509142945.GH2492385@google.com>

* Lee Jones (lee@kernel.org) wrote:
> On Thu, 08 May 2025, linux@treblig.org wrote:
> 
> > From: "Dr. David Alan Gilbert" <linux@treblig.org>
> > 
> > sm501_find_clock() was added in 2007 as part of
> > commit b6d6454fdb66 ("[PATCH] mfd: SM501 core driver")
> > but hasn't been used.
> > 
> > Remove it.
> > 
> > Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
> > ---
> >  drivers/mfd/sm501.c | 43 -------------------------------------------
> 
> Looks like you missed: include/linux/sm501.h.

Oops! Sorry about that, v2 posted; message id 20250509173521.49596-1-linux@treblig.org

Thanks for the review,

Dave

> >  1 file changed, 43 deletions(-)
> > 
> > diff --git a/drivers/mfd/sm501.c b/drivers/mfd/sm501.c
> > index 7ee293b09f62..bdeea0047e1b 100644
> > --- a/drivers/mfd/sm501.c
> > +++ b/drivers/mfd/sm501.c
> > @@ -631,49 +631,6 @@ unsigned long sm501_set_clock(struct device *dev,
> >  
> >  EXPORT_SYMBOL_GPL(sm501_set_clock);
> >  
> > -/* sm501_find_clock
> > - *
> > - * finds the closest available frequency for a given clock
> > -*/
> > -
> > -unsigned long sm501_find_clock(struct device *dev,
> > -			       int clksrc,
> > -			       unsigned long req_freq)
> > -{
> > -	struct sm501_devdata *sm = dev_get_drvdata(dev);
> > -	unsigned long sm501_freq; /* the frequency achieveable by the 501 */
> > -	struct sm501_clock to;
> > -
> > -	switch (clksrc) {
> > -	case SM501_CLOCK_P2XCLK:
> > -		if (sm->rev >= 0xC0) {
> > -			/* SM502 -> use the programmable PLL */
> > -			sm501_freq = (sm501_calc_pll(2 * req_freq,
> > -						     &to, 5) / 2);
> > -		} else {
> > -			sm501_freq = (sm501_select_clock(2 * req_freq,
> > -							 &to, 5) / 2);
> > -		}
> > -		break;
> > -
> > -	case SM501_CLOCK_V2XCLK:
> > -		sm501_freq = (sm501_select_clock(2 * req_freq, &to, 3) / 2);
> > -		break;
> > -
> > -	case SM501_CLOCK_MCLK:
> > -	case SM501_CLOCK_M1XCLK:
> > -		sm501_freq = sm501_select_clock(req_freq, &to, 3);
> > -		break;
> > -
> > -	default:
> > -		sm501_freq = 0;		/* error */
> > -	}
> > -
> > -	return sm501_freq;
> > -}
> > -
> > -EXPORT_SYMBOL_GPL(sm501_find_clock);
> > -
> >  static struct sm501_device *to_sm_device(struct platform_device *pdev)
> >  {
> >  	return container_of(pdev, struct sm501_device, pdev);
> > -- 
> > 2.49.0
> > 
> 
> -- 
> Lee Jones [李琼斯]
-- 
 -----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   |_______/

      reply	other threads:[~2025-05-09 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08  0:22 [PATCH] mfd: sm501: Remove unused sm501_find_clock linux
2025-05-09 14:29 ` Lee Jones
2025-05-09 17:36   ` Dr. David Alan Gilbert [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=aB49Co-q19pf3yO0@gallifrey \
    --to=linux@treblig.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.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