Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Wang <sean.wang@mediatek.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-clk@vger.kernel.org, linux-mediatek@lists.infradead.org,
	sboyd@codeaurora.org
Subject: Re: [bug report] clk: mediatek: add missing cpu mux causing Mediatek cpufreq can't work
Date: Sat, 8 Jul 2017 14:39:44 +0800	[thread overview]
Message-ID: <1499495984.16278.13.camel@mtkswgap22> (raw)
In-Reply-To: <20170707095331.s7zlvk5hbqwgngld@mwanda>

Hi Dan, 

	thank you for reporting the defect, I will handle this int next days.
	Sean

On Fri, 2017-07-07 at 12:53 +0300, Dan Carpenter wrote:
> Hello Sean Wang,
> 
> The patch 1e17de9049da: "clk: mediatek: add missing cpu mux causing
> Mediatek cpufreq can't work" from May 5, 2017, leads to the following
> static checker warning:
> 
> 	drivers/clk/mediatek/clk-cpumux.c:39 clk_cpumux_get_parent()
> 	warn: signedness bug returning '(-22)'
> 
> drivers/clk/mediatek/clk-cpumux.c
>     27  static u8 clk_cpumux_get_parent(struct clk_hw *hw)
>     28  {
>     29          struct mtk_clk_cpumux *mux = to_mtk_clk_cpumux(hw);
>     30          int num_parents = clk_hw_get_num_parents(hw);
>     31          unsigned int val;
>     32  
>     33          regmap_read(mux->regmap, mux->reg, &val);
>     34  
>     35          val >>= mux->shift;
>     36          val &= mux->mask;
>     37  
>     38          if (val >= num_parents)
>     39                  return -EINVAL;
>                         ^^^^^^^^^^^^^^
> Doesn't work for u8.
> 
>     40  
>     41          return val;
>     42  }
> 
> regards,
> dan carpenter



           reply	other threads:[~2017-07-08  6:39 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20170707095331.s7zlvk5hbqwgngld@mwanda>]

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=1499495984.16278.13.camel@mtkswgap22 \
    --to=sean.wang@mediatek.com \
    --cc=dan.carpenter@oracle.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=sboyd@codeaurora.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