From: "Bi, Chao" <chao.bi@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Alan Cox <alan@linux.intel.com>,
"Gorby, Russ" <russ.gorby@intel.com>,
"Chen, Jun D" <jun.d.chen@intel.com>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] serial:ifx6x60:Keep word size accordance with SPI controller
Date: Wed, 16 Jan 2013 04:57:40 +0000 [thread overview]
Message-ID: <253F3AA5ECB4EC43A2CA0147545F67F2102CE29F@SHSMSX102.ccr.corp.intel.com> (raw)
In-Reply-To: <20130116025028.GA29056@kroah.com>
Sorry for that, please check my resubmitted patch right now.
Thanks,
Chao
-----Original Message-----
From: Greg KH [mailto:gregkh@linuxfoundation.org]
Sent: Wednesday, January 16, 2013 10:50 AM
To: Bi, Chao
Cc: Alan Cox; Gorby, Russ; Chen, Jun D; linux-serial@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial:ifx6x60:Keep word size accordance with SPI controller
On Wed, Dec 12, 2012 at 01:07:06PM +0800, chao bi wrote:
>
> As protocol driver, IFX SPI driver initiate to setup SPI master with
> default SPI word size as 16 bit/word, however, SPI master may not
> adopt this default value due to SPI controller's capability, it might
> choose an available value by itself and set it to
> spi_device.bits_per_word. In order to keep align with Controller, IFX
> driver should make use of this value during SPI transfer, but the default one.
>
> Signed-off-by: Chen Jun <jun.d.chen@intel.com>
> Signed-off-by: channing <chao.bi@intel.com>
> ---
> drivers/tty/serial/ifx6x60.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/tty/serial/ifx6x60.c
> b/drivers/tty/serial/ifx6x60.c index 675d94a..5919992 100644
> --- a/drivers/tty/serial/ifx6x60.c
> +++ b/drivers/tty/serial/ifx6x60.c
> @@ -810,7 +810,8 @@ static void ifx_spi_io(unsigned long data)
> ifx_dev->spi_xfer.cs_change = 0;
> ifx_dev->spi_xfer.speed_hz = ifx_dev->spi_dev->max_speed_hz;
> /* ifx_dev->spi_xfer.speed_hz = 390625; */
> - ifx_dev->spi_xfer.bits_per_word = spi_bpw;
> + ifx_dev->spi_xfer.bits_per_word =
> + ifx_dev->spi_dev->bits_per_word;
Please follow the proper coding style (hint, this isn't it.)
thanks,
greg k-h
next prev parent reply other threads:[~2013-01-16 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 5:07 chao bi
2013-01-16 2:50 ` Greg KH
2013-01-16 4:57 ` Bi, Chao [this message]
2013-01-16 5:14 channing
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=253F3AA5ECB4EC43A2CA0147545F67F2102CE29F@SHSMSX102.ccr.corp.intel.com \
--to=chao.bi@intel.com \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jun.d.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=russ.gorby@intel.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
all inboxes | Powered by JetHome®