public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Viken Dadhaniya <quic_vdadhani@quicinc.com>,
	Bjorn Andersson <andersson@kernel.org>
Cc: andi.shyti@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, gregkh@linuxfoundation.org,
	jirislaby@kernel.org, broonie@kernel.or, konradybcio@kernel.org,
	johan+linaro@kernel.org, dianders@chromium.org,
	agross@kernel.org, linux-arm-msm@vger.kernel.org,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	linux-spi@vger.kernel.org, quic_msavaliy@quicinc.com,
	quic_anupkulk@quicinc.com
Subject: Re: [PATCH v3 6/9] soc: qcom: geni-se: Add support to load QUP SE Firmware via Linux subsystem
Date: Sat, 3 May 2025 13:17:24 +0200	[thread overview]
Message-ID: <c55d718f-00fa-442a-b67b-9a678556a2a7@oss.qualcomm.com> (raw)
In-Reply-To: <e0916f4b-d2be-46a7-889f-2eebd12b74d0@quicinc.com>

On 5/3/25 1:11 PM, Viken Dadhaniya wrote:
> 
> 
> On 3/6/2025 4:57 AM, Bjorn Andersson wrote:
>> On Mon, Mar 03, 2025 at 06:13:46PM +0530, Viken Dadhaniya wrote:
>>> Load the firmware to QUP SE based on the 'firmware-name' property specified

[...]

>>> +    u32 magic;
>>
>> What endian is that u32? Please be specific.
> 
> I didn't understand your comment. Could you please help me understand what is required here?

External data can be of different endianness than the running OS.
This should either be __le32 or __be32.

Konrad

  reply	other threads:[~2025-05-03 11:17 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 12:43 [PATCH v3 0/9] Add support to load QUP SE firmware from Viken Dadhaniya
2025-03-03 12:43 ` [PATCH v3 1/9] dt-bindings: qcom: geni-se: Add 'firmware-name' property for firmware loading Viken Dadhaniya
2025-03-04  8:08   ` Krzysztof Kozlowski
2025-03-03 12:43 ` [PATCH v3 2/9] dt-bindings: qcom: se-common: Add QUP Peripheral-specific properties for I2C, SPI, and SERIAL bus Viken Dadhaniya
2025-03-04  8:10   ` Krzysztof Kozlowski
2025-03-04  8:22     ` Krzysztof Kozlowski
2025-03-03 12:43 ` [PATCH v3 3/9] dt-bindings: i2c: qcom,i2c-geni: document qcom,gsi-dma-allowed Viken Dadhaniya
2025-03-04  8:12   ` Krzysztof Kozlowski
2025-03-03 12:43 ` [PATCH v3 4/9] spi: dt-bindings: " Viken Dadhaniya
2025-03-04  8:13   ` Krzysztof Kozlowski
2025-03-03 12:43 ` [PATCH v3 5/9] dt-bindings: serial: " Viken Dadhaniya
2025-03-04  8:13   ` Krzysztof Kozlowski
2025-03-03 12:43 ` [PATCH v3 6/9] soc: qcom: geni-se: Add support to load QUP SE Firmware via Linux subsystem Viken Dadhaniya
2025-03-04  3:46   ` kernel test robot
2025-03-05 17:13   ` kernel test robot
2025-03-05 18:16   ` kernel test robot
2025-03-05 23:27   ` Bjorn Andersson
2025-04-22  6:32     ` Viken Dadhaniya
2025-06-11 11:44       ` Viken Dadhaniya
2025-05-03 11:11     ` Viken Dadhaniya
2025-05-03 11:17       ` Konrad Dybcio [this message]
2025-03-08 18:06   ` Konrad Dybcio
2025-05-03 11:17     ` Viken Dadhaniya
2025-05-03 17:21       ` Dmitry Baryshkov
2025-05-06  9:17         ` Viken Dadhaniya
2025-03-03 12:43 ` [PATCH v3 7/9] i2c: qcom-geni: Load i2c qup Firmware from linux side Viken Dadhaniya
2025-03-03 12:43 ` [PATCH v3 8/9] spi: geni-qcom: Load spi " Viken Dadhaniya
2025-03-03 12:43 ` [PATCH v3 9/9] serial: qcom-geni: Load UART " Viken Dadhaniya
2025-03-04  8:11 ` [PATCH v3 0/9] Add support to load QUP SE firmware from Krzysztof Kozlowski
2025-03-04  8:12   ` Krzysztof Kozlowski

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=c55d718f-00fa-442a-b67b-9a678556a2a7@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=broonie@kernel.or \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=johan+linaro@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=quic_anupkulk@quicinc.com \
    --cc=quic_msavaliy@quicinc.com \
    --cc=quic_vdadhani@quicinc.com \
    --cc=robh@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