All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] spi: add support SuperH SPI module
Date: Wed, 19 Jan 2011 17:16:33 +0900	[thread overview]
Message-ID: <4D369DE1.2030704@renesas.com> (raw)
In-Reply-To: <20110118092838.62C7036C@gemini.denx.de>

Dear Wolfgang Denk,

Thank you very much for your review.

2011/01/18 18:28, Wolfgang Denk wrote:
>> @@ -37,6 +37,7 @@ COBJS-$(CONFIG_MPC8XXX_SPI) += mpc8xxx_spi.o
>>  COBJS-$(CONFIG_MXC_SPI) += mxc_spi.o
>>  COBJS-$(CONFIG_OMAP3_SPI) += omap3_spi.o
>>  COBJS-$(CONFIG_SOFT_SPI) += soft_spi.o
>> +COBJS-$(CONFIG_SH_SPI) += sh_spi.o
> 
> Please keep list sorted.
I will fix it.

>> +#define SPI_TBR		0x00
>> +#define SPI_RBR		0x00
>> +#define SPI_CR1		0x08
>> +#define SPI_CR2		0x10
>> +#define SPI_CR3		0x18
>> +#define SPI_CR4		0x20
> 
> Please declare a poper C struct instead.
I will modify it.

>> +/* CR4 */
>> +#define SPI_TBEI	0x80
>> +#define SPI_TBFI	0x40
>> +#define SPI_RBEI	0x20
>> +#define SPI_RBFI	0x10
>> +#define SPI_WPABRT	0x04
>> +#define SPI_SSS		0x01
>> +
>> +#define SPI_FIFO_SIZE	32
> 
> All this stuff should better go into a separate header file.
OK, I will create the sh_spi.h file.

>> +static void sh_spi_write(unsigned long data, unsigned long offset)
>> +{
>> +	writel(data, CONFIG_SH_SPI_BASE + offset);
> 
> NAK.  We do not allow the base + offset notation.  Pleaseuse a proper
> C struct instead.
>
> Please fix globally.
Yes, I will fix the driver.

Best regards,
Yoshihiro Shimoda

      reply	other threads:[~2011-01-19  8:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17  4:07 [U-Boot] [PATCH] spi: add support SuperH SPI module Yoshihiro Shimoda
2011-01-17 10:28 ` Nobuhiro Iwamatsu
2011-01-18  7:40   ` Yoshihiro Shimoda
2011-01-18  9:28 ` Wolfgang Denk
2011-01-19  8:16   ` Yoshihiro Shimoda [this message]

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=4D369DE1.2030704@renesas.com \
    --to=yoshihiro.shimoda.uh@renesas.com \
    --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.