From: Mark Brown <broonie@kernel.org>
To: Purna Chandra Mandal <purna.mandal@microchip.com>
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Joshua Henderson <digitalpeer@digitalpeer.com>
Subject: Re: [PATCH v4 2/2] spi: spi-pic32: Add PIC32 SPI master driver
Date: Mon, 28 Mar 2016 12:26:29 -0700 [thread overview]
Message-ID: <20160328192629.GG2350@sirena.org.uk> (raw)
In-Reply-To: <1458740576-9168-2-git-send-email-purna.mandal@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 2774 bytes --]
On Wed, Mar 23, 2016 at 07:12:56PM +0530, Purna Chandra Mandal wrote:
> + switch (bits_per_word) {
> + default:
> + case 8:
Are you sure that all bits per word settings other than those explicitly
supported should be handled in exactly the same fashion as 8 bits per
word? That doesn't seem entirely expected. I'd expect the default to
be to return an error.
> +static int pic32_spi_prepare_message(struct spi_master *master,
> + struct spi_message *msg)
> +{
> + struct spi_device *spi = msg->spi;
> + struct spi_transfer *xfer;
> + struct pic32_spi *pic32s;
> +
> + pic32s = spi_master_get_devdata(master);
> +
> + pic32s->mesg = msg;
> + pic32_spi_disable_chip(pic32s);
> +
> + if (!pic32_spi_debug)
> + return 0;
This appears to be some half implemented debugging code which is never
enabled, please remove it.
> + list_for_each_entry(xfer, &msg->transfers, transfer_list) {
> + dev_dbg(&spi->dev, " xfer %p: len %u tx %p rx %p\n",
> + xfer, xfer->len, xfer->tx_buf, xfer->rx_buf);
> + print_hex_dump(KERN_DEBUG, "tx_buf ",
> + DUMP_PREFIX_ADDRESS,
> + 16, 1, xfer->tx_buf,
> + min_t(u32, xfer->len, 16), 1);
> + }
Similarly here, the core already has extensive trace stuff in it which
you can use.
> + /* transact by DMA mode */
> + if (transfer->rx_sg.nents && transfer->tx_sg.nents) {
> + ret = pic32_spi_dma_transfer(pic32s, transfer);
> + if (ret) {
> + dev_err(&spi->dev, "dma submit error\n");
> + return ret;
> + }
> +
> + /* DMA issued, wait for completion */
> + set_bit(PIC32F_DMA_ISSUED, &pic32s->flags);
> + goto out_wait_for_xfer;
> + }
...
> +
> +out_wait_for_xfer:
Please write normal code with an if/else rather than using gotos, it's a
lot easier to follow.
> + pic32s = spi_master_get_devdata(master);
> +
> + pic32_spi_disable_chip(pic32s);
Do we really need tod isable the hardware after every single message?
It's normally more efficient to just leave the hardware powered until it
goes idle and unprepare_transfer_hardware() is called.
> + /* SPI master supports only one spi-device at a time.
> + * So multiple spi_setup() to different devices is not allowed.
> + */
> + if (unlikely(pic32s->spi_dev && (pic32s->spi_dev != spi))) {
unlikely() is for fast paths, outside of them it's just noise.
> + /* But spi_setup() can be called multiple times by same device.
> + * In that case stop current on-going transaction and release
> + * resource(s).
> + */
> + if (pic32s->spi_dev == spi)
> + pic32_spi_cleanup(spi);
This is broken, it will break in progress transfers. setup() shouldn't
be doing anything that disrupts them, anything that can't be run when
other transfers are in progress needs to be deferred till we actually do
the transfers (or done earlier in probe).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-29 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 13:42 [PATCH v4 1/2] dt/bindings: Add bindings for PIC32 SPI peripheral Purna Chandra Mandal
2016-03-23 13:42 ` [PATCH v4 2/2] spi: spi-pic32: Add PIC32 SPI master driver Purna Chandra Mandal
2016-03-28 19:26 ` Mark Brown [this message]
2016-03-29 12:02 ` Purna Chandra Mandal
2016-03-29 16:25 ` Mark Brown
2016-03-30 10:49 ` Purna Chandra Mandal
2016-03-30 15:48 ` Mark Brown
2016-03-31 11:09 ` Purna Chandra Mandal
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=20160328192629.GG2350@sirena.org.uk \
--to=broonie@kernel.org \
--cc=digitalpeer@digitalpeer.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=purna.mandal@microchip.com \
--cc=sergei.shtylyov@cogentembedded.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
Powered by JetHome