From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Qiang Yu <qiang.yu@oss.qualcomm.com>,
Manivannan Sadhasivam <mani@kernel.org>
Cc: mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mayank Rana <mayank.rana@oss.qualcomm.com>,
Baochen Qiang <quic_bqiang@quicinc.com>
Subject: Re: [PATCH v3] mhi: host: Add standard elf image download functionality
Date: Thu, 18 Dec 2025 10:31:16 -0800 [thread overview]
Message-ID: <590f6b8a-02a2-4ec7-ae43-27b267f0cbff@oss.qualcomm.com> (raw)
In-Reply-To: <20251201-wlan_image_load_skip_512k-v3-1-bedb5498a58a@oss.qualcomm.com>
On 12/1/2025 6:33 PM, Qiang Yu wrote:
> From: Mayank Rana <mayank.rana@oss.qualcomm.com>
>
> Currently, the FBC image is a non-standard ELF file that contains a single
> ELF header, followed by segments for SBL, and WLAN FW. However, TME-L
> (Trust Management Engine Lite) supported devices (eg. QCC2072) requires
> separate ELF headers for SBL and WLAN FW segments due to TME-L image
> authentication requirement.
>
> Current image format contains two sections in a single binary:
> - First 512KB: ELF header + SBL segments
> - Remaining: WLAN FW segments
>
> The TME-L supported image format contains two sections with two elf
> headers in a single binary:
> - First 512KB: First ELF header + SBL segments
> - Remaining: Second ELF header + WLAN FW segments
>
> Download behavior:
> - Legacy: 1. First 512KB via BHI (ELF header + SBL)
> 2. Full image via BHIe
>
> - TME-L: 1. First 512KB via BHI (First ELF header + SBL)
> 2. Remaining via BHIe (Second ELF header + WLAN FW segments)
>
> Add standard_elf_image flag to mhi_controller_config to indicate TME-L
> supported image format. When set, MHI skips the first 512KB during WLAN FW
> download over BHIe as it is loaded in BHI phase.
FYI the consumer of this functionality is now available:
series:
https://lore.kernel.org/all/20251218-ath12k-support-qcc2072-v1-0-87928cf8e547@oss.qualcomm.com
specific patch:
https://lore.kernel.org/all/20251218-ath12k-support-qcc2072-v1-11-87928cf8e547@oss.qualcomm.com/
prev parent reply other threads:[~2025-12-18 18:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 2:33 Qiang Yu
2025-12-06 11:25 ` Dmitry Baryshkov
2025-12-08 6:35 ` Qiang Yu
2025-12-09 22:57 ` Dmitry Baryshkov
2025-12-11 9:37 ` Qiang Yu
2025-12-11 13:57 ` Dmitry Baryshkov
2025-12-12 1:07 ` Manivannan Sadhasivam
2025-12-12 19:24 ` Dmitry Baryshkov
2025-12-13 2:21 ` Manivannan Sadhasivam
2025-12-15 7:09 ` Qiang Yu
2025-12-15 18:41 ` Dmitry Baryshkov
2025-12-16 8:26 ` Qiang Yu
2025-12-18 1:12 ` Dmitry Baryshkov
2025-12-18 7:41 ` Qiang Yu
2025-12-18 4:55 ` Manivannan Sadhasivam
2025-12-18 8:04 ` Qiang Yu
2025-12-18 9:13 ` Baochen Qiang
2025-12-18 9:21 ` Baochen Qiang
2025-12-18 11:21 ` Manivannan Sadhasivam
2025-12-18 12:36 ` Qiang Yu
2025-12-18 12:42 ` Manivannan Sadhasivam
2025-12-18 13:18 ` Bjorn Andersson
2025-12-19 4:07 ` Qiang Yu
2025-12-22 10:24 ` Qiang Yu
2025-12-15 18:21 ` Jeff Johnson
2025-12-16 6:11 ` Qiang Yu
2025-12-18 18:31 ` Jeff Johnson [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=590f6b8a-02a2-4ec7-ae43-27b267f0cbff@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mayank.rana@oss.qualcomm.com \
--cc=mhi@lists.linux.dev \
--cc=qiang.yu@oss.qualcomm.com \
--cc=quic_bqiang@quicinc.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
all inboxes | Powered by JetHome®