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 7BFA02E4997 for ; Thu, 3 Jul 2025 12:38:38 +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=1751546320; cv=none; b=MWvfPii9e8+s9jppUGxrw3eTfR54Y1PzWvAM0hK11eD4KOFyfR5P7QtvcnB19ScpLbv1ET+4kJRcoAxkFqkaNN3sikKz0wF/leJqOFV9V8EI6aZjIqyoX5nO1BMxLJzYEMA7dKdu/0q8dKRdgTUfiVJjGhcUcDd7QMSUEX6Wp5g= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1751546320; c=relaxed/simple; bh=blvhHAuvKd0z+M6UM8fJg7hW66Y0sZvUde7gR9VDZFc=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=Z7eBuQAICp73nj+AMfDmOTvl4NbPkFtlVDAP9mb6969oXaHRQs+MeGcDuekYso0Bi8V4kS6saWtRIVNXMUVLztb1+0r1/9682sTRJqQ5YT9Mf7UXidZMLWgLy8R6WuwcMT4olnFLQb9XvxkzozxElCxutnORXpLT45LraGVyinU= 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=c07+vPHx; 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="c07+vPHx" Received: from pps.filterd (m0279872.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 5637mYDa015165 for ; Thu, 3 Jul 2025 12:38:37 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= Qh8aZ053Ew1qTcqO548gAuyDU01MqTeC46OFogIdvLU=; b=c07+vPHx3IKsaKNJ +53zzbImtZLBaVhX0gRwKtESHcuUKKzex75Hisgg7BKtV2h2MORMWrimj02M1qKA 6Il+GHeP/ycLt1WdHxuqsodzLwnK/+XSd4NLEfy/sp3D1V2RhAgyT9UMJ722Vws8 GHbDeqon/n0jBwk3zeazACWa1hXYNSCx9JM0NC0cGfYXCA4sPYIno4tWj4p4SdpX gUkEVZ5glqNFNNM7u6AY2sf1gFt2cdn/nHWZs1C9vWneLMctqLki16etuQLb3fVX Lw7GZiAtwnFhIsDnXZaq1ooNaQp0Ws7LpVbdfUQlPS8DkU8vZuVO3PD0f8IaayQj uptZsw== Received: from mail-qv1-f72.google.com (mail-qv1-f72.google.com [209.85.219.72]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 47j8s9rf4t-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Thu, 03 Jul 2025 12:38:37 +0000 (GMT) Received: by mail-qv1-f72.google.com with SMTP id 6a1803df08f44-6fb030f541bso23145926d6.1 for ; Thu, 03 Jul 2025 05:38:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1751546316; x=1752151116; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Qh8aZ053Ew1qTcqO548gAuyDU01MqTeC46OFogIdvLU=; b=JfnhldEoIqt3Rc3OKHJE1jCwnMZDG7KHqKqTLsWLol6doFM4diciEmK5xT2fVFXlyK vOSv7pWrDGa3YS17PhzfGy0Vxal5eBjtTaPpGcYnZDl2I3Civ4iD/ZqHifd9s2ntetSU kTJeV48KS0dQNlldFc5lVtxf39eOOp4U9DlBlvWG406CgWEPzhj0+6Py5MS78Zds4pIa woAFkupJAkTnHb3DszuHBDNMkHJ8vS57UEor5hWvcU/Xnr1gB4luXC35Giu0G9k10mN2 a6R9EV2IEyPzEDyc00vX10ukmczKX0ow7sL2pF+P1B2b92nhlRSfBjmVv48yq/Z00AYD mL7g== X-Forwarded-Encrypted: i=1; AJvYcCXKTpsKmz7dWC6Ll3Gi7mQrWmSC68YKVIjtd9tZdehGmdlEbSWm67yt2AttNfYUwWwHXM/RCkmkThqeqA==@vger.kernel.org X-Gm-Message-State: AOJu0YxKy3oNuIdOcwMhKQv5d+PByu9EH7mUfFM0DDkKQ3BCUHBNu8Jx 4D0v5lSaqp3W3VwD0r/n90PLcIz/TVa9tWC7YBXcy7ngEI2xEZrsZE5PQNabF1FcAzTRKGWf06y Sx9VOAAxMj90sIyBCkhuSz0zE0PErdhVeOeYh/ym5ez4nKRCL71cA1dl03NP5K58/Xw== X-Gm-Gg: ASbGncssJqAulmgJ0fJ4Ws49xq9xIBfS+2L2wimQRFZSj9pSjx1aXb7AYIrynlfJ4SJ 0Fd2F1AAGzu5ncceYgtdzY3i5B5fWrvWPywkQFRDliWz8ROJ6Lki1FWpcAa2UGeYcTyUxf+OoRq DkaGpvBSQFCnxJwtiwUF2fxiy2nWluzuTLoPnu2zSif+wPX8Ym8FKoxAetJ4pwFNBfrz2rOFafQ YIGkFB8nrzOsAeo2BpPqfPAqBu6PU1NsMPGaun6f2ubGbL64cA4JK0IN2Y+OM85KZnh1jVjUP4C Lr/gYAvwKPKoxqDHBoSqKdNQ4NALgwg9DaNzlFWJX6hKpRtDJgH+NI4qFhNV5MqnGXdqo+G3tHu MgmDWT6AQ X-Received: by 2002:a05:620a:28c3:b0:7d3:b0a3:6aa7 with SMTP id af79cd13be357-7d5d3eb6529mr119135385a.3.1751546316485; Thu, 03 Jul 2025 05:38:36 -0700 (PDT) X-Google-Smtp-Source: AGHT+IHwk4eFNYt3i3rxN0XJmcdLSCwy/gouEpTFY2xPCM13VPaFLKLCRNVsyEKzUlz6/p28jLHr6A== X-Received: by 2002:a05:620a:28c3:b0:7d3:b0a3:6aa7 with SMTP id af79cd13be357-7d5d3eb6529mr119134985a.3.1751546316055; Thu, 03 Jul 2025 05:38:36 -0700 (PDT) Received: from [192.168.1.114] (83.9.29.190.neoplus.adsl.tpnet.pl. [83.9.29.190]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-ae353ca20fesm1272538066b.174.2025.07.03.05.38.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 03 Jul 2025 05:38:35 -0700 (PDT) Message-ID: <1ad2ca1e-1d57-4ad8-a057-ab0d804f1d49@oss.qualcomm.com> Date: Thu, 3 Jul 2025 14:38:33 +0200 Precedence: bulk X-Mailing-List: linux-media@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v3 0/5] Introduce "non-pixel" sub node within iris video node To: Krzysztof Kozlowski , Dmitry Baryshkov , Bryan O'Donoghue Cc: Vikash Garodia , Dikshita Agarwal , Abhinav Kumar , Mauro Carvalho Chehab , Rob Herring , Krzysztof Kozlowski , Conor Dooley , linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <20250627-video_cb-v3-0-51e18c0ffbce@quicinc.com> <5f90547d-945a-4e26-b36c-75f2d8a1af97@kernel.org> <5ad418d9-8199-43c9-a477-1e3b939c054c@kernel.org> <7b6db4fa-2f73-376d-4eb3-64c1c7e6cda3@quicinc.com> <5qsgbqml367yq6g5vb4lotrzulojqhi5zlwwribze373a63qrn@rxi4kwyt66m2> <4f38058d-a2f1-4ac5-b234-228cfb2e85ff@kernel.org> Content-Language: en-US From: Konrad Dybcio In-Reply-To: <4f38058d-a2f1-4ac5-b234-228cfb2e85ff@kernel.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Authority-Analysis: v=2.4 cv=H/Pbw/Yi c=1 sm=1 tr=0 ts=686679cd cx=c_pps a=7E5Bxpl4vBhpaufnMqZlrw==:117 a=fKQzr7EGRj+VoE0XNsDNvQ==:17 a=IkcTkHD0fZMA:10 a=Wb1JkmetP80A:10 a=V26NVJm5TTlvxhDq-ocA:9 a=QEXdDO2ut3YA:10 a=pJ04lnu7RYOZP9TFuWaZ:22 X-Proofpoint-ORIG-GUID: Wlb6TnC-pz99uU_dM0WvOB5mLuNyfa5H X-Proofpoint-GUID: Wlb6TnC-pz99uU_dM0WvOB5mLuNyfa5H X-Proofpoint-Spam-Details-Enc: AW1haW4tMjUwNzAzMDEwNSBTYWx0ZWRfXyVADRt9J1IKp K6momhYIQgG9LwFnhLvc8AJl9c4Mda7XGWe7PE1y5UY7WK0YDo/nO7Mo6WvJDYxTzjhmO2ygDsi ylDfd4SvFahtNn1+jcU16YTY4rMUo/foRRe1RMCAtJH0gyKfrVotoZTASsFyM96vsC58ElCymdP Muewxo4C+HmMPS0bYiJz+TAWT1k4+H4wxw4pRJk+MApvL98V4FbugWehTmvXg3OLMEVAGbT7eFB FQw/i5kVp12jMUwsVa6CEW2EMe5E2G59Y+okW1oNh3Nw5s58WFVq4035FmyyxhMgVpZ2cr0xD2w BnmLFwj1BPlQ4RGossHk/wdKngNAjfunsCBdlCsTw8Ig/OClir6803JsBVK3ElA22ucQ4z0ZD83 KjC9VjjgnbAzN11LDmcXFE+9EgqQHRebNjBovALGiqMbXTT70Xol7BnkVhIljr1tyGxmBpRG X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1099,Hydra:6.1.7,FMLib:17.12.80.40 definitions=2025-07-03_03,2025-07-02_04,2025-03-28_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 impostorscore=0 malwarescore=0 suspectscore=0 mlxlogscore=900 priorityscore=1501 clxscore=1015 mlxscore=0 lowpriorityscore=0 spamscore=0 adultscore=0 bulkscore=0 phishscore=0 classifier=spam authscore=0 authtc=n/a authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.19.0-2505280000 definitions=main-2507030105 On 03-Jul-25 09:27, Krzysztof Kozlowski wrote: > On 03/07/2025 00:26, Dmitry Baryshkov wrote: >> On Wed, Jul 02, 2025 at 01:06:17PM +0100, Bryan O'Donoghue wrote: >>> On 02/07/2025 13:01, Vikash Garodia wrote: >>>>> Anyway, in other messages I explained what is missing. You are changing >>>>> existing hardware and you clearly must explain how existing hardware is >>>>> affected, how can we reproduce it, how users are affected. >>>> Exactly all of these i have explained in the commit message. The limitation with >>>> existing hardware binding usage and how my new approach mitigates that limition. >>>> >>>> Coming to usecase, i made a generic comment saying usecases which needs higher >>>> IOVA, i can add the explicit detail about usecase like 8k or higher >>>> concurrencies like 32 or higher concurrent sessions. >>> >>> Why not make this change for a new SoC, instead of an existing ? >> >> Because we definitely want to improve support for older SoCs too. > > Older SoCs came with completely new drivers and bindings, instead of > evolving existing Venus, so they for sure came with correct code and > correct binding. No, this is a terrible assumption to make, and we've been through this time and time again - a huge portion of the code submitted in the early days of linux-arm-msm did the bare minimum to present a feature, without giving much thought to the sanity of hw description, be it on a block or platform level. That's why we're still adding clocks to mdss, regulators to camera etc. etc. to this day. And it's only going to get worse when there will be a need or will to add S2disk support with register save/restore.. Konrad > > That was one of the reasons why duplicating venus was accepted: to get > things right, so obviously your argument cannot be true, right? > > Best regards, > Krzysztof >