From: Mark Brown <broonie@kernel.org>
To: ryan.wanner@microchip.com, Louis Chauvet <louis.chauvet@bootlin.com>
Cc: thomas.petazzoni@bootlin.com, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, claudiu.beznea@tuxon.dev,
haavard.skinnemoen@atmel.com, akpm@linux-foundation.org,
dbrownell@users.sourceforge.net, linux-spi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH] spi: atmel: Fix clock issue when using devices with different polarities
Date: Thu, 14 Dec 2023 13:37:30 +0000 [thread overview]
Message-ID: <170256105093.58838.9858114740206767634.b4-ty@kernel.org> (raw)
In-Reply-To: <20231204154903.11607-1-louis.chauvet@bootlin.com>
On Mon, 04 Dec 2023 16:49:03 +0100, Louis Chauvet wrote:
> The current Atmel SPI controller driver (v2) behaves incorrectly when
> using two SPI devices with different clock polarities and GPIO CS.
>
> When switching from one device to another, the controller driver first
> enables the CS and then applies whatever configuration suits the targeted
> device (typically, the polarities). The side effect of such order is the
> apparition of a spurious clock edge after enabling the CS when the clock
> polarity needs to be inverted wrt. the previous configuration of the
> controller.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: atmel: Fix clock issue when using devices with different polarities
commit: fc70d643a2f6678cbe0f5c86433c1aeb4d613fcc
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: ryan.wanner@microchip.com, Louis Chauvet <louis.chauvet@bootlin.com>
Cc: alexandre.belloni@bootlin.com, dbrownell@users.sourceforge.net,
stable@vger.kernel.org, claudiu.beznea@tuxon.dev,
haavard.skinnemoen@atmel.com, thomas.petazzoni@bootlin.com,
akpm@linux-foundation.org, linux-spi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] spi: atmel: Fix clock issue when using devices with different polarities
Date: Thu, 14 Dec 2023 13:37:30 +0000 [thread overview]
Message-ID: <170256105093.58838.9858114740206767634.b4-ty@kernel.org> (raw)
In-Reply-To: <20231204154903.11607-1-louis.chauvet@bootlin.com>
On Mon, 04 Dec 2023 16:49:03 +0100, Louis Chauvet wrote:
> The current Atmel SPI controller driver (v2) behaves incorrectly when
> using two SPI devices with different clock polarities and GPIO CS.
>
> When switching from one device to another, the controller driver first
> enables the CS and then applies whatever configuration suits the targeted
> device (typically, the polarities). The side effect of such order is the
> apparition of a spurious clock edge after enabling the CS when the clock
> polarity needs to be inverted wrt. the previous configuration of the
> controller.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: atmel: Fix clock issue when using devices with different polarities
commit: fc70d643a2f6678cbe0f5c86433c1aeb4d613fcc
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-12-14 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 15:49 [PATCH] spi: atmel: Fix clock issue when using devices with different polarities Louis Chauvet
2023-12-04 15:49 ` Louis Chauvet
2023-12-14 13:37 ` Mark Brown [this message]
2023-12-14 13:37 ` 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=170256105093.58838.9858114740206767634.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=dbrownell@users.sourceforge.net \
--cc=haavard.skinnemoen@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=louis.chauvet@bootlin.com \
--cc=nicolas.ferre@microchip.com \
--cc=ryan.wanner@microchip.com \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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 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.