From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Mikhail Kshevetskiy <mikhail.kshevetskiy@iopsys.eu>
Cc: Lorenzo Bianconi <lorenzo@kernel.org>,
Ray Liu <ray.liu@airoha.com>, Mark Brown <broonie@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Andy Shevchenko <andy@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org,
Andreas Gnau <andreas.gnau@iopsys.eu>
Subject: Re: [PATCH v5 1/3] spi: airoha-snfi: en7523: workaround flash damaging if UART_TXD was short to GND
Date: Tue, 25 Nov 2025 22:24:33 +0200 [thread overview]
Message-ID: <aSYQgZR1YoVQkbxC@smile.fi.intel.com> (raw)
In-Reply-To: <20251125191635.1075027-2-mikhail.kshevetskiy@iopsys.eu>
On Tue, Nov 25, 2025 at 10:16:33PM +0300, Mikhail Kshevetskiy wrote:
...
> + dev_warn(dev, "Detected booting in RESERVED mode (UART_TXD was short to GND).\n");
> + dev_warn(dev, "This mode is known for incorrect DMA reading of some flashes.\n");
> + dev_warn(dev, "Usage of DMA for flash operations will be disabled to prevent data\n");
> + dev_warn(dev, "damage. Unplug your serial console and power cycle the board\n");
> + dev_warn(dev, "to boot with full performance.\n");
One non-critical remark (for the future), the '\n' in the string literals when
we print messages has two meanings:
- (obviously) new line
- (seems not so obvious for people) flush the line to the output device
Due to the second property the messages might be interleaved with the other
messages (assuming SMP machine actively doing and printing something), hence
your messages might be split with other and imagine the user who gets in the
middle of the text something like
"Usage of DMA for flash operations will be disabled to prevent data"
The first thought will be "what the heck does this mean?"
TL;DR: place '\n' with a care in the messages to print not only here,
but in general.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-11-25 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 19:16 [PATCH v5 0/3] spi: airoha: add support of en7523 SoC (for 6.19) Mikhail Kshevetskiy
2025-11-25 19:16 ` [PATCH v5 1/3] spi: airoha-snfi: en7523: workaround flash damaging if UART_TXD was short to GND Mikhail Kshevetskiy
2025-11-25 20:18 ` Andy Shevchenko
2025-11-25 20:24 ` Andy Shevchenko [this message]
2025-11-25 22:53 ` Mikhail Kshevetskiy
2025-11-25 19:16 ` [PATCH v5 2/3] dt-bindings: spi: airoha: add compatible for EN7523 Mikhail Kshevetskiy
2025-11-25 19:16 ` [PATCH v5 3/3] arm: dts: airoha: en7523: add SNAND node Mikhail Kshevetskiy
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=aSYQgZR1YoVQkbxC@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=andreas.gnau@iopsys.eu \
--cc=andy@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=mikhail.kshevetskiy@iopsys.eu \
--cc=ray.liu@airoha.com \
--cc=robh@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