From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Fei Shao <fshao@chromium.org>, Matthias Brugger <matthias.bgg@gmail.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: mediatek: Add MT8188 Lenovo Chromebook Duet (11", 9)
Date: Wed, 6 Nov 2024 14:19:11 +0100 [thread overview]
Message-ID: <eb0a7307-de25-47b1-aaed-032c7734ec70@collabora.com> (raw)
In-Reply-To: <20241105093222.4055774-2-fshao@chromium.org>
Il 05/11/24 10:30, Fei Shao ha scritto:
> Add entries for the MT8188-based Chromebook "Ciri", also known as
> Lenovo Chromebook Duet (11", 9).
>
> This device features a detachable design with touchscreen, detachable
> keyboard and USI 2.0 Stylus support, and has 8 SKUs to accommodate the
> combinations of second-source components.
>
> Signed-off-by: Fei Shao <fshao@chromium.org>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> ---
>
> (no changes since v1)
>
> Documentation/devicetree/bindings/arm/mediatek.yaml | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/mediatek.yaml b/Documentation/devicetree/bindings/arm/mediatek.yaml
> index 1d4bb50fcd8d..4b68f0baf010 100644
> --- a/Documentation/devicetree/bindings/arm/mediatek.yaml
> +++ b/Documentation/devicetree/bindings/arm/mediatek.yaml
> @@ -307,6 +307,19 @@ properties:
> - enum:
> - mediatek,mt8186-evb
> - const: mediatek,mt8186
> + - description: Google Ciri (Lenovo Chromebook Duet (11", 9))
> + items:
> + - enum:
> + - google,ciri-sku0
> + - google,ciri-sku1
> + - google,ciri-sku2
> + - google,ciri-sku3
> + - google,ciri-sku4
> + - google,ciri-sku5
> + - google,ciri-sku6
> + - google,ciri-sku7
> + - const: google,ciri
> + - const: mediatek,mt8188
> - items:
> - enum:
> - mediatek,mt8188-evb
next prev parent reply other threads:[~2024-11-06 13:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 9:30 [PATCH v2 0/2] Add device tree for MT8188-based Chromebook "Ciri" Fei Shao
2024-11-05 9:30 ` [PATCH v2 1/2] dt-bindings: arm: mediatek: Add MT8188 Lenovo Chromebook Duet (11", 9) Fei Shao
2024-11-05 14:06 ` Krzysztof Kozlowski
2024-11-06 13:19 ` AngeloGioacchino Del Regno [this message]
2024-11-05 9:30 ` [PATCH v2 2/2] arm64: dts: mediatek: Introduce MT8188 Geralt platform based Ciri Fei Shao
2024-11-06 13:19 ` AngeloGioacchino Del Regno
2024-11-07 6:58 ` Fei Shao
2024-11-07 10:37 ` AngeloGioacchino Del Regno
2024-11-08 4:11 ` Fei Shao
2024-11-11 7:10 ` Fei Shao
2024-11-14 10:09 ` AngeloGioacchino Del Regno
2024-11-18 5:26 ` Fei Shao
2024-11-18 6:42 ` AngeloGioacchino Del Regno
2024-11-05 13:11 ` [PATCH v2 0/2] Add device tree for MT8188-based Chromebook "Ciri" Rob Herring (Arm)
2024-11-06 6:30 ` Fei Shao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eb0a7307-de25-47b1-aaed-032c7734ec70@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fshao@chromium.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).