From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Akari Tsuyukusa <akkun11.open@gmail.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
matthias.bgg@gmail.com, sean.wang@mediatek.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: mediatek: Add Lenovo YOGA Tablet 8/10
Date: Thu, 5 Mar 2026 10:49:28 +0100 [thread overview]
Message-ID: <e8c587e8-61af-4ef7-b7dd-7d8da7b9aeff@collabora.com> (raw)
In-Reply-To: <20260304192417.818211-2-akkun11.open@gmail.com>
Il 04/03/26 20:24, Akari Tsuyukusa ha scritto:
> Add the "lenovo,blade" compatible string for the Lenovo YOGA Tablet 8/10
> family and add compatible strings for each board
> (B6000-F, B6000-H, B8000-F, B8000-H).
You're adding support (a devicetree) only for the B8000-F though...
>
> These tablets are based on the "blade" platform, featuring 1GB of RAM
> and powered by MediaTek MT8125 or MT8389 SoCs. Since these SoCs are
> tablet-oriented variants of the MT6589, they are grouped under the
> "mediatek,mt6589" compatible string.
>
> Signed-off-by: Akari Tsuyukusa <akkun11.open@gmail.com>
> ---
> Documentation/devicetree/bindings/arm/mediatek.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/mediatek.yaml b/Documentation/devicetree/bindings/arm/mediatek.yaml
> index 382d0eb4d0af..69dbe389515c 100644
> --- a/Documentation/devicetree/bindings/arm/mediatek.yaml
> +++ b/Documentation/devicetree/bindings/arm/mediatek.yaml
> @@ -44,6 +44,11 @@ properties:
> - items:
> - enum:
> - fairphone,fp1
> + - lenovo,b6000-f
> + - lenovo,b6000-h
> + - lenovo,b8000-f
> + - lenovo,b8000-h
> + - lenovo,blade
> - mundoreader,bq-aquaris5
> - const: mediatek,mt6589
> - items:
Did you really test this with dtbs_check?
...also, is the "lenovo,blade" really used for anything (bootloader)?
You can either fix that or just remove the lenovo,blade compatible... but please,
test with `make dtbs_check` before sending a v2 :-)
Cheers,
Angelo
next prev parent reply other threads:[~2026-03-05 9:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 19:24 [PATCH 0/2] Add initial support for " Akari Tsuyukusa
2026-03-04 19:24 ` [PATCH 1/2] dt-bindings: arm: mediatek: Add " Akari Tsuyukusa
2026-03-05 8:27 ` Krzysztof Kozlowski
2026-03-05 8:35 ` Krzysztof Kozlowski
2026-03-05 17:08 ` Akari Tsuyukusa
2026-03-05 9:49 ` AngeloGioacchino Del Regno [this message]
2026-03-05 17:19 ` Akari Tsuyukusa
2026-03-04 19:24 ` [PATCH 2/2] arm: dts: mediatek: mt6589: add basic support for Lenovo B8000-F Akari Tsuyukusa
2026-03-05 9:46 ` AngeloGioacchino Del Regno
2026-03-05 15:49 ` Akari Tsuyukusa
2026-03-06 14:06 ` AngeloGioacchino Del Regno
2026-03-12 4:36 ` Akari Tsuyukusa
2026-03-12 12:54 ` AngeloGioacchino Del Regno
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=e8c587e8-61af-4ef7-b7dd-7d8da7b9aeff@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=akkun11.open@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.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 \
--cc=sean.wang@mediatek.com \
/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