From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 74EB4394EB7; Wed, 1 Jul 2026 22:54:55 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782946496; cv=none; b=GtuoJHzXp3KM+3QWHg7PWQqDuaOD+Na2hm8xeiqfqF2D0YDX2g/u11IXS9az0kKT5y2jX4Xqdg3r17Na99H9NSrM0xR592j3eQ8xdHC7TMNRaCgqhpdSRm+3Sgf6vcJsHv4jLY2yr5bD6VSaP2rFI+G/6WxpBcthjZrjlK+2KCA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782946496; c=relaxed/simple; bh=Hmhi7qmI0mpVAxORw9kd/1Iwks7PvSNMTfZfNZK3ueY=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=L+O8cho0oXxUTvKDs7xRmZJSFjISs62FflqLRVX4DypOydCA50dqoj6NEPSokc6KhXh3KycOrmr994TWB3hZeRhzr6VB1YgFJJNi8AUojqJqeP2Jovou+452/K/Pwx2JAJvOQwyhZ2YKoHq69ZRe8+nxbI/I8KzflzN7bKh2fcY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=LUg5l2oP; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="LUg5l2oP" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 969221F000E9; Wed, 1 Jul 2026 22:54:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1782946495; bh=MVGGFAevLvBp9L77WVpeD2HDmtuvw1sCo9+wekarTRc=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=LUg5l2oPGoHK0R5ooHKHBGPlb3cgWORlAtAZAdsZEDVVYH5aj4rxRJkLCAgqVsxK/ 1XBEz0D3RzZZQ/xbEouvFnc+mml0c8f7ca1ZcZDCHiksc+cY/hjwUaGQYiShAG5aTF oOVflm3gwYbA1uSxxihGlqwh/UUuihrW3sELSjBLyAWTMsG9/Ll4pW+pzmzAJXNWpc VEAdWhnY8AUZFtUiBAJQGDzuP7Dhn6O53yaNnPPRoF84XrBretBu/HAL4guOP/oM// yG2nfa2nSN3osttnHgQjQo2kKw/T7JUoGpSzRbGq5AY1KdSFD/yLkFvpcgGZBQbjqg /OsQ0hvHbtv7Q== Message-ID: <7c564df8-5c5a-4b43-806e-5e017e5c51db@kernel.org> Date: Wed, 1 Jul 2026 23:54:51 +0100 Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v8 1/2] dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema To: Vladimir Zapolskiy , Bryan O'Donoghue , Vinod Koul , Kishon Vijay Abraham I , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Neil Armstrong Cc: 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: <20260523-x1e-csi2-phy-v8-0-a85668459521@linaro.org> <20260523-x1e-csi2-phy-v8-1-a85668459521@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: 7bit On 02/06/2026 22:59, Vladimir Zapolskiy wrote: >> + >> + "#phy-cells": >> + const: 1 >> + description: >> + The single cell specifies the PHY operating mode. > #phy-cells should be 0, because the PHY operating mode is well defined > by 'bus-type' property of an endpoint on the sensor side, the opposite > side of CAMSS/CSID as a CSIPHY "consumer" should not dictate the PHY type. So going through the list I don't believe this is correct. Inserting bus-type into the PHY layer is borrowing from one domain linux-media and pushing the concept into PHYs. phy-cells = 1 with CPHY/DPHY specified in the consumer, as was Rob's suggestion will specify the mode. Then to understand if we are in regular or combo mode, we parse the ports/endspoints in the PHY node as we've agreed already. --- bod