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 60C6D309F02 for ; Tue, 2 Dec 2025 10:13:26 +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=1764670408; cv=none; b=Ecj42q7/cUw+aLWthykiHKgYrZSFBVFh6o47NgOKgrWe8gS8JiWnVB8d996IPUrKQHFkimLmjGE9Ks++0MyUU8cpjnBBIQHnsKmY8r/0gaiWgL6yz1+3NNm1Frd1JvlZ4nzRE07jxb6LLQtXwEhbYD4gcN7AFE7YYRTbds6eMWw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764670408; c=relaxed/simple; bh=jkD0PgX4AYLD/tWeanomvQ7p36iUYtXramiDJGNxlqY=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=qgHMUv9Im5l1HxuvigaLgPQV0krcBTJZSwyqbTwvL/U7t+fthau7Owl/E1EJ9BV3YAiP7g7KNQDivkfJBx7a5EX6RqqNDRXsspD/vExX+idrs70S2WvmMg3IpSDxIlJakv6SS9wExdVc67YdI0W7CkUNXn+GwWHf+ebC+KEC8uQ= 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=T7FBKA6m; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b=V2odpmc4; 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="T7FBKA6m"; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b="V2odpmc4" Received: from pps.filterd (m0279873.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 5B27llb61926507 for ; Tue, 2 Dec 2025 10:13:25 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= LsmArkF89BOUHhGXQUlWFZF2aiQoOW1ZrRrGna7xdxg=; b=T7FBKA6m/ge7cXxt AXpuCZXKHfSJS4y+bY0aaVnQr4Fgd3vhmQcJz1p/CmJpjFtM8Obz7+j7Rgw9zI26 DX5mhc5PDqf4bJxyKhtCxk7ToPh/sEND4h6Jt48sjxdEbBDxtcYBldwzm7Cu+Zwe w1gE5HFrUT/YPw/UCzOANxGS07yRASCudBSnjWsCFtpIFkFz/nQjR4wZI8bPJKKB K97Yeq5U9AJosGbQqGArzbtjLYi4ijvYPLyoDHj5TCeD+nEDYkHUSfLhvEMzSfyn w/9/d/Dxi42kzCnJLvYD2OuIofHA1ImuyiE4X6TFCJdFG9GodeE34jfnGSsbj7qj 1GkM7A== Received: from mail-pf1-f200.google.com (mail-pf1-f200.google.com [209.85.210.200]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 4asm4xsu5h-1 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Tue, 02 Dec 2025 10:13:24 +0000 (GMT) Received: by mail-pf1-f200.google.com with SMTP id d2e1a72fcca58-7aa9f595688so7561266b3a.2 for ; Tue, 02 Dec 2025 02:13:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oss.qualcomm.com; s=google; t=1764670404; x=1765275204; 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=LsmArkF89BOUHhGXQUlWFZF2aiQoOW1ZrRrGna7xdxg=; b=V2odpmc4ypMEQtQyAR1x303PwKwZwzY0Jj2E7/YyeutsNyUfAVGGLds9uZmSwCq4eC jrwqnS6Kxmha96p8N+VU0/C2YzynLu94czRigHOPXqDiNb2bnKyp1Ba52EUb9UBQMR4K jNlS65+kk4KAtdLuE3RWauQHtWvfH5aonXsSWHjIs/1ZDLhmj3VVpoclECTEFlUDEnMT 5+C/OULPHtfaCQS61QrK2vv/XqhkdlpY4fy7nw4URXQS1Acp+gL8kd3/L3yMLtJz63b3 q8XC72EAXLPEI7gq30mp6Vx03Eh9fcw9FGOwFXKuYeUMxGz/VAngv6egCf6gSR3uJdzE 6Nhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764670404; x=1765275204; 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=LsmArkF89BOUHhGXQUlWFZF2aiQoOW1ZrRrGna7xdxg=; b=KNNVuyI2fQh11Sn/nNbTZwr4aND+D/o/tBbditT0U6RMArizhnMrSs1DR5LzApgMou fTUPJzd/70jhYUYPQw5nJS1ToL4h6UfBZ2evZ53U5l1cO/3E6wyN7mFC0xLQig2Xd0Rq oTQ8oZcPDkAA7DW5R/X9Kwk1oYT3OlKvwjzCjPLS96sZOfBz7UAsaClAg0zU4PRIlMpl in6AsEKHSLl1YcLs4fxyf9uoYlvWvLnPNw7RNcwcRTKRmPqvagrXE5p5F+ePvOHC1BWb x1t64juNbzTHwt03WtuLqvDm8aKNAEHaPIk555+JWE6oW9HfOy3X8gh0Vr9goZG74N8M hfhw== X-Forwarded-Encrypted: i=1; AJvYcCVE+ucN4MLz6+UBS2Nbx24nALOMToae1GS/zOdpfx+xCv8Zs73QJD+BC6SKNr9ZtnuG9rsib4lujmBBLNk=@vger.kernel.org X-Gm-Message-State: AOJu0YxPVNj9GSPj+/ToCUGFLqDcYE4A12xkoovgO+11BNgMeMM6TICO uDL6L4ULY+0WSGtMZnyJ/GkJ+THF+SaC2viYLmSUl+RGlCkDzXmyGjFAD0Waj1NUFuGSwyysKqF pnRLb8Is2dd7O7Qc+knj8CgLsu4YvTSHTtse0qfdkz93vHvCMV2+FNA+TRE3Of2k3eOc= X-Gm-Gg: ASbGncsNkTpYY18sbZH9tDBldsn6TuC9Rkqy+rXLvfJkNs+v8K5mXqQgFmyg2RblTWf lkhYfvFHgzQmmUA7uekNWK9Ox5vh5gILOJXdr02TbBz8NHJcIjKNJLeemtRt08X6uGZsfIeqaFj wlFh88DEMVu239z25T8ABNqL7i3YpPlSOU5xwp33DKkZpNx4tLYzHBWMTU4NTVVHY7aZcucq59X GAkd+gdjdUGbOIQiOpyzjna8GPeIRvuqAkoTlmqfJuO6pisyGATR/+m02icYmuFFy++tTx9MZxN ME1MUiS40NnCvhB9Smu4TJ2FvfBNcfYL00LzWyG3ygF7r93z7FoRpRaK54tXiTimlz5gRuzhuyr CUER9wF+PWJWdySrQCPuckK7HrVydeqlFen7hQTCLxA== X-Received: by 2002:a05:6a00:17a7:b0:7b8:383d:870e with SMTP id d2e1a72fcca58-7c58c2ab7b5mr43279787b3a.2.1764670403810; Tue, 02 Dec 2025 02:13:23 -0800 (PST) X-Google-Smtp-Source: AGHT+IESsZ966I0XhgbDr2ekmgjrYiAu9aQpL3u5Xnmdj7BMfBxv2ve0RBT+vHWnMSj5FtqfLf96iA== X-Received: by 2002:a05:6a00:17a7:b0:7b8:383d:870e with SMTP id d2e1a72fcca58-7c58c2ab7b5mr43279759b3a.2.1764670403377; Tue, 02 Dec 2025 02:13:23 -0800 (PST) Received: from [10.206.101.67] ([202.46.23.25]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-7d15fc08bd1sm16402354b3a.63.2025.12.02.02.13.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 02 Dec 2025 02:13:22 -0800 (PST) Message-ID: <623225c2-166a-49a1-9856-d02ed55f1e47@oss.qualcomm.com> Date: Tue, 2 Dec 2025 15:43:17 +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 v8 00/14] Peripheral Image Loader support for Qualcomm SoCs running Linux host at EL2 To: Mukesh Ojha , Bryan O'Donoghue Cc: Bryan O'Donoghue , Bjorn Andersson , Mathieu Poirier , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Manivannan Sadhasivam , Konrad Dybcio , linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Konrad Dybcio References: <20251121-kvm_rproc_v8-v8-0-8e8e9fb0eca0@oss.qualcomm.com> <0156c327-b867-481e-af24-679f037bfa56@linaro.org> <20251121113751.tnqw5abm5sd2rgr7@hu-mojha-hyd.qualcomm.com> <9dfe5343-824d-42c2-aab8-8389602601e9@kernel.org> <20251202083650.luk2jpcquq2pcf2r@hu-mojha-hyd.qualcomm.com> Content-Language: en-US From: Vikash Garodia In-Reply-To: <20251202083650.luk2jpcquq2pcf2r@hu-mojha-hyd.qualcomm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Proofpoint-GUID: p692Vbg_NBAXVQB4BsTc33P-MgE8byRx X-Proofpoint-Spam-Details-Enc: AW1haW4tMjUxMjAyMDA4MSBTYWx0ZWRfX+1yOIyFGSao+ e9SYE5Ys8LtyGRs7Tsk4Tt4xr/P5uD84pHiqEpkjRIZn4UJmY4gtm2bqR/XxrTSnZOCdAfoYvh1 kwtW47mmCoW5AEJLnVWbw7lO8jtwlahzeGFcwqfc+bzBrZOHn6ibL6XW2icoDEtCKgJQTPCmqqt HoMO3lixdSkagkobNpjtcwNS+kPbgwkZONeuNHKwxU2tmsTf7T6y4e9++JTyevz6ffhp1fVWBPH a/NRwl3LnNP3/YkdVmC3z7bl4UWQH9DXaQ/8Gx4N59mgnG2uHC+F/hilEU6vW7MJnz75liwKj0T 4E/fTshXsdApMpXlACdX2+Gx6E0u7tpB3pOnA9bW+4/2TXNyr78yzxSsj5ErJ1IovEnYEhb3B+K n57Ws1YKx6vSi7MhfWm9SobRoNbA3w== X-Authority-Analysis: v=2.4 cv=cPTtc1eN c=1 sm=1 tr=0 ts=692ebbc5 cx=c_pps a=mDZGXZTwRPZaeRUbqKGCBw==:117 a=ZePRamnt/+rB5gQjfz0u9A==:17 a=IkcTkHD0fZMA:10 a=wP3pNCr1ah4A:10 a=s4-Qcg_JpJYA:10 a=VkNPw1HP01LnGYTKEx00:22 a=VwQbUJbxAAAA:8 a=KKAkSRfTAAAA:8 a=COk6AnOGAAAA:8 a=EUspDBNiAAAA:8 a=Ajh8_egcEEMJNl95zMkA:9 a=3ZKOabzyN94A:10 a=QEXdDO2ut3YA:10 a=zc0IvFSfCIW2DFIPzwfm:22 a=cvBusfyB2V15izCimMoJ:22 a=TjNXssC_j7lpFel5tvFf:22 X-Proofpoint-ORIG-GUID: p692Vbg_NBAXVQB4BsTc33P-MgE8byRx 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=2025-12-01_01,2025-11-27_02,2025-10-01_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 impostorscore=0 lowpriorityscore=0 bulkscore=0 adultscore=0 malwarescore=0 priorityscore=1501 clxscore=1015 phishscore=0 spamscore=0 suspectscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2510240001 definitions=main-2512020081 On 12/2/2025 2:06 PM, Mukesh Ojha wrote: > On Thu, Nov 27, 2025 at 10:25:23AM +0000, Bryan O'Donoghue wrote: >> On 21/11/2025 11:37, Mukesh Ojha wrote: >>>> Sorry. >>>> >>>> Did we actually come up with a cogent reason to omit the video firmware >>>> loading here ? >>>> >>>> AFAIU it is required for Lemans and Glymur - leaving it out is blocking >>>> getting video stuff done and storing up trouble. >>>> >>>> What exactly is the blockage - is it something you want help with ? >>> I replied to you here[1] and given my reason..till something concluded on >>> "multi-cell IOMMU[2]", I can not add video and block what is working >>> already. >>> >>> [1] >>> https://lore.kernel.org/lkml/20251105081421.f6j7ks5bd4dfgr67@hu-mojha- >>> hyd.qualcomm.com/ >> >> Why though ? >> >> You are mixing together the issue of multiple SIDs and the original loading >> of firmware which could easily reuse the venus method of >> >> &iris { >> video-firmware { >> iommus = <&apss_smmu hex>; >> }; >> }; > > I completely understand what you are saying, and it would be very easy > for me to do that if it gets accepted. However, I doubt that the people > who raised this concern would agree with the approach. > > I’m not sure if the video team would like to pursue pixel/non-pixel/firmware context > banks separately. I’ll leave this to @Vikas to answer. Not exactly as a separate sub-node, but i do like the idea of introducing a simple iommu property, something like this, which Stephan proposed earlier in the discussion [1] firmware-iommus = <&apps_smmu ...>; I understand that we are doing the iommu-map thing, but a property exclusively for firmware like above look much simpler to me. Dmitry/ Bryan/ Krzysztof if you are good with this, we can bring back video in this series. Please share your thoughts on this. Regards, Vikash [1] https://lore.kernel.org/lkml/aKooCFoV3ZYwOMRx@linaro.org/ > > Also, I do not want the video PIL discussion to be part of this series, as it could > unnecessarily give the impression that this series depends on it. > >> >> That binding got dropped because it was unused in Iris. >> >> https://lore.kernel.org/lkml/05d40a3b-cc13-b704-cac7-0ecbeea0e59d@quicinc.com/ >> >> I still fail to see why we are waiting for multi-cell IOMMU to land, when it >> is expected to and what the VPU enablement story is upstream in the >> meantime. >> >> Blocked it seems. > > No, it is ongoing, there will be next version coming. > >> >> --- >> bod >