From: Nicolas Boichat <drinkcat@chromium.org>
To: Mark Brown <broonie@kernel.org>
Cc: Kukjin Kim <kgene@kernel.org>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: [PATCH 2/3] spi: ppc44x: Remove chipselect from setupxfer
Date: Tue, 4 Aug 2015 14:09:57 +0800 [thread overview]
Message-ID: <1438668598-6678-2-git-send-email-drinkcat@chromium.org> (raw)
In-Reply-To: <1438668598-6678-1-git-send-email-drinkcat@chromium.org>
The chipselect operation is already done in spi_bitbang_transfer_one,
or in spi_bitbang_setup, so there is no need to do it in setupxfer
as well.
Signed-off-by: Nicolas Boichat <drinkcat@chromium.org>
---
drivers/spi/spi-ppc4xx.c | 7 -------
1 file changed, 7 deletions(-)
diff --git a/drivers/spi/spi-ppc4xx.c b/drivers/spi/spi-ppc4xx.c
index 54fb984..55947f6 100644
--- a/drivers/spi/spi-ppc4xx.c
+++ b/drivers/spi/spi-ppc4xx.c
@@ -210,13 +210,6 @@ static int spi_ppc4xx_setupxfer(struct spi_device *spi, struct spi_transfer *t)
if (in_8(&hw->regs->cdm) != cdm)
out_8(&hw->regs->cdm, cdm);
- spin_lock(&hw->bitbang.lock);
- if (!hw->bitbang.busy) {
- hw->bitbang.chipselect(spi, BITBANG_CS_INACTIVE);
- /* Need to ndelay here? */
- }
- spin_unlock(&hw->bitbang.lock);
-
return 0;
}
--
2.5.0.rc2.392.g76e840b
next prev parent reply other threads:[~2015-08-04 6:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 6:09 [PATCH 1/3] spi: bitbang: Replace spinlock by mutex when calling chipselect Nicolas Boichat
2015-08-04 6:09 ` Nicolas Boichat [this message]
2015-08-04 6:09 ` [PATCH 3/3] spi: s3c24xx: Convert spinlock to mutex Nicolas Boichat
2015-08-04 11:00 ` Mark Brown
2015-08-04 10:59 ` [PATCH 1/3] spi: bitbang: Replace spinlock by mutex when calling chipselect Mark Brown
2015-08-05 10:24 ` Nicolas Boichat
2015-08-14 19:19 ` Mark Brown
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=1438668598-6678-2-git-send-email-drinkcat@chromium.org \
--to=drinkcat@chromium.org \
--cc=broonie@kernel.org \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.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
all inboxes | Powered by JetHome®