From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx0b-0031df01.pphosted.com (mx0b-0031df01.pphosted.com [205.220.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CF40534214F for ; Mon, 5 Jan 2026 17:57:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=205.220.180.131 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767635838; cv=none; b=jbROg4Aq3kOAoMHbYwWmNRoKJFtBCNC1Q71/ZfT+qsP9qLFxAFpwixjbb9oKbJ43RW+hEcHUurc8aMK1Dz7YOU+OQPo0j+ar7fovtm76qCS4b1wda11qCDGix5aYpU+AGT+TM1eVBJTWU7ir3qwEepquYtFuNCyRKcaSepf+fos= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767635838; c=relaxed/simple; bh=pyEGqOvXdHfsPS8mT2RifqqvTmsMWYWxCpCvhaasfpA=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=qLTbVfsYFj8GZwNmOK3E9SbMULMDqgp71yIFlqOfR0W2P0/CqGzU1+tgBe0h2aFREBU44JXfCghEs9imezM1IQd+cohkdGtuLIetCzGO9U5aiO0Hr1hi7lYvs8uOfthn1zC+nELaBVhMAFasemAeZdny+COo5Fx5VawzCdo3mKc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com; spf=pass smtp.mailfrom=oss.qualcomm.com; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b=kBTYcP7G; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b=WJfjdw3M; arc=none smtp.client-ip=205.220.180.131 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b="kBTYcP7G"; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b="WJfjdw3M" Received: from pps.filterd (m0279871.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 605AXKYj091265 for ; Mon, 5 Jan 2026 17:57:13 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qualcomm.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to; s=qcppdkim1; bh= luFQohOzUtSfFErML01fuIAdonSt43+90znEjAeHo9g=; b=kBTYcP7GTT32LIEU jBm5osAqY0ijXTXPYf4V7qJnig8su9EKz6kSpKk2PesX+ZD1FBeCkablOidbsPHO w1KdIMiC3TfWpe6zwIbCTXdH0xcT/s0Jl255bjkd7wPl1pDazLuv0QwvqpvMc8tf C2hqMvvfkWbx1kwhkcanSzpcvZLX4D0kfM2yYIPPjhUpTKaCSd6Gw3kYkHx5xi8q C22fAqTOoV/55LT+S+ZhsuTlgHnfVa7XwNghcR0Ymxg4wh6dkqM/72Z92dOirAm9 VeNVqxxfH0ZNRiMlNT0vWIfmDbvKv+7YavPKAVAL0QVXlwgYLK8WZ24Zb95L69OG FWMs7g== Received: from mail-pg1-f198.google.com (mail-pg1-f198.google.com [209.85.215.198]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 4bg4v62d84-1 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Mon, 05 Jan 2026 17:57:13 +0000 (GMT) Received: by mail-pg1-f198.google.com with SMTP id 41be03b00d2f7-c1d27c65670so1149003a12.1 for ; Mon, 05 Jan 2026 09:57:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oss.qualcomm.com; s=google; t=1767635832; x=1768240632; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=luFQohOzUtSfFErML01fuIAdonSt43+90znEjAeHo9g=; b=WJfjdw3MFVbI9DtRp6FnfHX1Sq1dUnYRH0FHh16hqBpRBRCQNBfEoepPCsvn2gU7TX Jr/PM+X3CPWjTAE5wYfl4DSsicABNR9qov8vpov1rsi23SQV61dcANWYh41oIdY0LrdJ kdrvscQTrGVfK8A+/wLcZE88PMgu6IHVJz8Z0bS0YhOIY1wAS4FAVguWe9WsY0qG5qQ0 Abv1uy/5yEfqSgEFy86Du1pb5pexmWEdejyDzRNNyUQ+J5JtijvWCYaVgx31nRv2wJlw Od7xGQVrGS7gZUV/i06DBImD5qfQs+oqG5Ixw3hOE2VLyOkjc5ap7uECcYrC6TNabnOr rbqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1767635832; x=1768240632; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=luFQohOzUtSfFErML01fuIAdonSt43+90znEjAeHo9g=; b=irw5Av1CZzdZMxilWuIiVDs9xGCLBOIEssmurfamDk4UBK/GhImpltMUU354td8vro hsE4PMovLRkKbvOrBC3Ll6udVH2eC77pQjvQZy87MJke8TS+T60xpCqN3I/1kvoel3MN wTYj6M7q8RrEWLgpUgf2gE0ywlqVlsCD0Q+NfpOuTZd/NnT5yR/nVCoWhXl3cykS9It+ Bnk3sjffye4n4eSBFJ3cMsODWBtfrpQA6qlNS8vmAhGkvDzOaLvj4iswI0h/qES5buCM azoX48vKY4cgAjeFIWZVqGCqB1kDYExCo7bo7mBwi+bfpLY+ofp4QW5w5MFJsojk9lTV 6LOA== X-Forwarded-Encrypted: i=1; AJvYcCXkmI6PAm7ZE8POCSIaCkgEvk5jicshGcOPYJUS0X7HJT/Cm9ixAFPBncgt6VK2bVtF32bQweITy3sjNgI=@vger.kernel.org X-Gm-Message-State: AOJu0Yw14+P3+3ccJlRAgoTy/LAyvvnxmElVt1KDGMUk478yPwxurJxA Nv1HCpm6ebD9kpyChHDswQhuruoqXssFmkohcbf+Okf4fOZJaCcVv5fgg9YY4I98+vY6UQ1DHzc TDpylMuGkZRzCHRzZ0GyOVVFcHThR0oAIeldUUGcXvmWgKElagt2wIBOmnZh92uR7lkY= X-Gm-Gg: AY/fxX5/tin7SuOThtuSZtYmS8t/JrzKDwCcOY0UboRSXfHVLztEFsHoDSjeK1wezlt +LMb3Xhq72sf2hfaM1E/KvkIJfjm1jZZvTx1W/7O1e95R82s0TDYIwOj28OmgnsfqrJKSAo3Z+d X8vNTKibYloOKf25Kv0AT9kfAgPCqPOLbruPUHO3RcN+dazaKOvzgpopm148gLpTSYVWT8BfhPU J5d4iqITX232CQxcVK0rM25oD+MeDoSEEbMdM5ts+QiweB0DPClwtF/aWf4je7oYKbjd54gAUwY s5GGjecq2ZRgwjZ7P0LbwUmpMB1dOC9uMjB8ZKsTwdQQNsV65bU+Nsb0IRYLwHxR5bfjdTDfd93 ju+V2I5X1DkpR9g4gr9CaX0XpDbaewUuTK1tKlUlnD2quRl9gZw== X-Received: by 2002:a17:90b:5825:b0:34a:a16d:77c3 with SMTP id 98e67ed59e1d1-34f5f83ddc3mr14796a91.2.1767635831925; Mon, 05 Jan 2026 09:57:11 -0800 (PST) X-Google-Smtp-Source: AGHT+IElruqKiFOG7DhNDu5zJlxmkqXIl8agGfM9DEGHevp6QtmhWxaqcdqCqo8PIRXDBYKFtHOY+Q== X-Received: by 2002:a17:90b:5825:b0:34a:a16d:77c3 with SMTP id 98e67ed59e1d1-34f5f83ddc3mr14767a91.2.1767635831388; Mon, 05 Jan 2026 09:57:11 -0800 (PST) Received: from [192.168.0.107] ([183.82.31.185]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-34f5f7a557asm14022a91.3.2026.01.05.09.57.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 05 Jan 2026 09:57:11 -0800 (PST) Message-ID: <19b2dd07-ed70-4eaa-8395-6a62d52ec862@oss.qualcomm.com> Date: Mon, 5 Jan 2026 23:27:07 +0530 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 6/9] remoteproc: qcom_q6v5_wcss: support IPQ9574 To: mr.nuke.me@gmail.com, Konrad Dybcio , andersson@kernel.org, mathieu.poirier@linaro.org, linux-kernel@vger.kernel.org Cc: krzk+dt@kernel.org, Philipp Zabel , linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org References: <20251219043425.888585-1-mr.nuke.me@gmail.com> <20251219043425.888585-6-mr.nuke.me@gmail.com> <12223416.nUPlyArG6x@nukework.gtech> <55d70e0b-7a6b-4979-9ae9-4443e54ab584@oss.qualcomm.com> <7f6754a4-4a3b-4b6f-9220-a1790a9ba393@gmail.com> Content-Language: en-US From: Vignesh Viswanathan In-Reply-To: <7f6754a4-4a3b-4b6f-9220-a1790a9ba393@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwMTA1MDE1NiBTYWx0ZWRfX/8zxYVJHuESK PYDBH+Ui1vPkqVgl8oajoQ6bpZJ4MZqhKk7arKlnTwwtNA1ejegFdOFR0Ze24CujMBHY8+9nPzy gdIEF39CKalGXdEIHFWag00Nf6e91eZd8hwkLvRH/fLuV+MGLiVa0XC2tqXxgqpkvmPvieHtVG5 2mxcCEwzUPT+hCbFioTuxSi/gXT4l9oZPZ3ccRy0dIv4lK1g1DyOg8OYy3jpTq2wWaIccaNiHcZ GeSv0gjNoiwRk6LVw/E1Tl6Eahecbx2nu+ypgbZz/2NepN+HthN0k+FAxnUUGpOHh6S4W51IZPa 3PDVKjEHBtYfySUdr6jSO+gK8imwDfdSIGxmrcRVBAxapga9jxTHK4S00lm5zgdDH8TM9rEMsEz GlhQTrvX6ol23LBES0Ajye4/ImjlO9fHyyNHgl8PZGF3BCrRIPT4q9joqxKL0miBVZ8Psu7K9DW TovN/jw6OnnjbXPQtZA== X-Proofpoint-ORIG-GUID: yynaqCCD4wqXxOS6R5STkpwKSXohvTKg X-Authority-Analysis: v=2.4 cv=c4ymgB9l c=1 sm=1 tr=0 ts=695bfb79 cx=c_pps a=Qgeoaf8Lrialg5Z894R3/Q==:117 a=V6Ol1F/91haf34TWKFX4Fg==:17 a=IkcTkHD0fZMA:10 a=vUbySO9Y5rIA:10 a=s4-Qcg_JpJYA:10 a=VkNPw1HP01LnGYTKEx00:22 a=VwQbUJbxAAAA:8 a=COk6AnOGAAAA:8 a=pGLkceISAAAA:8 a=CDNBFjyWLGXVnZMhk_0A:9 a=3ZKOabzyN94A:10 a=QEXdDO2ut3YA:10 a=x9snwWr2DeNwDh03kgHS:22 a=TjNXssC_j7lpFel5tvFf:22 X-Proofpoint-GUID: yynaqCCD4wqXxOS6R5STkpwKSXohvTKg X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.9,FMLib:17.12.100.49 definitions=2026-01-05_01,2026-01-05_01,2025-10-01_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 lowpriorityscore=0 suspectscore=0 adultscore=0 clxscore=1015 bulkscore=0 impostorscore=0 priorityscore=1501 phishscore=0 spamscore=0 malwarescore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2512120000 definitions=main-2601050156 On 1/5/2026 9:39 PM, mr.nuke.me@gmail.com wrote: > > > On 12/29/25 6:35 AM, Konrad Dybcio wrote: >> On 12/23/25 9:21 PM, Alex G. wrote: >>> On Friday, December 19, 2025 7:20:04 AM CST Konrad Dybcio wrote: >>>> On 12/19/25 5:34 AM, Alexandru Gagniuc wrote: >>>>> Q6 based firmware loading is also present on IPQ9574, when coupled >>>>> with a wifi-6 device, such as QCN5024. Populate driver data for >>>>> IPQ9574 with values from the downstream 5.4 kerrnel. >>>>> >>>>> Add the new sequences for the WCSS reset and stop. The downstream >>>>> 5.4 kernel calls these "Q6V7", so keep the name. This is still worth >>>>> using with the "q6v5" driver because all other parts of the driver >>>>> can be seamlessly reused. >>>>> >>>>> The IPQ9574 uses two sets of clocks. the first, dubbed "q6_clocks" >>>>> must be enabled before the Q6 is started by writing the Q6SS_RST_EVB >>>>> register. The second set of clocks, "clks" should only be enabled >>>>> after the Q6 is placed out of reset. Otherwise, the host CPU core that >>>>> tries to start the remoteproc will hang. >>>>> >>>>> The downstream kernel had a funny comment, "Pray god and wait for >>>>> reset to complete", which I decided to keep for entertainment value. >>>>> >>>>> Signed-off-by: Alexandru Gagniuc >>>>> --- >>>> >>>> [...] >>>> >>>>> @@ -128,6 +137,12 @@ struct q6v5_wcss { >>>>> >>>>>       struct clk *qdsp6ss_xo_cbcr; >>>>>       struct clk *qdsp6ss_core_gfmux; >>>>>       struct clk *lcc_bcr_sleep; >>>>> >>>>> +    struct clk_bulk_data *clks; >>>>> +    /* clocks that must be started before the Q6 is booted */ >>>>> +    struct clk_bulk_data *q6_clks; >>>> >>>> "pre_boot_clks" or something along those lines? >>> >>> I like "pre_boot_clocks". >>> >>>> In general i'm not super stoked to see another platform where manual and >>>> through-TZ bringup of remoteprocs is supposed to be supported in parallel.. >>>> >>>> Are you sure your firmware doesn't allow you to just do a simple >>>> qcom_scm_pas_auth_and_reset() like in the multipd series? >>> >>> I am approaching this from the perspective of an aftermarket OS, like OpenWRT. >>> I don't know if the firmware will do the right thing. I can mitigate this for >>> OS-loaded firmware, like ath11k 16/m3 firmware, because I can test the driver >>> and firmware together. I can't do that for bootloader-loaded firmware, so I try >>> to depend on it as little as possible. I hope that native remoterproc loading >>> for IPQ9574 will be allowed. >> >> These are two parallel questions. I didn't even know that the bootloader >> preloaded firmware on these platforms (are you sure that's the case?) >> >> qcom_scm_pas_auth_and_reset() is usually preceded by qcom_mdt_pas_init() + >> qcom_mdt_load_no_init() where *you* supply the loadable firmware for the >> remote processor. > > What I mean is that the init sequence is implemented in the trustzone firmware which is loaded at boot time. Irrespective of what Q6 and M3 firmware I supply, if trustzone doesn't cooperate, I can't start the remoteproc. I don't have that problem when the init sequence is implemented in the kernel. > >> The init sequence provided by this interface will be at worst identical to >> what you're proposing here (except abstracted out), and at best containing >> some fixes and/or workarounds that may be necessary. > > I think this portrays the TZ path as somehow superior. That's not how things work in my use casee. Adding my 2 cents here, in some platforms, the regions which you are accessing as part of the init sequence might be access protected by Trustzone. This might lead to the kernel bringup failing due to an access violation. This was the motivation behind me asking if this worked in my previous email. Using the TZ interface, as suggested by Konrad, should work in any case. Thanks, Vignesh > > The bootloader/FW versions depends on when and who made the device. So while the newest TZ from upstream may have the latest fixes, I have no guarantee that they will be present on a given device at runtime. The best solution I found to get consistent behavior across devices is to do these sequences from the kernel. Is there something incomplete in my init sequence that I can fix? > >  > Please try using PAS and see if that works. > > I found the v6 of the multipd series [1]. It needed some minor adjustments to compile. I went as far as loading the Q6 firmware and starting the remoteproc without error. I did not test any further. > > Alex > > [1] https://patchwork.kernel.org/project/linux-remoteproc/patch/20231110091939.3025413-1-quic_mmanikan@quicinc.com/ > >