From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 3491C2D7BF; Tue, 7 Apr 2026 09:34:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775554464; cv=none; b=MHr6H2oPzVmIRHysMqP061PUjJRoUel5lXqqrYoRwwfkJEYBEXKaBqtLZusJnAgsao0Q8Bl0+iBiLljQ5QgjWgL5O7qdbr1LG8i/AgL1dh31oNuWM7DDLGQSkwp0QONHHIh8ZzpHrmWz7p0AybltKMtJLZ2sDR3eK6Ja+RaYWU0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775554464; c=relaxed/simple; bh=DOJqK1vcnzd2aYpCEVGT7CW4DJ9dz564DOCE0PC7N+w=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=nVZtLqF0uq/yRZWJbhxkVxc31UEUfkVVSQgvfGzFcsm/cvn9wAC6+yoobdcsHFwNu0bQX4jRkMG+5XuvDRyDXHR6U/PMsBzZL03lijx2vC10d8wPlUOEG3LDUd/RnEwpp4YPbVUNa1zLpj1azeia8A1z/rDeBMLAAhGxNgQkoiI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=RBpd7zWE; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="RBpd7zWE" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B7335C19421; Tue, 7 Apr 2026 09:34:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1775554463; bh=DOJqK1vcnzd2aYpCEVGT7CW4DJ9dz564DOCE0PC7N+w=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=RBpd7zWErz8kmfapDEjomtgKdJmlAtotjpA1DiTmtGklrmYo4YeRwd36fjKYl+F+g pUhwEkPF+SQYVPjujGs1tYNqozAZdQflEErIkaDFkftkI4VEiaeDVDFZWA2aAq5foo mktRJ7Q9XMfy048b/ItWRMFGwIUGdP61VWALkA70uf0cuaQ0ig7f3RKl8Nwyr69nVW K4a11UjfKtW259B8jUPFS4olvzcfWMazbVjSpFlCfCkNsxQMuwKyS/zc9hHKKKsNoN 8JaXMqhmhtALGBmk7owI1jO1QaGjGMflKReZrhhVw3I3lBhA6LGilrX47sVpWSlNel iCwwZEZg1TJ8w== Message-ID: <1f839244-ff46-4b9e-bb93-65785ee8bb2c@kernel.org> Date: Tue, 7 Apr 2026 10:34:18 +0100 Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 0/5] media: qcom: camss: Fix RDI streaming for various CSIDs To: Loic Poulain , Bryan O'Donoghue Cc: Robert Foss , Todor Tomov , Vladimir Zapolskiy , Mauro Carvalho Chehab , Hans Verkuil , Hans Verkuil , Gjorgji Rosikopulos , Milen Mitkov , Depeng Shao , Yongsheng Li , linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org References: <20260406-camss-rdi-fix-v1-0-d3f8b12473d0@kernel.org> <5812c794-fd2c-4b49-8146-db6a1c783706@linaro.org> Content-Language: en-US From: Bryan O'Donoghue In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 07/04/2026 09:49, Loic Poulain wrote: > Okay, then that does reduce the usefulness somewhat... Another point I > hadn’t initially considered is that we may also want to support > different data types on the same VC. For example, metadata, stats, and > image data could be transmitted over the same VC/stream? That seems > like a valid use case enabled by your fix, and it might be worth > explicitly mentioning it. Yes true you can also separate out based on DT. We could have different data-types on the same VC but of course you'd see the DT field in data-stream change and then we'd route that to a different rdi on the VFE. Should be possible to interpret that data from the streams API and route but it is indeed VC+DT to vfe_rdiX where both determine X not just the VC. --- bod