Message ID | 20240210070934.2549994-1-swboyd@chromium.org |
---|---|
Headers | show |
Series | platform/chrome: Add DT USB/DP muxing/topology to Trogdor | expand |
On Sat, 10 Feb 2024 at 09:16, Stephen Boyd <swboyd@chromium.org> wrote: > > It's simpler to reason about things if we disable nodes instead of > deleting them. Disable the second usb type-c connector node on > quackingstick instead of deleting it so that we can reason about ports > more easily. > > Cc: <cros-qcom-dts-watchers@chromium.org> > Cc: Andy Gross <agross@kernel.org> > Cc: Bjorn Andersson <andersson@kernel.org> > Cc: Konrad Dybcio <konrad.dybcio@linaro.org> > Cc: Rob Herring <robh+dt@kernel.org> > Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> > Cc: Conor Dooley <conor+dt@kernel.org> > Cc: <linux-arm-msm@vger.kernel.org> > Cc: <devicetree@vger.kernel.org> > Cc: Pin-yen Lin <treapking@chromium.org> > Signed-off-by: Stephen Boyd <swboyd@chromium.org> > --- > .../arm64/boot/dts/qcom/sc7180-trogdor-quackingstick.dtsi | 8 +++++--- > 1 file changed, 5 insertions(+), 3 deletions(-) Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
On Sat, 10 Feb 2024 at 09:17, Stephen Boyd <swboyd@chromium.org> wrote: > > At a high-level, detachable Trogdors (sometimes known as Strongbads) > don't have a cros_ec keyboard, while all clamshell Trogdors (only known > as Trogdors) always have a cros_ec keyboard. Looking closer though, all > clamshells have a USB type-A connector and a hardwired USB camera. And > all detachables replace the USB camera with a MIPI based one and swap > the USB type-a connector for the detachable keyboard pogo pins. > > Split the detachable and clamshell bits into different files so we can > describe these differences in one place instead of in each board that > includes sc7180-trogdor.dtsi. For now this is just the keyboard part, > but eventually this will include the type-a port and the pogo pins. > > Cc: <cros-qcom-dts-watchers@chromium.org> > Cc: Andy Gross <agross@kernel.org> > Cc: Bjorn Andersson <andersson@kernel.org> > Cc: Konrad Dybcio <konrad.dybcio@linaro.org> > Cc: Rob Herring <robh+dt@kernel.org> > Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> > Cc: Conor Dooley <conor+dt@kernel.org> > Cc: <linux-arm-msm@vger.kernel.org> > Cc: <devicetree@vger.kernel.org> > Cc: Pin-yen Lin <treapking@chromium.org> > Signed-off-by: Stephen Boyd <swboyd@chromium.org> > --- > .../boot/dts/qcom/sc7180-trogdor-clamshell.dtsi | 9 +++++++++ > arch/arm64/boot/dts/qcom/sc7180-trogdor-coachz.dtsi | 5 +---- > .../boot/dts/qcom/sc7180-trogdor-detachable.dtsi | 12 ++++++++++++ > .../arm64/boot/dts/qcom/sc7180-trogdor-homestar.dtsi | 7 +------ > .../boot/dts/qcom/sc7180-trogdor-kingoftown.dts | 2 +- > arch/arm64/boot/dts/qcom/sc7180-trogdor-lazor.dtsi | 3 +-- > arch/arm64/boot/dts/qcom/sc7180-trogdor-pazquel.dtsi | 2 +- > arch/arm64/boot/dts/qcom/sc7180-trogdor-pompom.dtsi | 2 +- > .../boot/dts/qcom/sc7180-trogdor-quackingstick.dtsi | 7 +------ > arch/arm64/boot/dts/qcom/sc7180-trogdor-r1.dts | 2 +- > .../boot/dts/qcom/sc7180-trogdor-wormdingler.dtsi | 5 +---- > 11 files changed, 30 insertions(+), 26 deletions(-) > create mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-clamshell.dtsi > create mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-detachable.dtsi > Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
On 10/02/2024 08:09, Stephen Boyd wrote: > The ChromeOS embedded controller (EC) supports setting the state of > GPIOs when the system is unlocked, and getting the state of GPIOs in all > cases. The GPIOs are on the EC itself, so the EC acts similar to a GPIO > expander. Add a binding to describe these GPIOs in DT so that other > devices described in DT can read the GPIOs on the EC. ... > + > +additionalProperties: false > + > +examples: > + - | > + spi { > + #address-cells = <1>; > + #size-cells = <0>; > + > + cros-ec@0 { > + compatible = "google,cros-ec-spi"; > + reg = <0>; > + interrupts = <101 0>; This is should be proper define but then are you sure interrupt is type NONE? Does not look right. Best regards, Krzysztof
On 10/02/2024 08:09, Stephen Boyd wrote: > Add a binding for the USB type-c switch controls found on some ChromeOS > Embedded Controllers (ECs). When this device is a mode switch, it takes > one DisplayPort (DP) port as input and some number (possibly zero) of > USB SuperSpeed ports (bundles of USB SS lanes) as input, and muxes those > lanes into USB type-c SuperSpeed lanes suitable for the SSTRX1/2 pins on > a usb-c-connector. When this device is an orientation switch, it > redirects the DP lanes to the proper USB type-c SSTRX lanes. > > Cc: Rob Herring <robh+dt@kernel.org> > Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> > Cc: Conor Dooley <conor+dt@kernel.org> > Cc: Lee Jones <lee@kernel.org> > Cc: Benson Leung <bleung@chromium.org> > Cc: Guenter Roeck <groeck@chromium.org> > Cc: Prashant Malani <pmalani@chromium.org> > Cc: Tzung-Bi Shih <tzungbi@kernel.org> > Cc: <devicetree@vger.kernel.org> > Cc: <chrome-platform@lists.linux.dev> > Cc: Pin-yen Lin <treapking@chromium.org> > Signed-off-by: Stephen Boyd <swboyd@chromium.org> > --- > .../chrome/google,cros-ec-typec-switch.yaml | 365 ++++++++++++++++++ > .../bindings/mfd/google,cros-ec.yaml | 5 + > 2 files changed, 370 insertions(+) > create mode 100644 Documentation/devicetree/bindings/chrome/google,cros-ec-typec-switch.yaml Ah, and wrong placement. There is no hardware called "chrome", please don't stuff things there. USB switches go to other USB switches (git grep usb-switch.yaml will give you hints). Best regards, Krzysztof