From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wr1-f46.google.com (mail-wr1-f46.google.com [209.85.221.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8CB7B37C931 for ; Fri, 27 Mar 2026 17:42:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.221.46 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774633340; cv=none; b=B3GuQy5ShNjF33rP943cop8KJsEAzFmyCTz2VQQ14K0R6IV5mqpSScFf5pnlH2RgHwt5IWIiUedp0h6B3UvTA2q42zGqAug1GfnaBwk0BFt21O6X8CXS8LOYSC4SQMa9nSmOnVE5U8kSB8XqMQu560zVMi4hWszMMjSR9I7QKNg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774633340; c=relaxed/simple; bh=ETJq2PPi48JVsLsmWI9PZOd4lZiQNUeAf8BRU0YBYTY=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=dlnY8RmXPoA83aNVHhKrJ391HX81ZlBY+0Y8iBp5DBMXX4qhvIxNjyN7VofBuWX1msasr01P3IvoX1My0DQwvmjI8SSBu3/ZXYcLA5VVpyH7A+Dt0roXCH3NGE4+wMPQICjSGGxqtZl4YeFlhmiSXH2KLzXODVI2y4gkhs9rNv8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linaro.org; spf=pass smtp.mailfrom=linaro.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b=wLELYUxH; arc=none smtp.client-ip=209.85.221.46 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linaro.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linaro.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="wLELYUxH" Received: by mail-wr1-f46.google.com with SMTP id ffacd0b85a97d-43b871dd06eso1406029f8f.0 for ; Fri, 27 Mar 2026 10:42:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1774633337; x=1775238137; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:content-language:from :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=Yfu/d6+o0zctQTHLu2MWPdnz/JwccY9dTbonya9Zlio=; b=wLELYUxHX7osQKoxO2CZUd96lWlg7qNF6VR5x0ztPGEAMyIunRJ+4MKieRHjCrx1eK VXW1LA8N4N2cqsh8XrwyuABjr6EmzONiim988HhXPeCemSA7W8XdZ1/iSeK4uA0I2JtE 2XdOpOfvXTdbz8w1q/+/w1apPYzp+myboRxfbKB59z4QtwKlWJUd7LH7LGLdIzh5w6Jp dgutxT2S7uJNyJcuwSlt8lB224+ddNRDj81ltdWjWdFT6ueMSC1ISb6vjdAn3eiJhyy1 3qgPJZWguLiqshgA/Aa7PFeXq4q1GbyA4raQ9cHB622HitwoW0DIhpJjrGM7/yoWlAh1 yX7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1774633337; x=1775238137; h=content-transfer-encoding:in-reply-to:content-language:from :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=Yfu/d6+o0zctQTHLu2MWPdnz/JwccY9dTbonya9Zlio=; b=pfwc97RrCQw+w7bjpQcc+V59Nroa58JWYfI2iKGpWBTTxJkpSh2KVzS/5PzFyWX1Br hjlNPsr7yZq2z7hklnmUdv8TK+MR+KD75gxjwRDAP1XQbwDYOasQC6V+j/7oDbMeMwLH gwfvguRsK+LxSUazFP5uARWwQ2BerZVIdb/JL3xxsLCFhnp1KPkZ3vJmpF7nrMDqi6jT 4sXHuoCAyjkCssROArP4dk/JkzaDMqMKNAhW4irZbEhltJ318MbQZg0/4NZkKvLnOVDJ B0VlJ7cco93eNxvOtGXAG5q/fqb8SnpocTqJQtPiWP/lCovzJN7sB2AnLEM93rYJ+ghB rtgA== X-Forwarded-Encrypted: i=1; AJvYcCVzEmrpLajmFffZKHJGNX2lTMyntGAnhABoZ18l45odGf17/sfjuso2XT6Gele35k2jrsousJYJMrZARg0=@vger.kernel.org X-Gm-Message-State: AOJu0Yx06BT+kJvi0RDv+Gli53c3YOwiaJ68pSX+ec1GSdwje4hRdLWn 3yOjeq9IK9eOKDlJJnvW5JLwK/08nl6qYSi5O4h4vicuaOeSQz5t1T2vQyaZXS8gnkc= X-Gm-Gg: ATEYQzzCohBSVUhY5NaYqxOobBvRQek51phSE926of6drAaDXIv5niw4yOJ5KFsF+Q3 p9ZF2cWh3f6gXTeum+a9B5jSA0dehnchUfgnf+z2Qc2KEtpn9UNFZUOwsqn3nXtz2FGrEvt0Mjd +rxdO/1f53D9Drf5nMrgfwpRVRoqjgRduzHyOYwSbb8NuUfxpLGfdvlvKXYtFSSO3lOrBd7RfyF YDGT6DqeJrPYGPuDoa6JS6pSFZKzU4AI17I8aciP0KYeWzppmJkJRpRs62E35b7lgsR7E0ytnKd dwvBhlhMJjbm2iCojaf1D6QZver8jFJyYrxwe2/fBoaJovJKnTpUKkyPfiOwFyMGVwvyDooOluI Of+2st+yO7kuFCi/wYiFVDExYg8S2Pt5L6TmTpN+V6+rRtO4KeYOCWcdGz0gFkw1ClHR5nc1hwh poE6Mo4THkHq7F918SMO7pnANQqeqcnjJc4Hpu X-Received: by 2002:a05:6000:2006:b0:43b:41df:705e with SMTP id ffacd0b85a97d-43b9ea77850mr5911220f8f.49.1774633336801; Fri, 27 Mar 2026 10:42:16 -0700 (PDT) Received: from [192.168.0.167] ([78.152.214.161]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-43b919432f0sm17358844f8f.13.2026.03.27.10.42.15 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 27 Mar 2026 10:42:15 -0700 (PDT) Message-ID: Date: Fri, 27 Mar 2026 17:42:14 +0000 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 v5 1/2] dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema To: Neil Armstrong , Konrad Dybcio , Vinod Koul , Kishon Vijay Abraham I , Rob Herring , Krzysztof Kozlowski , Conor Dooley Cc: Bryan O'Donoghue , Vladimir Zapolskiy , linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org, linux-media@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <20260326-x1e-csi2-phy-v5-0-0c0fc7f5c01b@linaro.org> <20260326-x1e-csi2-phy-v5-1-0c0fc7f5c01b@linaro.org> <7712fbdd-a225-49f0-aeb9-ebcbb9d5abac@oss.qualcomm.com> <1f38187a-9464-4aa9-b70a-03b767349d56@linaro.org> From: Bryan O'Donoghue Content-Language: en-US In-Reply-To: <1f38187a-9464-4aa9-b70a-03b767349d56@linaro.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 27/03/2026 15:28, Neil Armstrong wrote: >> To be frankly honest you can make an argument for it either way. >> However my honestly held position is analysing other upstream >> implementations connecting to the PHY means we can't make the PHY >> device a drivers/phy device - it would have to be a V4L2 device and >> then for me the question is why is that even required ? > > This is plain wrong, DT definition is different from software > implementation, you can do whatever you want if you describe HW accurately. I'm not sure what point it is you are trying to make here. Are you trying to say drivers/phy is OK with you but you want an endpoint ? If so, please just say so. I can see an argument for that hence my response to Konrad, I just don't see why its a Qualcomm specific argument and of course understood stuff bubbles up in review, we have a public debate and come to a consensus - that's a good thing. However, I'd want wider buy-in and understanding that endpoints in the PHYs is a more accurate description of the data-flow. We've been applying DT bindings aplenty without that so far. So we would establish new CSI2 PHY bindings should represent the sensor endpoints. Is that what you want ? > The CSIPHYs are not tied to a single "consumer" block, they can be > connected to different consumers at runtime, which is not something > classic PHY devices are designed for. So they are de facto a media > element in the dynamic camera pipeline. The existing CAMSS binding and media graph are not changed by this series. > And actually Rob Herring asked use to define the complete data flow, it > was a strong requirement. I don't see why we wouldn't here. I'm implementing feedback from Rob. https://lore.kernel.org/linux-media/20250710230846.GA44483-robh@kernel.org/ To me, here is where we stand: - Individual nodes - we all agree that - As sub-nodes - I think the majority agrees this Krzsztof, Dmitry I'm fine with it too. - drivers/phy - I think we are accepting this is also fine ? - endpoints should flow into the PHY and then back to the controller I get that argument. In fact I _like_ that argument at least I like my conception of that argument. I'll stipulate to that argument meaning then that, new CSI2 PHYs shall include endpoints for this purpose globally. As I've said before, there's nothing Qualcomm specific about this discussion, really. --- bod