Netdev List
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: han.junyang@zte.com.cn
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	ran.ming@zte.com.cn, han.chengfei@zte.com.cn,
	zhang.yanze@zte.com.cn
Subject: Re: [PATCH net-next v1 1/3] dinghai: add firmware version check and? RISC-V readiness polling
Date: Mon, 24 Aug 2026 19:59:38 +0200	[thread overview]
Message-ID: <aa56dcc9-0637-493e-8cbd-cb8f0426c811@lunn.ch> (raw)
In-Reply-To: <20260824033538020rXU4GiMrh05w37DWs5k7v@zte.com.cn>

> +	struct zxdh_fw_compat *fw_compat;

> +	/* Firmware predating the compatibility region keeps the erased
> +	 * pattern, which fails the module id check below and defers the
> +	 * decision to the readiness wait.
> +	 */
> +	ioread32_rep(compat_base, fw_compat, sizeof(*fw_compat) / 4);

> +/* Firmware version compatibility block at ZXDH_FW_COMPAT_OFFSET.
> + * Copied out with ioread32_rep(), which converts from little-endian.
> + */
> +struct zxdh_fw_compat {
> +	u8 module_id;
> +	u8 major;
> +	s8 fw_minor;
> +	u8 drv_minor;
> +	u16 patch;
> +	u16 rsv;

What are the endinness of these two u16? Should they be marked as
little endian?

> +} __packed;
> +
> +/* Health buffer at ZXDH_RISCV_HB_OFFSET, maintained by the RISC-V
> + * management core of the firmware. Fields are read through ioread*().
> + */
> +struct zxdh_health_buffer {
> +	u32 synd;		/* Bitmask of active syndrome flags. */
> +	u32 health_counter;	/* Incremented heartbeat counter. */

Same question here.

     Andrew

  parent reply	other threads:[~2026-08-24 17:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23 19:32 [PATCH net-next v1 0/3] dinghai: firmware handshake, MSI-X interrupts and async event queue han.junyang
2026-08-23 19:35 ` [PATCH net-next v1 1/3] dinghai: add firmware version check and RISC-V readiness polling han.junyang
2026-08-23 21:55   ` [PATCH net-next v1 1/3] dinghai: add firmware version check and? " Andrew Lunn
2026-08-24 17:59   ` Andrew Lunn [this message]
2026-08-23 19:37 ` [PATCH net-next v1 2/3] dinghai: add MSI-X interrupt pools han.junyang
2026-08-24 23:55   ` Andrew Lunn
2026-08-23 19:40 ` [PATCH net-next v1 3/3] dinghai: add async event queue for firmware notifications han.junyang
2026-08-24 17:00 ` [PATCH net-next v1 0/3] dinghai: firmware handshake, MSI-X interrupts and async event queue Jakub Kicinski

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=aa56dcc9-0637-493e-8cbd-cb8f0426c811@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=han.chengfei@zte.com.cn \
    --cc=han.junyang@zte.com.cn \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ran.ming@zte.com.cn \
    --cc=zhang.yanze@zte.com.cn \
    /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