From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.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 B68611C8633 for ; Sat, 9 Aug 2025 11:43:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=205.220.168.131 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1754739836; cv=none; b=PbaKU7pKEM42Dm+xg8kI7ZKMAAm7y2FnP2comFALC5EpzNm4Ld5KINJfO/oC9Wkdf/9VDsry1qTkfHibu9aCWUn5x7SvvFrmV2xGi8+bzHI/18gf+jwFLg7Z6rFtU+ECpt8elE1XaAAw1DXdlWyGE7iZFZoIXQNqfzQeP3N7gx8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1754739836; c=relaxed/simple; bh=SwO5nELXRLBtJc5KwDzdoxO3kOP3CyZAe2nh9etB1hI=; h=From:Date:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=EZkkJQtLmoN8nIm3ZCI7r9ZQS+K425AHI2eRpAXcB1T3VixYXK2AbrdGGxFeigVc7LtqGiK1RNlZeORk4QlPMnQJ62FbbNXu8fHLpLUalQXaTS3fVcPRbcUv023SvTxcc50qnrfIEVDwAAzCJGOLNglXAo28yAAAAu9LJhpUbaw= 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=ShIujPF1; arc=none smtp.client-ip=205.220.168.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="ShIujPF1" Received: from pps.filterd (m0279864.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 5794e27X010455 for ; Sat, 9 Aug 2025 11:43:54 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= Dhq7QtFTNob/e68BFvCh2tCGaBjvEnXwpiBGxxMlG8A=; b=ShIujPF1qx23DOVC snJMx5DvsRwluCSvPpoXpdLOJGvKZL6pIwCEtcsO7J6QR5Khg9tqnL5oTAxsS5vJ WFxjBrXDL7mG9tYg+MvTwd7/Wunz3SA2qQrdTH6Fbn+DltMlwsJDMmoucgCs42Gs a+sboUBPdvz+PFVyJvaRY3jkaCm32lYI4CscIG+1U9jT6KUu++Yc97jb7/x8vTvC y9dfLJh3z/ZPOnsy8L8fsBBMMzHI634jOlo1qluY+QiQ70IIJc7WzBCYaQ65dOQ8 l2cdWYxynsyRe+DmsTd+zKFFiDkjYylPMezfL1ihXq39ptyL7a5y52vTdoXH31QW S8jF4A== Received: from mail-qt1-f199.google.com (mail-qt1-f199.google.com [209.85.160.199]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 48dygm8fd2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Sat, 09 Aug 2025 11:43:53 +0000 (GMT) Received: by mail-qt1-f199.google.com with SMTP id d75a77b69052e-4b0a3557d05so57528471cf.2 for ; Sat, 09 Aug 2025 04:43:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1754739832; x=1755344632; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:date:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Dhq7QtFTNob/e68BFvCh2tCGaBjvEnXwpiBGxxMlG8A=; b=bt7L20VMsIrggqHr23qaSx9XmnDFjWOQMuCnRwFklcpQQ/aRYT6ZZPf0tpTYdqTdmU N19ByNWoOeMkEQyLTkzKFp4ZUK69LzqIsmlrEhSnIJhGKDQ/Fr1iaFzoOqxvgyPsLO4N bXSyVnWSeDYs4vpFtYQEZYzBdNRFovBaiSjXlWgPXkmpY+3O494GyfrAzfFvHDyW2oKz sNhrP6MHc0Zz7DWc4b5fn3zWXzAVTFZ9TvKednfx4BDITTSf+Zd34rGA50s2dWehIriG xGfIxcHodJ9/3QPJyylBdN8/JTDJJ1jFOiUWYjUkZAyEhwOGemMlsKV/RzLEQCmhiUYl SWig== X-Forwarded-Encrypted: i=1; AJvYcCUc4DaB4LckXlj53uLcaLn0pKDSNbrsHvOay2C/WeLLlc88lnYLK4x6x4aLBaTYj+6bPQWgPk0jXB9R@vger.kernel.org X-Gm-Message-State: AOJu0Yw8+T9ajmfp7ld2as7ZyCyY7hJuW5F5yxiM3GsdfN8JP2uNmKHP azfSJ3son1pd8xjrJhIifQ/lrC1p8eU9S+8m8GgYLwbq3yI0hQRDs7AyT4ILXxULyEG/u8emzLM U2bUrRIg6E6+0GhKfXHgawfyJkvPvg1UweY7etE7BSX5A1wBM2iZk4eNDn+MGaja7 X-Gm-Gg: ASbGncsqsokwkwjS4PIH+MG3XO3k37Aw+XvfudRebmAoD0n9cllQhxxfmlhdW4Ecz53 T+H7mgvVMqAgJPbx6GSE6kMD8UD1AI7HIDWul2vO0HRLCJ5239tt1uH1h/25v51K8N4p2hguwpQ PFqRnggv0yKj0esOuIsArE2Sa7yWrLxD+NY5W9VUzxs/hXJTX9DcyHyxaVjhbatduXH60HTpA2d frfMK8iCN/Fe7QVGe4IcxgHbGWDLPys9NrZ4vsKU9o+115EODrMixOU0V3BOO9lisHQz5vrR8jE GWMJB5+/K3JgqhOJVJQhg5CMfFMjQfy4Z8SMSRDovgFOk5jPECAzgpQo5DVBL2cn8se5tg== X-Received: by 2002:a05:622a:4a10:b0:4af:1a43:6a52 with SMTP id d75a77b69052e-4b0aec78545mr96034771cf.16.1754739832329; Sat, 09 Aug 2025 04:43:52 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEzqs1ndblPPDaYRCzYH6G5/RMWdae2a1I3H1jVxQ9aCs494h/N6aUaTOA+9QAqxW5zPf/3sA== X-Received: by 2002:a05:622a:4a10:b0:4af:1a43:6a52 with SMTP id d75a77b69052e-4b0aec78545mr96034361cf.16.1754739831696; Sat, 09 Aug 2025 04:43:51 -0700 (PDT) Received: from trex (205.red-83-60-94.dynamicip.rima-tde.net. [83.60.94.205]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-3b79c3bc12csm34291769f8f.28.2025.08.09.04.43.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 09 Aug 2025 04:43:50 -0700 (PDT) From: Jorge Ramirez X-Google-Original-From: Jorge Ramirez Date: Sat, 9 Aug 2025 13:43:49 +0200 To: Dmitry Baryshkov Cc: Jorge Ramirez , Vikash Garodia , Konrad Dybcio , bryan.odonoghue@linaro.org, quic_dikshita@quicinc.com, konradybcio@kernel.org, krzk+dt@kernel.org, mchehab@kernel.org, conor+dt@kernel.org, andersson@kernel.org, linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v8 5/7] media: venus: core: Add qcm2290 DT compatible and resource data Message-ID: References: <0248afed-b82d-4555-8277-e84aacf153fd@oss.qualcomm.com> <447caa6d-13d2-2e75-5f33-6df9b2fd6d69@quicinc.com> <2yj3er5j72yoa2ltboopx5gvquur7jl3viqnq5qsci2fxjf4ix@7t63vgizfknb> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Proofpoint-Spam-Details-Enc: AW1haW4tMjUwODA5MDAzNSBTYWx0ZWRfX0Cu6AVuFb02r uvSKcLKvQH0PYHrR8Sm4PUw0hohinXjD93paqqS4P6UB2gca6Kf/2astaGUlU1DmTS5eKpKo9pq 882dj3r7KMd7SnhvU2rUiKdVYpDrKwtYgD6JnXB9TTGTv/q/PXS+1JG8lPkNLRIi/1GJp0RGB1p YGmZaCEXee9qT4Fylxd0oM+VFa+VCCtwVUOIPYqeme/FVsE3jbzWbP9d/OQUq8mS/qHPDOtagd0 Qy431UHqpvMIj+AZf6MT8zsma9PPPjgrEOM4t8kHjbSPcNCcypxXuTLm6rF+ORWV47q4sFEDRgl EiG5kp8qg6lHfVn2j4//Xhx73YmKpasAZWqPlvqDhf5aYpFGN1TF97W0lIIu0do87uwaycfh5VD VuhqI0gA X-Authority-Analysis: v=2.4 cv=FvMF/3rq c=1 sm=1 tr=0 ts=68973479 cx=c_pps a=WeENfcodrlLV9YRTxbY/uA==:117 a=Rr2dNH5/fcnoRoBmcVUeRg==:17 a=IkcTkHD0fZMA:10 a=2OwXVqhp2XgA:10 a=MGQ6gT6oETv9xCBFa_IA:9 a=3ZKOabzyN94A:10 a=QEXdDO2ut3YA:10 a=kacYvNCVWA4VmyqE58fU:22 X-Proofpoint-GUID: xslFhQt94RZodbCLiWim_Xk6iPBb8Qo6 X-Proofpoint-ORIG-GUID: xslFhQt94RZodbCLiWim_Xk6iPBb8Qo6 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1099,Hydra:6.1.9,FMLib:17.12.80.40 definitions=2025-08-09_03,2025-08-06_01,2025-03-28_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 bulkscore=0 suspectscore=0 phishscore=0 clxscore=1015 impostorscore=0 spamscore=0 adultscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.19.0-2507300000 definitions=main-2508090035 On 09/08/25 12:22:39, Dmitry Baryshkov wrote: > On Sat, Aug 09, 2025 at 11:09:24AM +0200, Jorge Ramirez wrote: > > On 09/08/25 11:18:21, Dmitry Baryshkov wrote: > > > On Thu, Aug 07, 2025 at 10:05:10PM +0530, Vikash Garodia wrote: > > > > > > > > > > > > On 8/7/2025 7:22 PM, Jorge Ramirez wrote: > > > > > On 07/08/25 16:36:41, Vikash Garodia wrote: > > > > >> > > > > >>> It was agreed that this complexity was not necessary and that we should > > > > >>> just drop <6.0.55 firmware support (which would in any case only include > > > > >>> video decode). > > > > >>> > > > > >>> And so on v8, I removed the above. > > > > >>> > > > > >>> Now I have v9 ready to post it, but Dmitry is asking why cant we have > > > > >>> the v7 functionality so I am waiting for direction. > > > > >> > > > > >> the issue is in firmware for both encoder and decoder. Didn't like the idea of > > > > >> driver carrying the hack for a firmware issue. Just because, for encoder, we are > > > > >> unable to hack it in driver, we are ok to have it enabled in a newer version of > > > > >> the firmware, we can follow the same for decoders as well. > > > > > > > > > > if that is the only reason please do explain what do you mean by hack. > > > > > > > > I meant that the EOS handling was not needed in driver after fixing it in > > > > firmware, isn't it ? Was trying to avoid carrying this in driver. > > > > > > > > I tend to agree with the comment made by Dmitry in another thread to have decode > > > > enabled with existing firmware, no option but to support the *already* published > > > > bins. > > > > > > > > Having said that, these limitation of having a separate EOS dummy buffer is well > > > > sorted out in gen2 HFI which have an explicit DRAIN cmd for it. Hope this > > > > motivates you to migrate to iris soon for AR50LITE variants :) > > > > > > Migrating to Iris won't bring gen2 HFI. Think about users which have > > > OEM-fused hardware. For them it's not possible to switch firmware from > > > gen1 to gen2. Thus, if the SoC has been released using gen1 HFI, we > > > should think twice before upgrading it to gen2. > > > > > > > As I understand it now after the thread, any driver developer working on > > new features should not be constrained by users with OEM-fused hardware. > > > > Since only the OEM can provide signed firmware updates, it is their > > responsibility—not ours—to figure out how to deliver those updates if > > they want their users to benefit from new features (or new fixes). > > The OEMs might go bankrupt, might stop supporting hardware, might not be > bound by EU laws, etc. If the platform was shipped with gen1 HFI and we > suddently provide gen2 HFI, the driver must support both firmware > interfaces for that platform. sure, that is backwards compatibility > > > The EU Cyber Resilience Act supports this view by placing the update > > obligation on manufacturers (at least that is what I understand it, let > > me know if you understand it differently) > > > > Breaking backward compatibility is something we must avoid of > > course. However, guaranteeing compatibility between old firmwares > > (whether signed or not) and _new_ features is a separate matter... > > Anyway, the kernel is provided separately from the firmware. If we > supported a particular firmware set, we can not break that. > > AR50_LITE is a corner case, as we have been shipping the firmware, but > there was no corresponding open-source driver for that platform. right > > -- > With best wishes > Dmitry