From: Siarhei Volkau <lis8215@gmail.com>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH v2 2/2] dmaengine: JZ4780: Add support for the JZ4755.
Date: Mon, 17 Oct 2022 20:29:27 +0300 [thread overview]
Message-ID: <CAKNVLfY87P6jTG8g5L_S84MUXCfL1Z0GLgAdZqD4K6h6ubJb-Q@mail.gmail.com> (raw)
In-Reply-To: <895WJR.03DS0G5N9R0V1@crapouillou.net>
пн, 17 окт. 2022 г. в 12:34, Paul Cercueil <paul@crapouillou.net>:
> Can you verify that?
>
> It should be pretty simple, if it has the bug you'll see I/O errors on
> the SD card.
Well, the result is ambiguous:
Without that 'broken' flag: mmc works poorly, but becomes more or less
stable when MMC clock downs to 6MHz (90% boots without errors).
On the 12MHz MMC clock the issue doesn't appear in 50-70% cases.
On the 24MHz MMC clock the device never boots up.
However with the flag: MMC works stable on 24MHz MMC clock
(boot issue observed only once), but if I increase MMC clock speed even
a bit the problem appears oftenly ( >70% of cases).
So, that flag definitely helps a lot, but the nature of the problem might be
different.
BR,
Siarhei
next prev parent reply other threads:[~2022-10-17 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 15:12 [PATCH v2 0/2] Add Ingenic JZ4755 DMA support Siarhei Volkau
2022-10-16 15:12 ` [PATCH v2 1/2] dt-bindings: ingenic: Add support for the JZ4755 dmaengine Siarhei Volkau
2022-10-16 15:31 ` Krzysztof Kozlowski
2022-10-16 15:12 ` [PATCH v2 2/2] dmaengine: JZ4780: Add support for the JZ4755 Siarhei Volkau
2022-10-17 9:34 ` Paul Cercueil
2022-10-17 17:29 ` Siarhei Volkau [this message]
2022-10-18 13:16 ` Paul Cercueil
2022-10-18 13:19 ` Paul Cercueil
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=CAKNVLfY87P6jTG8g5L_S84MUXCfL1Z0GLgAdZqD4K6h6ubJb-Q@mail.gmail.com \
--to=lis8215@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=robh+dt@kernel.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).