From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3BAFCC07524 for ; Mon, 13 Nov 2023 22:15:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231833AbjKMWPi (ORCPT ); Mon, 13 Nov 2023 17:15:38 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38666 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231713AbjKMWPf (ORCPT ); Mon, 13 Nov 2023 17:15:35 -0500 Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 45597D73 for ; Mon, 13 Nov 2023 14:15:31 -0800 (PST) Received: by mail-lf1-x12f.google.com with SMTP id 2adb3069b0e04-507bd19eac8so6646573e87.0 for ; Mon, 13 Nov 2023 14:15:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1699913729; x=1700518529; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=CavqYbpJDhm0OKuh4STOsXUdXIvRsCGtB4InVaES23I=; b=FofDm00yUf4ACJaFKDl1isGSOwGscsQjQksuo3C2m7L/cNffYutXe0yKjSbAPlUso6 NRSK5C4L4RLoZ9tAIauzhYmdfoNIp67bHquMTQj2HoymtXyq4aR74nGWSh2O52LEbWyK rMLQuESuU4KhTZ28c/ViiMF3xrGuxk2Zh3UD+9cGlwZRk4wHWil9i4TBi77SUXm8neZM QVDlHKz6l8tYBLr5b1LJuckYABKSq7hYojEEs0pE4vKNdukBhKyEGrwvQX74AkaVuy+b FOsYFxn1oXQ6vglRCFibiTjZU7h/d2ANe+5jhYr7g0kLea/us6SlAUMtPNx9JPuhUxod /s0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699913729; x=1700518529; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=CavqYbpJDhm0OKuh4STOsXUdXIvRsCGtB4InVaES23I=; b=friNaeNygb+XtW4iE6Kz24o1qT4zh9LXp7xVYfSmDRioDhT/qjbEudxmbpFogPP19z OTdApILgYOhI47M+/NwHjNG5ivAU/1cEtDyHHfnpKVu/affVcYlJXPY/E5wDjB08dCLe AEUYAGVmrozeHMMss8i5GqOQ3z6vDH9pk6yScrjwR+LmZ2cVIkG8ZpNFOCJHxI3lNvy8 dtovNi68Be+qhhkXANzDbKeKN8kUMRQReYrpNEwvosEsVt+voi4yf1LMHmE6l4NumHLM MrJVu9V8K1NLHMhWP5HYvij2YBy4e387/oAQzF8471GLGz9RyhQKBmt1FfVsoYOpgMI5 TvFw== X-Gm-Message-State: AOJu0YwFfVFRRQ1lm3Gm3tS0IDllG4RV66LUk0I80nKZFej7NFKlBIYQ s6d9QJVWquAYObKiYOIaiska+Q== X-Google-Smtp-Source: AGHT+IGReEDcnEERO89WQ2VhevAyWOeYn9OJtVWGTf7awX8F6nWP1bv1VZ+A0hyce6bKbkbjmUVZ5g== X-Received: by 2002:a05:6512:1087:b0:507:b7db:1deb with SMTP id j7-20020a056512108700b00507b7db1debmr6898125lfg.38.1699913729380; Mon, 13 Nov 2023 14:15:29 -0800 (PST) Received: from eriador.lan (dzdqv0yyyyyyyyyyybcwt-3.rev.dnainternet.fi. [2001:14ba:a0db:1f00::8a5]) by smtp.gmail.com with ESMTPSA id w8-20020a0565120b0800b00507f18af7e0sm1097578lfu.4.2023.11.13.14.15.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 13 Nov 2023 14:15:28 -0800 (PST) From: Dmitry Baryshkov To: Rob Herring , Krzysztof Kozlowski , Conor Dooley , Andy Gross , Bjorn Andersson , Konrad Dybcio , Hans de Goede , =?UTF-8?q?Ilpo=20J=C3=A4rvinen?= , Mark Gross , Heikki Krogerus , Greg Kroah-Hartman Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, platform-driver-x86@vger.kernel.org, linux-usb@vger.kernel.org Subject: [PATCH v2 0/3] dt-bindings: connector: usb: provide bindings for altmodes Date: Tue, 14 Nov 2023 00:13:26 +0200 Message-ID: <20231113221528.749481-1-dmitry.baryshkov@linaro.org> X-Mailer: git-send-email 2.42.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org In some cases we need a way to specify USB-C AltModes that can be supportd on the particular USB-C connector. For example, x86 INT33FE driver does this by populating fwnode properties internally. For the Qualcomm Robotics RB5 platform (and several similar devices which use Qualcomm PMIC TCPM) we have to put this information to the DT. Provide the DT bindings for this kind of information and while we are at it, change svid property to be 16-bit unsigned integer instead of a simple u32. NOTE: usage of u16 is not compatible with the recenty extended qcom/qrb5165-rb5.dts DT file. I'm looking for the guidance from DT and USB maintainers whether to retain u32 usage or it's better to switch to u16. Changes since v1: - Added type:object and fixed 'description' string in the altmodes-list definition. Dmitry Baryshkov (3): dt-bindings: connector: usb: add altmodes description usb: typec: change altmode SVID to u16 entry arm64: dts: qcom: qrb5165-rb5: use u16 for DP altmode svid .../bindings/connector/usb-connector.yaml | 36 +++++++++++++++++++ arch/arm64/boot/dts/qcom/qrb5165-rb5.dts | 2 +- drivers/platform/x86/intel/chtwc_int33fe.c | 2 +- drivers/usb/typec/class.c | 5 +-- 4 files changed, 41 insertions(+), 4 deletions(-) -- 2.42.0