From: Mark Brown <broonie@kernel.org>
To: Vaishnav Achath <vaishnav.a@ti.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
vigneshr@ti.com, u-kumar1@ti.com
Subject: Re: [PATCH] spi: omap2-mcspi: Revert FIFO support without DMA
Date: Mon, 12 Feb 2024 15:33:20 +0000 [thread overview]
Message-ID: <170775200080.46149.6260047434970051936.b4-ty@kernel.org> (raw)
In-Reply-To: <20240212120049.438495-1-vaishnav.a@ti.com>
On Mon, 12 Feb 2024 17:30:49 +0530, Vaishnav Achath wrote:
> MCSPI controller have few limitations regarding the transaction
> size when the FIFO buffer is enabled and the WCNT feature is used
> to find the end of word, in this case if WCNT is not a multiple of
> the FIFO Almost Empty Level (AEL), then the FIFO empty event is not
> generated correctly. In addition to this limitation, few other unknown
> sequence of events that causes the FIFO empty status to not reflect the
> exact status were found when FIFO is being used without DMA enabled
> during extended testing in AM65x platform. Till the exact root cause
> is found and fixed, revert the FIFO support without DMA.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: omap2-mcspi: Revert FIFO support without DMA
commit: e56c671c2272d939d48a66be7e73b92b74c560c2
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
prev parent reply other threads:[~2024-02-12 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 12:00 Vaishnav Achath
2024-02-12 12:59 ` Mark Brown
2024-02-12 15:33 ` Mark Brown [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=170775200080.46149.6260047434970051936.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=u-kumar1@ti.com \
--cc=vaishnav.a@ti.com \
--cc=vigneshr@ti.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®