From: Dan Carpenter <dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: pandy.gao-3arQi8VN3Tc@public.gmane.org
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [bug report] spi: imx: add lpspi bus driver
Date: Thu, 24 Nov 2016 01:57:19 +0300 [thread overview]
Message-ID: <20161123225719.GA16302@mwanda> (raw)
Hello Gao Pan,
The patch 5314987de5e5: "spi: imx: add lpspi bus driver" from Nov 22,
2016, leads to the following static checker warning:
drivers/spi/spi-fsl-lpspi.c:220 fsl_lpspi_set_cmd()
warn: potential shift truncation. '0x11 << 30'
drivers/spi/spi-fsl-lpspi.c
213 static void fsl_lpspi_set_cmd(struct fsl_lpspi_data *fsl_lpspi,
214 bool is_first_xfer)
215 {
216 u32 temp = 0;
217
218 temp |= fsl_lpspi->config.bpw - 1;
219 temp |= fsl_lpspi->config.prescale << 27;
220 temp |= (fsl_lpspi->config.mode & 0x11) << 30;
Are you sure you didn't intend to write:
temp |= (fsl_lpspi->config.mode & 0x3) << 30;
The current code doesn't make sense at any rate.
221 temp |= (fsl_lpspi->config.chip_select & 0x3) << 24;
222
223 /*
224 * Set TCR_CONT will keep SS asserted after current transfer.
225 * For the first transfer, clear TCR_CONTC to assert SS.
226 * For subsequent transfer, set TCR_CONTC to keep SS asserted.
227 */
228 temp |= TCR_CONT;
229 if (is_first_xfer)
230 temp &= ~TCR_CONTC;
231 else
232 temp |= TCR_CONTC;
233
234 writel(temp, fsl_lpspi->base + IMX7ULP_TCR);
235
236 dev_dbg(fsl_lpspi->dev, "TCR=0x%x\n", temp);
237 }
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-11-23 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 22:57 Dan Carpenter [this message]
2016-11-24 1:36 ` [bug report] spi: imx: add lpspi bus driver Pandy Gao
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=20161123225719.GA16302@mwanda \
--to=dan.carpenter-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pandy.gao-3arQi8VN3Tc@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.