All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 3/8] tegra2: spi: Add SPI driver for Tegra2 SOC
Date: Thu, 3 Nov 2011 21:36:40 -0400	[thread overview]
Message-ID: <201111032136.42310.vapier@gentoo.org> (raw)
In-Reply-To: <1320360099-28227-4-git-send-email-sjg@chromium.org>

On Thursday 03 November 2011 18:41:34 Simon Glass wrote:
> --- a/arch/arm/include/asm/arch-tegra2/tegra2.h
> +++ b/arch/arm/include/asm/arch-tegra2/tegra2.h
>
>  #define NV_PA_APB_UARTC_BASE	(NV_PA_APB_MISC_BASE + 0x6200)
>  #define NV_PA_APB_UARTD_BASE	(NV_PA_APB_MISC_BASE + 0x6300)
>  #define NV_PA_APB_UARTE_BASE	(NV_PA_APB_MISC_BASE + 0x6400)
> +#define TEGRA2_SPI_BASE		(NV_PA_APB_MISC_BASE + 0xC380)
>  #define NV_PA_PMC_BASE		0x7000E400
>  #define NV_PA_CSITE_BASE	0x70040000

shouldn't it use the same naming convention ?  NV_xxxx_SPI_BASE ?

> --- /dev/null
> +++ b/drivers/spi/tegra2_spi.c
>
> +int spi_cs_is_valid(unsigned int bus, unsigned int cs)
> +{
> +	/* Tegra2 SPI-Flash - only 1 device ('bus/cs') */
> +	if (bus > 0 && cs != 0)
> +		return 0;
> +	else
> +		return 1;
> +}

shouldn't that be "||" and not "&&" ?

> +struct spi_slave *spi_setup_slave(unsigned int bus, unsigned int cs,
> +		unsigned int max_hz, unsigned int mode)
> +{
> +	struct tegra_spi_slave *spi;
> +
> +	if (!spi_cs_is_valid(bus, cs))
> +		return NULL;
> +
> +	if (bus != 0) {
> +		printf("SPI error: unsupported bus %d\n", bus);
> +		return NULL;
> +	}
> +	if (cs != 0) {
> +		printf("SPI error: unsupported chip select %d on bus %d\n",
> +		       cs, bus);
> +		return NULL;
> +	}

doesn't spi_cs_is_valid() make these two later checks redundant ?

> +	if (mode > SPI_MODE_3) {
> +		printf("SPI error: unsupported SPI mode %i\n", mode);
> +		return NULL;
> +	}

this is weird ... i'd just drop it as this isn't something that should be in 
spi drivers, but rather the common layer (if we choose to do so)

> +int spi_xfer(struct spi_slave *slave, unsigned int bitlen,
> +		const void *data_out, void *data_in, unsigned long flags)
> +{
> ...
> +	if (bitlen & 7)
> +		return -1;

i'd use (bitlen % 8) as that is what all the other drivers are doing

> +	reg = readl(&regs->status);
> +	writel(reg, &regs->status);	/* Clear all SPI events via R/W */

are these R1C or W1C bits ?  if the latter, you could just write -1 and avoid 
the read altogether ...
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20111103/23601ddc/attachment.pgp 

  reply	other threads:[~2011-11-04  1:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03 22:41 [U-Boot] [PATCH v2 0/8] tegra2: Implement SPI flash and saved environment Simon Glass
2011-11-03 22:41 ` [U-Boot] [PATCH v2 1/8] tegra2: Tidy UART selection Simon Glass
2011-11-03 22:41 ` [U-Boot] [PATCH v2 2/8] tegra2: Add UARTB support Simon Glass
2011-11-03 22:41 ` [U-Boot] [PATCH v2 3/8] tegra2: spi: Add SPI driver for Tegra2 SOC Simon Glass
2011-11-04  1:36   ` Mike Frysinger [this message]
2011-11-05 14:36     ` Simon Glass
2011-11-05 17:13       ` Mike Frysinger
2011-11-05 19:17         ` Simon Glass
2011-11-06  8:41           ` Mike Frysinger
2011-11-03 22:41 ` [U-Boot] [PATCH v2 4/8] tegra2: config: Enable SPI flash on Seaboard Simon Glass
2011-11-03 22:41 ` [U-Boot] [PATCH v2 5/8] tegra2: Enable SPI environment " Simon Glass
2011-11-03 22:41 ` [U-Boot] [PATCH v2 6/8] tegra2: Implement SPI / UART GPIO switch Simon Glass
2011-11-04  1:44   ` Mike Frysinger
2011-11-05 14:43     ` Simon Glass
2011-11-05 17:11       ` Mike Frysinger
2011-11-05 19:05         ` Simon Glass
2011-11-03 22:41 ` [U-Boot] [PATCH v2 7/8] tegra2: spi: Support SPI / UART switch Simon Glass
2011-11-03 22:41 ` [U-Boot] [PATCH v2 8/8] tegra2: Plumb in SPI/UART switch code Simon Glass

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=201111032136.42310.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=u-boot@lists.denx.de \
    /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.