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 96CFE22758A for ; Thu, 6 Feb 2025 11:30:56 +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=1738841458; cv=none; b=KwhRewf3aZ/dJDOmT7RT57u493XX8mUfm8qeDujtP6xjC3XW5XxQfWLgG1Uz3S4TkoFx+onFKg9VSphOxWKN5BBVDpzH9FHTjH9A5TtT55TIfxn24u/UiZPvEXZ7FtA+nZEC0XZd9CZiwaUGLKme+c/Fqb8jjv8HOmHknIDdYgw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1738841458; c=relaxed/simple; bh=+kJFybMU29i1ocNVrjOt1XzKDp4dKUhYjmoAXiIMHSg=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=hbm13VpVl4Vo4fEwzIcH759iYAbCJrOcbaAOrCZOOjObM/Y1hkdLQ/FhV85sdKVN6ZvnCho7bgcZPbMlkWQOKmUHONInLtLRH/TyWgXiRRsaFvPabDVpiHk32BYeHmnn/qIv/3H2zHeVXZvXIN3BBxpVDIJv3XiArksa/LydMHE= 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=HzsM3LvD; 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="HzsM3LvD" Received: from pps.filterd (m0279865.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 5169Cepx014793 for ; Thu, 6 Feb 2025 11:30:56 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= cdjlky8vQqWoR/DClvLfxcIIKQztp9TSGwGX4STpaG0=; b=HzsM3LvDlfRhLbwv YT0GiyN1s7fwuW6yK+lAI2PeWbfEcyHUk1GwMuAOnHO8a5du8BUfsZIXB6dPZCXN elZG4t2OnnoUEDCbp9acHMr9veBls2GraxUupra2+M7TTQafdK1y6fbywetrXSbK uOZXHAHjO1tSFstFB7hfo8Q69UR1otyzTyFOntRxxg5Sc1mIeYXiTrPMFtK4mnTg BB4bNjEB63OcpcIeW7WkhCQZQErw0FjG/M/GbVV3+wFCjifaFVOr8AdqhVLOS++h AmCVirRH7ueJp9NW70hoGLoshXa5gohWyRYoj/Y3KxEYpckbin5cYyM3TOjjFOI2 26N6tw== Received: from mail-qt1-f197.google.com (mail-qt1-f197.google.com [209.85.160.197]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 44mt8e0bs4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Thu, 06 Feb 2025 11:30:55 +0000 (GMT) Received: by mail-qt1-f197.google.com with SMTP id d75a77b69052e-46b3359e6deso2579171cf.2 for ; Thu, 06 Feb 2025 03:30:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738841454; x=1739446254; 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=cdjlky8vQqWoR/DClvLfxcIIKQztp9TSGwGX4STpaG0=; b=ja7ztP3cPDh2sr7S/+vPY5//Xv0gh9MxB5IGYKVAVv5Auz9s5ypc7PBguL+JwyBrko sY5PYj9hosnh8zcomRZOxfwlLUu1UPEH9Li/MSDDHalipL9jJSwepS2OEk/fX+fIZ3hE o8i+sIWNfUj8w7fHxgQa/RQ0cJnmomnEdDUoJyDzXRgOsL3S1LlgpvEiF/HNzxYn/17R M+gVLV/Zo9nfXL1fL1Xy/Q7boDIQ2duOKurTY+qbS5AynYBuHl6pHsarQzHqovfC7hfJ dutKnjGHGTFgB1kutoOBkYi2FY9R2eoFKD1I3NRficFQqvR6vyWKXIBTToGJaTJ2Fp0b NxUg== X-Forwarded-Encrypted: i=1; AJvYcCUlF69/W+E9FJaKMxbjjwdhK7UL2DJDGaxd2y5RqS8Y2PJXZHjFKqGJzSXaE0yAWCUKV/5D0ijaCY6vL+OyAuU=@lists.linux.dev X-Gm-Message-State: AOJu0YxNnCXjPmhqeJ5ov5zeFs818xgSnHAbFObl8YajpZacDHD8pI3+ RUtOEXOvcItX5gEI+Zgm8iRk3skfVhPncpElJW4fHXYO0LPAXud+bxJ7lHpa9ZeyEWtyO0WSen1 QN/hhfD5HHVLvVRUMHuZ+DVL6KL/5wX1quW6XpLHPbRL8GYzQIhJ7VsKrqPZqxNFlzrQ= X-Gm-Gg: ASbGncuX2lW8Vbbt1HBvcjjazn4W2IpKtTcjvNf6PgQQy0gwtfb35hR9oJK5fBiaRpR gk+HdbwdCERAjSztl5tdNSj7wrSFWx7V726O3hi910z4ABmdVh+L2heAsbZsCaWEmN8Z3HntzyN 4p9zej5warv9+p8/YtB/yrwKB3luDCrF3coIW5114Gk4O0bfVB2ZqcqpQmtyEA3TW+2M7l/V4cc IVGfs5/3q4TJQwVqGCezoS+jolwLkHF4+2lbyy59LwaBM+dCD06tZ4Ab/i8d9ChenR+pafVLgAn MUn9wyN9X8BcEc7YUXmsaVG4D/jnMqH/zT2oEMcrK8YtIhFvV7hCk3Plapg= X-Received: by 2002:a05:622a:14ce:b0:464:889f:a41e with SMTP id d75a77b69052e-470281879a6mr35208501cf.1.1738841454363; Thu, 06 Feb 2025 03:30:54 -0800 (PST) X-Google-Smtp-Source: AGHT+IGkpfa+4IQFCPrfzSK+M4AEnSEY06jPWO2IJilWAzgSn6R+5ZMyekAr2oFw0CAA6OD5gd6Fdg== X-Received: by 2002:a05:622a:14ce:b0:464:889f:a41e with SMTP id d75a77b69052e-470281879a6mr35208281cf.1.1738841453750; Thu, 06 Feb 2025 03:30:53 -0800 (PST) Received: from [192.168.65.90] (078088045245.garwolin.vectranet.pl. [78.88.45.245]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-ab77365ff55sm84490166b.181.2025.02.06.03.30.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 06 Feb 2025 03:30:53 -0800 (PST) Message-ID: <74527323-31ff-4ed0-b19f-e535f26abf2b@oss.qualcomm.com> Date: Thu, 6 Feb 2025 12:30:50 +0100 Precedence: bulk X-Mailing-List: chrome-platform@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2 1/2] dt-bindings: chrome: Add binding for ChromeOS Pogo pin connector To: Stephen Boyd , Konrad Dybcio , Bjorn Andersson Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, patches@lists.linux.dev, cros-qcom-dts-watchers@chromium.org, Rob Herring , Krzysztof Kozlowski , Conor Dooley , Benson Leung , devicetree@vger.kernel.org, chrome-platform@lists.linux.dev, Pin-yen Lin References: <20250205233016.1600517-1-swboyd@chromium.org> <20250205233016.1600517-2-swboyd@chromium.org> Content-Language: en-US From: Konrad Dybcio In-Reply-To: <20250205233016.1600517-2-swboyd@chromium.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Proofpoint-ORIG-GUID: ntq6T8N9iqo0H8WUBQigy99cEsNfhpkI X-Proofpoint-GUID: ntq6T8N9iqo0H8WUBQigy99cEsNfhpkI X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1057,Hydra:6.0.680,FMLib:17.12.68.34 definitions=2025-02-06_03,2025-02-05_03,2024-11-22_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 bulkscore=0 phishscore=0 adultscore=0 priorityscore=1501 impostorscore=0 mlxscore=0 spamscore=0 lowpriorityscore=0 suspectscore=0 mlxlogscore=999 malwarescore=0 clxscore=1011 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2501170000 definitions=main-2502060095 On 6.02.2025 12:30 AM, Stephen Boyd wrote: > Describe the set of pins used to connect the detachable keyboard on > detachable ChromeOS devices. The set of pins is called the "pogo pins". > It's basically USB 2.0 with an extra pin for base detection. We expect > to find a keyboard on the other side of this connector with a specific > vid/pid, so describe that as a child device at the port of the usb > device connected upstream. > > Cc: Rob Herring > Cc: Krzysztof Kozlowski > Cc: Conor Dooley > Cc: Benson Leung > Cc: > Cc: > Cc: Pin-yen Lin > Signed-off-by: Stephen Boyd > --- > .../chrome/google,pogo-pin-connector.yaml | 68 +++++++++++++++++++ > 1 file changed, 68 insertions(+) > create mode 100644 Documentation/devicetree/bindings/chrome/google,pogo-pin-connector.yaml > > diff --git a/Documentation/devicetree/bindings/chrome/google,pogo-pin-connector.yaml b/Documentation/devicetree/bindings/chrome/google,pogo-pin-connector.yaml > new file mode 100644 > index 000000000000..622e171b6b08 > --- /dev/null > +++ b/Documentation/devicetree/bindings/chrome/google,pogo-pin-connector.yaml > @@ -0,0 +1,68 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/chrome/google,pogo-pin-connector.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Google Pogo Pin Connector This looks like a very generic piece of hw.. many boards (esp. convertibles) do the same thing, with 4 or 5 pins on the bottom of the device. But of course hw manufacturers being hw manufacturers, many different kinds of signals go through such connectors - if it's not USB then it's perhaps I2C or some variation thereof IMO, we could perhaps add this to usb-connector.yaml as "usb-custom-connector" or so Konrad