From: Jan Kiszka <jan.kiszka@web.de>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Mark Brown <broonie@kernel.org>,
linux-spi <linux-spi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] spi: pxa2xx: Only claim CS GPIOs when the slave device is created
Date: Mon, 24 Jul 2017 12:53:20 +0200 [thread overview]
Message-ID: <59066818-a284-4da0-d05f-d2503aeee44b@web.de> (raw)
In-Reply-To: <CAHp75VfpJzOdhMyZoMGnC4CQc5kGxq1k-__dpmVAOaxaD04w6Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1185 bytes --]
On 2017-07-24 12:44, Andy Shevchenko wrote:
> +Cc: Mika
>
> On Sat, Jul 8, 2017 at 11:41 AM, Jan Kiszka <jan.kiszka@web.de> wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> Avoid hogging chip select GPIOs just because they are listed for the
>> master. They might be mulitplexed and, if no slave device is attached,
>> used for different purposes. Moreover, this strategy avoids having to
>> allocate a cs_gpiods structure.
>>
>> Tested on the IOT2000 where the second SPI bus is connected to an
>> Arduino-compatible connector and multiplexed between SPI, GPIO and PWM
>> usage.
>>
>
> This breaks all systems which are using _DSD.
Err, can you elaborate? Worked fine here with _DSD on the IOT2000.
>
> While I'm looking for fix, I get feeling that the approach itself is not right,
>
> So, for now I would vote for immediate revert and then rethink what we
> can do here.
I'm fine with reverting because the patch wasn't clean anyway (mixed old
and new GPIO API) - aside from whatever you found in addition. I had an
update pending but, as you are looking into this anyway, I'm sure your
patches will be more holistic.
Thanks,
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-07-24 10:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 8:41 Jan Kiszka
2017-07-08 21:48 ` Andy Shevchenko
2017-07-09 9:30 ` Jan Kiszka
2017-07-09 9:55 ` Andy Shevchenko
2017-07-09 10:30 ` Jan Kiszka
2017-07-10 12:09 ` Mark Brown
2017-07-10 17:31 ` Jan Kiszka
2017-07-17 16:07 ` Applied "spi: pxa2xx: Only claim CS GPIOs when the slave device is created" to the spi tree Mark Brown
2017-07-22 22:07 ` [PATCH] spi: pxa2xx: Only claim CS GPIOs when the slave device is created Andy Shevchenko
2017-07-24 10:44 ` Andy Shevchenko
2017-07-24 10:53 ` Jan Kiszka [this message]
2017-07-24 11:02 ` Andy Shevchenko
2017-07-24 11:06 ` Jan Kiszka
2017-07-24 11:14 ` Andy Shevchenko
2017-07-24 13:03 ` Andy Shevchenko
2017-07-24 13:14 ` Mika Westerberg
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=59066818-a284-4da0-d05f-d2503aeee44b@web.de \
--to=jan.kiszka@web.de \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
/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®