From: "MOHAMAD JAMIAN, MUHAMMAD AMIRUL ASYRAF" <muhammad.amirul.asyraf.mohamad.jamian@altera.com>
To: Dinh Nguyen <dinguyen@kernel.org>
Cc: "Rao, Mahesh" <mahesh.rao@altera.com>,
Matthew Gerlach <matthew.gerlach@altera.com>,
Anders Hedlund <anders.hedlund@windriver.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 0/2] firmware: stratix10-svc: Fix probe failure with old ATF
Date: Fri, 8 May 2026 09:32:53 +0000 [thread overview]
Message-ID: <625db1c1-e8d2-4e62-ab65-43eed05af454@altera.com> (raw)
In-Reply-To: <15ea8185-49ac-4a43-aecf-b650e54a2a9c@kernel.org>
On 5/5/2026 8:14 pm, Dinh Nguyen wrote:
>
>
> On 4/16/26 02:22, Muhammad Amirul Asyraf Mohamad Jamian wrote:
>> Since commit bcb9f4f07061 ("firmware: stratix10-svc: Add support for
>> async communication"), the SVC driver fails to probe entirely when
>> running with ATF versions older than 3.0 (e.g. ATF 2.5) that do not
>> support SIP SVC v3 asynchronous operations.
>>
>> stratix10_svc_async_init() returns -EINVAL for old ATF, and the probe
>> function treats any non-zero return as fatal, causing:
>>
>> stratix10-svc firmware:svc: probe with driver stratix10-svc failed \
>> with error -22
>>
>> This prevents all dependent client drivers (hwmon, RSU, FCS) from
>> probing even though they can operate correctly via the synchronous V1
>> SMC path.
>>
>> This series fixes the issue in two steps:
>> 1. Return -EOPNOTSUPP (instead of -EINVAL) when ATF async is
>> unsupported, so callers can distinguish "not supported" from
>> "bad argument / programming error".
>> 2. Treat -EOPNOTSUPP as non-fatal in probe, allowing the SVC driver
>> to load in sync-only mode so all client drivers can probe normally.
>>
>> Both patches fix bcb9f4f07061 and are tagged for stable.
>>
>>
> I think it makes more sense to squash these 2 patches together. Patch 1
> adds the -EOPNOTSUPP, but does not make use of it. Patch 2 actually
> makes use of the -EOPNOTSUPP. So I was a bit confused on how the change
> is getting used.
>
> Dinh
Addressed in v2
https://lore.kernel.org/all/20260508092936.18380-1-muhammad.amirul.asyraf.mohamad.jamian@altera.com/
Thanks,
Amirul
prev parent reply other threads:[~2026-05-08 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260416072207.27074-1-muhammad.amirul.asyraf.mohamad.jamian@altera.com>
2026-05-05 12:14 ` [PATCH 0/2] firmware: stratix10-svc: Fix probe failure with old ATF Dinh Nguyen
2026-05-08 9:32 ` MOHAMAD JAMIAN, MUHAMMAD AMIRUL ASYRAF [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=625db1c1-e8d2-4e62-ab65-43eed05af454@altera.com \
--to=muhammad.amirul.asyraf.mohamad.jamian@altera.com \
--cc=anders.hedlund@windriver.com \
--cc=dinguyen@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahesh.rao@altera.com \
--cc=matthew.gerlach@altera.com \
--cc=stable@vger.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