mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: Fabio Estevam <festevam@gmail.com>, Ralf Schlatterbeck <rsc@runtux.com>
Cc: Mark Brown <broonie@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	NXP Linux Team <linux-imx@nxp.com>,
	linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2 1/1] spi-mxs: Fix chipselect glitch
Date: Wed, 4 Dec 2024 14:27:24 +0100	[thread overview]
Message-ID: <5ab9b62a-6577-4a3f-9dfe-c7362bf725db@gmx.net> (raw)
In-Reply-To: <CAOMZO5CD7+E_BBH+oQ8HUdBeRFZxWW7s2uJgS5eaQAW_Fe4CNg@mail.gmail.com>

Hi,

Am 13.02.24 um 18:22 schrieb Fabio Estevam:
> Hi Ralf,
>
> On Tue, Feb 13, 2024 at 2:07 PM Ralf Schlatterbeck <rsc@runtux.com> wrote:
>> On Fri, Feb 02, 2024 at 12:53:30PM +0100, Ralf Schlatterbeck wrote:
>>> There was a change in the mxs-dma engine that uses a new custom flag.
>>> The change was not applied to the mxs spi driver.
>>> This results in chipselect being deasserted too early.
>>> This fixes the chipselect problem by using the new flag in the mxs-spi
>>> driver.
>>>
>>> Fixes: ceeeb99cd821 ("dmaengine: mxs: rename custom flag")
>>> Signed-off-by: Ralf Schlatterbeck <rsc@runtux.com>
>>> ---
>>> For oscilloscope screenshots and a verbose explanation see my blog post
>>> at https://blog.runtux.com/posts/2024/02/01/
> I suggest putting the link to your detailed explanation into the
> commit log as this is useful information.
>
> Reviewed-by: Fabio Estevam <festevam@gmail.com>
I noticed that this patch hasn't applied to stable yet.

Are there reason for not doing this or is it just because the patch
missed the Cc: stable@vger.kernel.org ?

  parent reply	other threads:[~2024-12-04 13:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 11:53 Ralf Schlatterbeck
2024-02-13 17:06 ` Ralf Schlatterbeck
2024-02-13 17:22   ` Fabio Estevam
2024-02-13 20:02     ` Ralf Schlatterbeck
2024-02-13 20:04       ` Fabio Estevam
2024-12-04 13:27     ` Stefan Wahren [this message]
2024-02-13 17:49   ` Mark Brown
2024-02-13 18:44 ` Mark Brown
2024-02-13 20:02   ` Ralf Schlatterbeck

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=5ab9b62a-6577-4a3f-9dfe-c7362bf725db@gmx.net \
    --to=wahrenst@gmx.net \
    --cc=broonie@kernel.org \
    --cc=festevam@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=rsc@runtux.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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®