From: jesszhan@codeaurora.org
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: seanpaul@chromium.org, linux-arm-msm@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [bug report] drm/msm: dsi: Handle dual-channel for 6G as well
Date: Fri, 01 Oct 2021 11:58:15 -0700 [thread overview]
Message-ID: <baf1fcba58b05c90a0c7e2200a22ead1@codeaurora.org> (raw)
In-Reply-To: <20211001123115.GE2283@kili>
Hey Dan,
Thanks for the report, will take care of it.
On 2021-10-01 05:31, Dan Carpenter wrote:
> Hello Sean Paul,
>
> The patch a6bcddbc2ee1: "drm/msm: dsi: Handle dual-channel for 6G as
> well" from Jul 25, 2018, leads to the following
> Smatch static checker warning:
>
> drivers/gpu/drm/msm/dsi/dsi_host.c:729 dsi_calc_clk_rate_6g()
> warn: wrong type for 'msm_host->esc_clk_rate' (should be 'ulong')
>
> drivers/gpu/drm/msm/dsi/dsi_host.c
> 721 int dsi_calc_clk_rate_6g(struct msm_dsi_host *msm_host, bool
> is_bonded_dsi)
> 722 {
> 723 if (!msm_host->mode) {
> 724 pr_err("%s: mode not set\n", __func__);
> 725 return -EINVAL;
> 726 }
> 727
> 728 dsi_calc_pclk(msm_host, is_bonded_dsi);
> --> 729 msm_host->esc_clk_rate =
> clk_get_rate(msm_host->esc_clk);
> ^^^^^^^^^^^^^^^^^^^^^^
> I don't know why Smatch is suddenly warning about ancient msm code, but
> clock rates should be unsigned long. (I don't remember why).
>
> 730 return 0;
> 731 }
>
> regards,
> dan carpenter
Thanks,
Jessica Zhang
next prev parent reply other threads:[~2021-10-01 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 12:31 [bug report] drm/msm: dsi: Handle dual-channel for 6G as well Dan Carpenter
2021-10-01 18:58 ` jesszhan [this message]
2021-10-15 1:43 ` Jessica Zhang
2021-10-15 8:12 ` Dan Carpenter
2021-10-15 16:58 ` Jessica Zhang
2021-10-15 18:24 ` Dmitry Baryshkov
2021-10-15 19:34 ` Jessica Zhang
2021-10-16 19:35 ` Dan Carpenter
2021-10-18 18:03 ` Jessica Zhang
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=baf1fcba58b05c90a0c7e2200a22ead1@codeaurora.org \
--to=jesszhan@codeaurora.org \
--cc=dan.carpenter@oracle.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=seanpaul@chromium.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;
as well as URLs for NNTP newsgroup(s).