From: Niklas Cassel <cassel@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-ide@vger.kernel.org, Damien Le Moal <dlemoal@kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ata: pata_ep93xx: fix PIO fallback when DMA init fails
Date: Tue, 2 Jun 2026 14:05:08 +0200 [thread overview]
Message-ID: <ah7G9AbYy1M66u0s@ryzen> (raw)
In-Reply-To: <20260601190749.20045-1-rosenp@gmail.com>
On Mon, Jun 01, 2026 at 12:07:49PM -0700, Rosen Penev wrote:
> ep93xx_pata_dma_init() returns an error when dma_request_chan() fails,
> which causes ep93xx_pata_probe() to abort entirely. The probe function
> already has a PIO fallback path (it checks both channel pointers before
> enabling UDMA), so the DMA init should not fail the probe on non-fatal
> errors.
>
> Treat only -EPROBE_DEFER as a fatal error. For all other failures
> (ENODEV, ENXIO, configuration errors), release any allocated channels,
> NULL the pointers, warn, and return 0 so the driver continues in PIO mode.
This patch looks correct to me, but I do think that the commit message,
which refers to -EPROBE_DEFER as a fatal error, is very misleading.
Better phrasing would be something like:
Propagate -EPROBE_DEFER, such that we allow the DMA controller driver
to load, in case we got probed before the DMA controller driver.
For all other failures (e.g. -ENODEV when the DMA controller is missing
in the device tree), fall back to PIO.
Kind regards,
Niklas
prev parent reply other threads:[~2026-06-02 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 19:07 [PATCH] ata: pata_ep93xx: fix PIO fallback when DMA init fails Rosen Penev
2026-06-02 12:05 ` Niklas Cassel [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=ah7G9AbYy1M66u0s@ryzen \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rosenp@gmail.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