From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-180.mta1.migadu.com (out-180.mta1.migadu.com [95.215.58.180]) (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 292D91D5170; Tue, 24 Feb 2026 18:45:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.180 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771958721; cv=none; b=dYft7R7hZrpKxvM78hSaa1qiKQ3POh+URnEaWKehn9tWx7yixRtT8VbS2Boekb8TYnvRShbU8eMxab0qzqwVX0heuCg8J4AJAxH8KsUi6j2nqCKdlSmQNvnsQfGGop0XiUcCQ+Qp4W7yXRZ4JmCvExeRfGiPhcs41rqwV1FAicY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771958721; c=relaxed/simple; bh=SqolAWGlUuLI3GWRT27Gw5TF43c8uynCsM1+ZmdyY0Y=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=eVnRXdX3uWO84KXU+dpBMjMQoCV1RjvcDVaFU/gePsDd6QboF52A5wPZM+nssKLuRnviLeG4kjqYfgxS5834zIYBXV5BnMA8clmTJQlyBOtl2gvZwtCpi4WdOQbwiCli0jWOEVLCBbxWJLy9M2BJujQy/Z0KIabEERnczYRtkF4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=packett.cool; spf=pass smtp.mailfrom=packett.cool; dkim=pass (2048-bit key) header.d=packett.cool header.i=@packett.cool header.b=KUeOs5ER; arc=none smtp.client-ip=95.215.58.180 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=packett.cool Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=packett.cool Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=packett.cool header.i=@packett.cool header.b="KUeOs5ER" Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packett.cool; s=key1; t=1771958716; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=XFvAN+eThWLRnldrhy5N9eq98qVVFyFFadQtYFCknE4=; b=KUeOs5ERjE4CmcrKHoSDRiDxz8WcjSY7WPUhlSjBy9OwKiP2QuHdI20AQstwce59aslGXa ZaFZB1ldfe8hG947Z6XZkTCoWBzk6YMy2r07pha+8ToOvPCHerrlQEna7O4GI8L+rv8Uig srLDuurRuY9eQ0/ejTGLgsrh6PcsKXFWFe867T4VQi3T26oAeu+vWC16v8wpJfVDomNfdi sFsfEp8nrXQZHriQpvcf/+dSCPYpQdQwnz/dSbdzx3w9uC04gjampRnnRTQHRsdDTbJCDE nkYLGN4kR5mINub2UcTyMCZx9tsx0ppZ8+39PKlBnKPF5NGeMrfXvlaUn2Jz7Q== Date: Tue, 24 Feb 2026 15:45:05 -0300 Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH v2] remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3 To: Bjorn Andersson Cc: Mathieu Poirier , Nathan Chancellor , Nick Desaulniers , Bill Wendling , Justin Stitt , =?UTF-8?Q?Matti_Lehtim=C3=A4ki?= , Luca Weiss , Vladimir Lypak , =?UTF-8?B?QmFybmFiw6FzIEN6w6ltw6Fu?= , Konrad Dybcio , Dmitry Baryshkov , ~postmarketos/upstreaming@lists.sr.ht, linux@mainlining.org, phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org, llvm@lists.linux.dev References: <20260201210230.911220-1-val@packett.cool> Content-Language: en-US X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Val Packett In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT On 2/23/26 5:03 PM, Bjorn Andersson wrote: > On Sun, Feb 01, 2026 at 05:55:03PM -0300, Val Packett wrote: >> The changes introduced to handle single power domain platforms have >> swapped the info pointer increment from num_pd_vregs to num_pds, which >> would shift the info pointer past the end of the array for pronto-v3, >> which does not list power domain regulators in vregs. >> >> This showed up as a difference between GCC- and LLVM-compiled kernels >> on SDM632 devices, where only with LLVM one would get the >> "regulator request with no identifier" error, because the out-of-bounds >> memory ended up being zeroed. Fix by skipping the increment when there >> are more power domains than regulators. >> > Is the error only an error print, or did the thing stop working as well? It's a real error. Likely no one would've bothered debugging it if it weren't breaking everything :) It was a blocker for allowing LLVM/clang builds of the msm8953 kernel in postmarketOS, the whole reason to dig into this was "switching to clang breaks the modem, WTF?!" ~val