public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Akari Tsuyukusa <akkun11.open@gmail.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
	sean.wang@mediatek.com, 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 09:35:35 +0100	[thread overview]
Message-ID: <9edef237-aab3-4f7f-a86d-ec8796ba87fe@kernel.org> (raw)
In-Reply-To: <20260305-fair-jasper-barracuda-5ae1e6@quoll>

On 05/03/2026 09:27, Krzysztof Kozlowski wrote:
> On Thu, Mar 05, 2026 at 04:24:16AM +0900, Akari Tsuyukusa wrote:
>> 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).
>>
>> 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
> 
> I don't see users of few of these. Also, explain in commit msg
> differences between 'f' and 'h'.

I don't see the "blade" used either.

Best regards,
Krzysztof


  reply	other threads:[~2026-03-05  8:35 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 Lenovo YOGA Tablet 8/10 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 [this message]
2026-03-05 17:08       ` Akari Tsuyukusa
2026-03-05  9:49   ` AngeloGioacchino Del Regno
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=9edef237-aab3-4f7f-a86d-ec8796ba87fe@kernel.org \
    --to=krzk@kernel.org \
    --cc=akkun11.open@gmail.com \
    --cc=angelogioacchino.delregno@collabora.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