From: Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-F5mvAk5X5gdBDgjK7y7TUQ@public.gmane.org,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/4] spi: Add new driver for STMicroelectronics' SPI Controller
Date: Thu, 27 Nov 2014 15:05:08 +0000 [thread overview]
Message-ID: <20141127150508.GI4628@x1> (raw)
In-Reply-To: <20141127125904.GV7712-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
[...]
> > +struct spi_st {
> > + /* SSC SPI Controller */
> > + struct spi_bitbang bitbang;
>
> Is there a good reason for using bitbang over the core transmit_one()
> interface? The operations are basically the same but more modern and
> the functionality is more discoverable.
I don't know enough about SPI to answer that question. I will look
into moving over to transmit_one(). Most of the design decisions in
this driver were taken back when you were probably wearing denim
jackets and supporting an afro. ;)
> > + } else if (spi_st->bits_per_word == 8 && !(t->len & 0x1)) {
> > + /*
> > + * If transfer is even-length, and 8 bits-per-word, then
> > + * implement as half-length 16 bits-per-word transfer
> > + */
> > + spi_st->bytes_per_word = 2;
> > + spi_st->words_remaining = t->len/2;
> > +
> > + /* Set SSC_CTL to 16 bits-per-word */
> > + ctl = readl_relaxed(spi_st->base + SSC_CTL);
> > + writel_relaxed((ctl | 0xf), spi_st->base + SSC_CTL);
> > +
> > + readl_relaxed(spi_st->base + SSC_RBUF);
>
> No byte swapping issues here?
I think this implementation has been pretty heavily tested. What
should I be looking out for?
[...]
> > + printk("LEE: %s: %s()[%d]: Probing\n", __FILE__, __func__, __LINE__);
>
> Tsk.
School boy error!
> > + spi_st->clk = of_clk_get_by_name(np, "ssc");
> > + if (IS_ERR(spi_st->clk)) {
> > + dev_err(&pdev->dev, "Unable to request clock\n");
> > + ret = PTR_ERR(spi_st->clk);
> > + goto free_master;
> > + }
>
> Why is this of_get_clk_by_name() and not just devm_clk_get()?
Probably historical and I didn't notice.
I'll look into swapping it over.
[...]
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-11-27 15:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 11:43 [PATCH 0/4] spi: st: New driver for ST's SPI Controller Lee Jones
2014-11-27 11:43 ` [PATCH 1/4] spi: Add new driver for STMicroelectronics' " Lee Jones
2014-11-27 12:33 ` [STLinux Kernel] " Peter Griffin
[not found] ` <1417088636-11994-2-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-11-27 12:59 ` Mark Brown
[not found] ` <20141127125904.GV7712-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-11-27 15:05 ` Lee Jones [this message]
2014-11-27 16:24 ` Mark Brown
2014-11-27 13:24 ` Maxime Coquelin
2014-11-27 11:43 ` [PATCH 2/4] spi: st: Provide Device Tree binding documentation Lee Jones
[not found] ` <1417088636-11994-3-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-11-27 13:00 ` Mark Brown
[not found] ` <20141127130053.GW7712-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-11-27 14:55 ` Lee Jones
2014-11-27 16:30 ` Mark Brown
[not found] ` <1417088636-11994-1-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-11-27 11:43 ` [PATCH 3/4] ARM: sti: Provide DT nodes for SSC[0..4] Lee Jones
2014-11-27 11:43 ` [PATCH 4/4] ARM: sti: Provide DT nodes for SBC SSC[0..2] Lee Jones
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=20141127150508.GI4628@x1 \
--to=lee.jones-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-F5mvAk5X5gdBDgjK7y7TUQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@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 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).