Linux on Apple ARM platform development
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: Janne Grunau <j@jannau.net>
Cc: u-boot@lists.u-boot-project.org, asahi@lists.linux.dev,
	kettenis@openbsd.org, sven@kernel.org, neil.armstrong@linaro.org,
	bmeng.cn@gmail.com, trini@konsulko.com, fberder@outlook.fr,
	j@jannau.net
Subject: Re: [PATCH 2/4] nvme: apple: Never set the opcode in the NVMMU TCB
Date: Mon, 07 Sep 2026 23:21:55 +0200	[thread overview]
Message-ID: <87se3ksqoc.fsf@bloch.sibelius.xs4all.nl> (raw)
In-Reply-To: <20260904-apple-nvme-fwabi-v1-2-f7ede661c469@jannau.net> (message from Janne Grunau on Fri, 04 Sep 2026 21:22:40 +0200)

> From: Janne Grunau <j@jannau.net>
> Date: Fri, 04 Sep 2026 21:22:40 +0200
> 
> macOS always sets this to zero and the firmware starting with macOS 15
> has started to complain about what we're doing here.
> 
> Based on Linux kernel commit cc0fec9b42cf ("nvme-apple: Never set the
> opcode in the NVMMU TCB").

Reviewed-by: Mark Kettenis <kettenis@openbsd.org>

> Link: https://lore.kernel.org/asahi/20260806-b4-nvme-fwabi-v1-3-bde19ce8db04@kernel.org/
> Fixes: 50333c94f2de ("nvme: apple: Add driver for Apple NVMe storage controller")
> Signed-off-by: Janne Grunau <j@jannau.net>
> ---
>  drivers/nvme/nvme_apple.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/nvme/nvme_apple.c b/drivers/nvme/nvme_apple.c
> index dc94988e2ff..f615f8fac4a 100644
> --- a/drivers/nvme/nvme_apple.c
> +++ b/drivers/nvme/nvme_apple.c
> @@ -121,7 +121,7 @@ static void apple_nvme_submit_cmd(struct nvme_queue *nvmeq,
>  
>  	tcb = ((void *)priv->tcbs[nvmeq->qid]) + tail * ANS_NVMMU_TCB_PITCH;
>  	memset(tcb, 0, sizeof(*tcb));
> -	tcb->opcode = cmd->common.opcode;
> +	tcb->opcode = 0;
>  	if (cmd->common.prp1)
>  		tcb->flags = ANS_NVMMU_TCB_WRITE | ANS_NVMMU_TCB_READ;
>  	else
> 
> -- 
> 2.55.0
> 
> 

  reply	other threads:[~2026-09-07 21:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 19:22 [PATCH 0/4] Apple NVMe fixes for macOS 15+ firmware / M4 support Janne Grunau
2026-09-04 19:22 ` [PATCH 1/4] nvme: apple: Don't set a DMA direction for commands without a data transfer Janne Grunau
2026-09-07 21:21   ` Mark Kettenis
2026-09-04 19:22 ` [PATCH 2/4] nvme: apple: Never set the opcode in the NVMMU TCB Janne Grunau
2026-09-07 21:21   ` Mark Kettenis [this message]
2026-09-04 19:22 ` [PATCH 3/4] nvme: apple: Add WARN_ON_ONCE for non page-aligned admin queue buffers Janne Grunau
2026-09-07 21:23   ` Mark Kettenis
2026-09-04 19:22 ` [PATCH 4/4] nvme: apple: Drop the PRP null check chicken bit Janne Grunau
2026-09-07 21:24   ` Mark Kettenis
2026-09-10 12:44 ` [PATCH 0/4] Apple NVMe fixes for macOS 15+ firmware / M4 support Neil Armstrong
2026-09-10 13:11   ` Mark Kettenis
2026-09-10 13:14 ` Neil Armstrong

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=87se3ksqoc.fsf@bloch.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=asahi@lists.linux.dev \
    --cc=bmeng.cn@gmail.com \
    --cc=fberder@outlook.fr \
    --cc=j@jannau.net \
    --cc=kettenis@openbsd.org \
    --cc=neil.armstrong@linaro.org \
    --cc=sven@kernel.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.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