From: Tomoya MORINAGA <tomoya-linux@dsn.lapis-semi.com>
To: Toshiharu Okada <toshiharu-linux@dsn.okisemi.com>
Cc: grant.likely@secretlab.ca,
spi-devel-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org, qi.wang@intel.com,
yong.y.wang@intel.com, joel.clark@intel.com,
kok.howg.ewe@intel.com, tomoya-linux@dsn.okisemi.com
Subject: Re: [PATCH] spi_topcliff_pch: supports a spi mode setup and bit order setup by IO control
Date: Thu, 06 Oct 2011 14:24:45 +0900 [thread overview]
Message-ID: <4E8D3B9D.6030208@dsn.lapis-semi.com> (raw)
In-Reply-To: <1311141414-12867-1-git-send-email-toshiharu-linux@dsn.okisemi.com>
Hi Grant,
It seems this patch Toshiharu posted in 20-July remains not to be
reviewed by you.
Could you review this patch and merge to your tree ?
Thanks in advance,
--
tomoya
ROHM Co., Ltd.
(2011/07/20 14:56), Toshiharu Okada wrote:
> This patch supports a spi mode setup and bit order setup by IO control.
> spi mode: mode 0 to mode 3
> bit order: LSB first, MSB first
>
> Signed-off-by: Toshiharu Okada<toshiharu-linux@dsn.okisemi.com>
> ---
> drivers/spi/spi_topcliff_pch.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/spi/spi_topcliff_pch.c b/drivers/spi/spi_topcliff_pch.c
> index 79e48d4..dec83c9 100644
> --- a/drivers/spi/spi_topcliff_pch.c
> +++ b/drivers/spi/spi_topcliff_pch.c
> @@ -1038,6 +1038,7 @@ static int pch_spi_probe(struct pci_dev *pdev, const struct pci_device_id *id)
> master->num_chipselect = PCH_MAX_CS;
> master->setup = pch_spi_setup;
> master->transfer = pch_spi_transfer;
> + master->mode_bits = SPI_CPOL | SPI_CPHA | SPI_LSB_FIRST;
> dev_dbg(&pdev->dev,
> "%s transfer member of SPI master initialized\n", __func__);
>
prev parent reply other threads:[~2011-10-06 5:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 5:56 Toshiharu Okada
2011-08-04 0:20 ` Toshiharu Okada
2011-10-06 5:24 ` Tomoya MORINAGA [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=4E8D3B9D.6030208@dsn.lapis-semi.com \
--to=tomoya-linux@dsn.lapis-semi.com \
--cc=grant.likely@secretlab.ca \
--cc=joel.clark@intel.com \
--cc=kok.howg.ewe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qi.wang@intel.com \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=tomoya-linux@dsn.okisemi.com \
--cc=toshiharu-linux@dsn.okisemi.com \
--cc=yong.y.wang@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®