[v1,1/2] dt-bindings: display: panel: raspberrypi: Add compatible property for waveshare 7inch touchscreen panel
Message ID | 20231124104451.44271-2-shengyang.chen@starfivetech.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:ce62:0:b0:403:3b70:6f57 with SMTP id o2csp1071330vqx; Fri, 24 Nov 2023 02:45:12 -0800 (PST) X-Google-Smtp-Source: AGHT+IHcpRdtp4Du56MVoTURLMzW0s+I3KGFhUArUcrcAlCcLbfQjOolGf4K0oSQRH+3WOf/C9xe X-Received: by 2002:a17:902:d4cb:b0:1c4:4462:f1bd with SMTP id o11-20020a170902d4cb00b001c44462f1bdmr2544361plg.35.1700822712331; Fri, 24 Nov 2023 02:45:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1700822712; cv=none; d=google.com; s=arc-20160816; b=n8sOUMEY/qMJ2OpGSlvEtmsQn5syEzJNCSowKQQidLHXc/SBCYBuHkdU2xGtEe3sj6 LHDZmOvHADutAVk/qs6hVd9Of+7ZSNl9srPjiaMdOPuxQ1DBiT0WJxAAexGUZmZ2Y1Gh Z2WSJ+QgTE1+thI8FW9nKiYb8yUPov4ICKantTIS5kTDJxFTE3kPLn6yAi8FsN2OTri7 P8Iu1PMRoj21ZdjaEwrO753Uj4+MB9hDp5DILSVCATppe5mHFe0YJedGcqufEsALxjJ+ +ZMeuQ34Bb6NSJfKgFmbltFh+r4jopFyHvtHb/U9sV3DTbp78ncJHI45YMtJjnx25gDg FG4A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from; bh=2psRUajNxwvjtgwvRaj2VntshlIKVGKYPmdU2xE/6qY=; fh=HdKC1Y26FhBgoGJ8HMU+IavW3w3oWEnuTkb2R7hprvA=; b=t80cN+vogmiqMW/5kg0qQjPjbfQEfQ7oU1wlApKk8A1Tgt7oBV2bpuISuUdhnfrwrH 8jXfM2S3h4u3Xp6VPUqIjjxagkIcjBBGiN6J0mO3wCGxpX6wyh//+b+te8MRd6fnIWzG ZfDFhTDZABgv2MTiYF6g1QdqRutn2EHkcgX1X2/4KDDiCTWY8A2tBCAp9DlqNRuvKsjX O2LEqF2tZtRYZOxQKAL6Wio+JGZeZPdcQvyQLBvk0TBm2UVaXHe5ZcSXpXQv1QfJdI+c qdK3O+VmoDV7BnWNc1MMlygMtLlAJRlx8J03/dxBaAnAWrDQBAtrFQ2hRrf08BwSE7Or 5Vyg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from howler.vger.email (howler.vger.email. [2620:137:e000::3:4]) by mx.google.com with ESMTPS id t15-20020a170902e84f00b001c9ca0a03ecsi3279550plg.2.2023.11.24.02.45.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 24 Nov 2023 02:45:12 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) client-ip=2620:137:e000::3:4; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by howler.vger.email (Postfix) with ESMTP id 2EDBE8049168; Fri, 24 Nov 2023 02:45:08 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at howler.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345648AbjKXKo7 (ORCPT <rfc822;ouuuleilei@gmail.com> + 99 others); Fri, 24 Nov 2023 05:44:59 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39288 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345640AbjKXKo5 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Fri, 24 Nov 2023 05:44:57 -0500 Received: from ex01.ufhost.com (ex01.ufhost.com [61.152.239.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C42EF12B; Fri, 24 Nov 2023 02:45:01 -0800 (PST) Received: from EXMBX166.cuchost.com (unknown [175.102.18.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "EXMBX166", Issuer "EXMBX166" (not verified)) by ex01.ufhost.com (Postfix) with ESMTP id 04AA524E0D8; Fri, 24 Nov 2023 18:44:54 +0800 (CST) Received: from EXMBX171.cuchost.com (172.16.6.91) by EXMBX166.cuchost.com (172.16.6.76) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Fri, 24 Nov 2023 18:44:54 +0800 Received: from yang-virtual-machine.localdomain (113.72.144.198) by EXMBX171.cuchost.com (172.16.6.91) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Fri, 24 Nov 2023 18:44:52 +0800 From: Shengyang Chen <shengyang.chen@starfivetech.com> To: <devicetree@vger.kernel.org>, <dri-devel@lists.freedesktop.org> CC: <neil.armstrong@linaro.org>, <quic_jesszhan@quicinc.com>, <sam@ravnborg.org>, <airlied@gmail.com>, <daniel@ffwll.ch>, <maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>, <tzimmermann@suse.de>, <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>, <florian.fainelli@broadcom.com>, <bcm-kernel-feedback-list@broadcom.com>, <eric@anholt.net>, <thierry.reding@gmail.com>, <changhuang.liang@starfivetech.com>, <keith.zhao@starfivetech.com>, <shengyang.chen@starfivetech.com>, <jack.zhu@starfivetech.com>, <linux-rpi-kernel@lists.infradead.org>, <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org> Subject: [PATCH v1 1/2] dt-bindings: display: panel: raspberrypi: Add compatible property for waveshare 7inch touchscreen panel Date: Fri, 24 Nov 2023 18:44:50 +0800 Message-ID: <20231124104451.44271-2-shengyang.chen@starfivetech.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20231124104451.44271-1-shengyang.chen@starfivetech.com> References: <20231124104451.44271-1-shengyang.chen@starfivetech.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [113.72.144.198] X-ClientProxiedBy: EXCAS062.cuchost.com (172.16.6.22) To EXMBX171.cuchost.com (172.16.6.91) X-YovoleRuleAgent: yovoleflag X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on howler.vger.email Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (howler.vger.email [0.0.0.0]); Fri, 24 Nov 2023 02:45:08 -0800 (PST) X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1783441875862260751 X-GMAIL-MSGID: 1783441875862260751 |
Series |
Add waveshare 7inch touchscreen panel support
|
|
Commit Message
Shengyang Chen
Nov. 24, 2023, 10:44 a.m. UTC
The waveshare 7inch touchscreen panel is a kind of raspberrypi pi panel and it can be drived by panel-raspberrypi-touchscreen.c. Add compatible property for it. Signed-off-by: Keith Zhao <keith.zhao@starfivetech.com> Signed-off-by: Shengyang Chen <shengyang.chen@starfivetech.com> --- .../bindings/display/panel/raspberrypi,7inch-touchscreen.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
Comments
On Fri, Nov 24, 2023 at 06:44:50PM +0800, Shengyang Chen wrote: > The waveshare 7inch touchscreen panel is a kind of raspberrypi pi > panel Can you be more specific about what "is a kind of rpi panel" means? Are they using identical chips as controllers or something like that? > and it can be drived by panel-raspberrypi-touchscreen.c. > Add compatible property for it. > > Signed-off-by: Keith Zhao <keith.zhao@starfivetech.com> > Signed-off-by: Shengyang Chen <shengyang.chen@starfivetech.com> > --- > .../bindings/display/panel/raspberrypi,7inch-touchscreen.yaml | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml b/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml > index 22a083f7bc8e..e4e6cb4d4e5b 100644 > --- a/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml > +++ b/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml > @@ -22,7 +22,9 @@ description: |+ > > properties: > compatible: > - const: raspberrypi,7inch-touchscreen-panel > + enum: > + - raspberrypi,7inch-touchscreen-panel > + - waveshare,7inch-touchscreen-panel > > reg: > const: 0x45 > -- > 2.17.1 >
Hi, Conor On 2023/11/24 20:31, Conor Dooley wrote: > On Fri, Nov 24, 2023 at 06:44:50PM +0800, Shengyang Chen wrote: >> The waveshare 7inch touchscreen panel is a kind of raspberrypi pi >> panel > > Can you be more specific about what "is a kind of rpi panel" means? > Are they using identical chips as controllers or something like that? > Wareshare panel has same i2c slave address and registers address with the original raspberry pi panel. They both use Atmel firmware and they got same reg id. It can be operated by using the driver of raspberry pi driver after some change of the code. So I suppose it may be a kind of raspberry pi panel and discribe it in this way. It's my own judgement. Sorry about that. Maybe just like Dave said, It cloned the behaviour of the raspberri pi panel. I will change the discribtion in next version to not make other confused. By the way, we will try Stefan's method before next version. The method we used in this patch may be abandoned if Stefan's method is verified in our platform. At that time yaml may also be changed to fit new method. >> and it can be drived by panel-raspberrypi-touchscreen.c. >> Add compatible property for it. >> >> Signed-off-by: Keith Zhao <keith.zhao@starfivetech.com> >> Signed-off-by: Shengyang Chen <shengyang.chen@starfivetech.com> >> --- >> .../bindings/display/panel/raspberrypi,7inch-touchscreen.yaml | 4 +++- >> 1 file changed, 3 insertions(+), 1 deletion(-) >> >> diff --git a/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml b/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml >> index 22a083f7bc8e..e4e6cb4d4e5b 100644 >> --- a/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml >> +++ b/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml >> @@ -22,7 +22,9 @@ description: |+ >> >> properties: >> compatible: >> - const: raspberrypi,7inch-touchscreen-panel >> + enum: >> + - raspberrypi,7inch-touchscreen-panel >> + - waveshare,7inch-touchscreen-panel >> >> reg: >> const: 0x45 >> -- >> 2.17.1 >> thanks. Best Regards, Shengyang
On Wed, Dec 06, 2023 at 05:43:48PM +0800, Shengyang Chen wrote: > Hi, Conor > > On 2023/11/24 20:31, Conor Dooley wrote: > > On Fri, Nov 24, 2023 at 06:44:50PM +0800, Shengyang Chen wrote: > >> The waveshare 7inch touchscreen panel is a kind of raspberrypi pi > >> panel > > > > Can you be more specific about what "is a kind of rpi panel" means? > > Are they using identical chips as controllers or something like that? > > > > Wareshare panel has same i2c slave address and registers address with > the original raspberry pi panel. They both use Atmel firmware and they > got same reg id. It can be operated by using the driver of raspberry pi driver > after some change of the code. So I suppose it may be a kind of raspberry pi panel > and discribe it in this way. It's my own judgement. Sorry about that. > Maybe just like Dave said, It cloned the behaviour of the raspberri pi panel. > I will change the discribtion in next version to not make other confused. > > By the way, we will try Stefan's method before next version. > The method we used in this patch may be abandoned if Stefan's method is verified in our platform. > At that time yaml may also be changed to fit new method. I don't know what Stefan's approach is, but I do not think that a bindings patch should be dropped. The waveshare might be a clone, but it is a distinct device. If the same driver can control both, then the compatible setups that should be permitted are: compatible = "raspberrypi,7inch-touchscreen-panel"; and compatible = "waveshare,7inch-touchscreen-panel", "raspberrypi,7inch-touchscreen-panel"; Cheers, Conor. > >> and it can be drived by panel-raspberrypi-touchscreen.c. > >> Add compatible property for it. > >> > >> Signed-off-by: Keith Zhao <keith.zhao@starfivetech.com> > >> Signed-off-by: Shengyang Chen <shengyang.chen@starfivetech.com> > >> --- > >> .../bindings/display/panel/raspberrypi,7inch-touchscreen.yaml | 4 +++- > >> 1 file changed, 3 insertions(+), 1 deletion(-) > >> > >> diff --git a/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml b/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml > >> index 22a083f7bc8e..e4e6cb4d4e5b 100644 > >> --- a/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml > >> +++ b/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml > >> @@ -22,7 +22,9 @@ description: |+ > >> > >> properties: > >> compatible: > >> - const: raspberrypi,7inch-touchscreen-panel > >> + enum: > >> + - raspberrypi,7inch-touchscreen-panel > >> + - waveshare,7inch-touchscreen-panel > >> > >> reg: > >> const: 0x45 > >> -- > >> 2.17.1 > >> > > > thanks. > > Best Regards, > Shengyang >
Hi, Conor thanks for comment On 2023/12/6 23:40, Conor Dooley wrote: > On Wed, Dec 06, 2023 at 05:43:48PM +0800, Shengyang Chen wrote: >> Hi, Conor >> >> On 2023/11/24 20:31, Conor Dooley wrote: >> > On Fri, Nov 24, 2023 at 06:44:50PM +0800, Shengyang Chen wrote: >> >> The waveshare 7inch touchscreen panel is a kind of raspberrypi pi >> >> panel >> > >> > Can you be more specific about what "is a kind of rpi panel" means? >> > Are they using identical chips as controllers or something like that? >> > >> >> Wareshare panel has same i2c slave address and registers address with >> the original raspberry pi panel. They both use Atmel firmware and they >> got same reg id. It can be operated by using the driver of raspberry pi driver >> after some change of the code. So I suppose it may be a kind of raspberry pi panel >> and discribe it in this way. It's my own judgement. Sorry about that. >> Maybe just like Dave said, It cloned the behaviour of the raspberri pi panel. >> I will change the discribtion in next version to not make other confused. >> >> By the way, we will try Stefan's method before next version. >> The method we used in this patch may be abandoned if Stefan's method is verified in our platform. >> At that time yaml may also be changed to fit new method. > > I don't know what Stefan's approach is, but I do not think that a > bindings patch should be dropped. The waveshare might be a clone, but it > is a distinct device. If the same driver can control both, then the > compatible setups that should be permitted are: > compatible = "raspberrypi,7inch-touchscreen-panel"; > and > compatible = "waveshare,7inch-touchscreen-panel", "raspberrypi,7inch-touchscreen-panel"; > > Cheers, > Conor. > Here is our consideration of this submit: Although Waveshare panel reuse the driver of raspberry pi panel, they are different in probing process and panel parameters. we try to use compatible and data to distinguish these two panel Here are the reference driver part: https://elixir.bootlin.com/linux/v6.7-rc3/source/drivers/gpu/drm/panel/panel-simple.c dt-binding part: https://elixir.bootlin.com/linux/v6.7-rc3/source/Documentation/devicetree/bindings/display/panel/panel-simple.yaml For example: in driver part: in drivers/gpu/drm/panel/panel-simple.c:#in line 4189 ---------------------------------------------------------------------------------- we can got different compatible with its own data. ================================================ static const struct of_device_id platform_of_match[] = { //the of_match array list { .compatible = "ampire,am-1280800n3tzqw-t00h", .data = &ire_am_1280800n3tzqw_t00h, //we define our panel parameter or special panel function, which can distinguish different panels }, { .compatible = "ampire,am-480272h3tmqw-t01h", .data = &ire_am_480272h3tmqw_t01h, }, ... ... } =============================================== in drivers/gpu/drm/panel/panel-simple.c:#in line 4611 ---------------------------------------------------------------------------------- we can use the generic probing process to probe our driver after getting its own data. ================================================ static int panel_simple_platform_probe(struct platform_device *pdev) { const struct panel_desc *desc; desc = of_device_get_match_data(&pdev->dev); //we get our panel parameter if (!desc) return -ENODEV; return panel_simple_probe(&pdev->dev, desc); //probe with returned data } ================================================ in yamel part: in /Documentation/devicetree/bindings/display/panel/panel-simple.yaml#in line 33 ---------------------------------------------------------------------------------- We refer to this approach, adding our compatible to the yaml of raspberry pi panel ================================================ properties: compatible: enum: # compatible must be listed in alphabetical order, ordered by compatible. # The description in the comment is mandatory for each compatible. # Ampire AM-1280800N3TZQW-T00H 10.1" WQVGA TFT LCD panel - ampire,am-1280800n3tzqw-t00h # Ampire AM-480272H3TMQW-T01H 4.3" WQVGA TFT LCD panel - ampire,am-480272h3tmqw-t01h ================================================ If we use Stenfan's method, we can reuse the code of panel-simple.c we may submit our patch to /Documentation/devicetree/bindings/display/panel/panel-simple.yaml /drivers/gpu/drm/panel/panel-simple.c as a new panel porting. That may less confuse. here is Stenfan's method: [1] - https://github.com/lategoodbye/rpi-zero/commits/v6.7-7inch-ts [2] - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/arm64/boot/dts/freescale/imx8mm-venice-gw72xx-0x-rpidsi.dtso?h=v6.6.2&id=6b4da1354fd81adace0cda448c77d8f2a47d8474 Thanks Best Regards, Shengyang >> >> and it can be drived by panel-raspberrypi-touchscreen.c. >> >> Add compatible property for it. >> >> >> >> Signed-off-by: Keith Zhao <keith.zhao@starfivetech.com> >> >> Signed-off-by: Shengyang Chen <shengyang.chen@starfivetech.com> >> >> --- >> >> .../bindings/display/panel/raspberrypi,7inch-touchscreen.yaml | 4 +++- >> >> 1 file changed, 3 insertions(+), 1 deletion(-) >> >> >> >> diff --git a/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml b/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml >> >> index 22a083f7bc8e..e4e6cb4d4e5b 100644 >> >> --- a/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml >> >> +++ b/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml >> >> @@ -22,7 +22,9 @@ description: |+ >> >> >> >> properties: >> >> compatible: >> >> - const: raspberrypi,7inch-touchscreen-panel >> >> + enum: >> >> + - raspberrypi,7inch-touchscreen-panel >> >> + - waveshare,7inch-touchscreen-panel >> >> >> >> reg: >> >> const: 0x45 >> >> -- >> >> 2.17.1 >> >> >> >> >> thanks. >> >> Best Regards, >> Shengyang >>
On Thu, Dec 07, 2023 at 11:48:56AM +0800, Shengyang Chen wrote: > Hi, Conor > > thanks for comment > > On 2023/12/6 23:40, Conor Dooley wrote: > > On Wed, Dec 06, 2023 at 05:43:48PM +0800, Shengyang Chen wrote: > >> Hi, Conor > >> > >> On 2023/11/24 20:31, Conor Dooley wrote: > >> > On Fri, Nov 24, 2023 at 06:44:50PM +0800, Shengyang Chen wrote: > >> >> The waveshare 7inch touchscreen panel is a kind of raspberrypi pi > >> >> panel > >> > > >> > Can you be more specific about what "is a kind of rpi panel" means? > >> > Are they using identical chips as controllers or something like that? > >> > > >> > >> Wareshare panel has same i2c slave address and registers address with > >> the original raspberry pi panel. They both use Atmel firmware and they > >> got same reg id. It can be operated by using the driver of raspberry pi driver > >> after some change of the code. So I suppose it may be a kind of raspberry pi panel > >> and discribe it in this way. It's my own judgement. Sorry about that. > >> Maybe just like Dave said, It cloned the behaviour of the raspberri pi panel. > >> I will change the discribtion in next version to not make other confused. > >> > >> By the way, we will try Stefan's method before next version. > >> The method we used in this patch may be abandoned if Stefan's method is verified in our platform. > >> At that time yaml may also be changed to fit new method. > > > > I don't know what Stefan's approach is, but I do not think that a > > bindings patch should be dropped. The waveshare might be a clone, but it > > is a distinct device. If the same driver can control both, then the > > compatible setups that should be permitted are: > > compatible = "raspberrypi,7inch-touchscreen-panel"; > > and > > compatible = "waveshare,7inch-touchscreen-panel", "raspberrypi,7inch-touchscreen-panel"; > If we use Stenfan's method, we can reuse the code of panel-simple.c > we may submit our patch to > /Documentation/devicetree/bindings/display/panel/panel-simple.yaml > /drivers/gpu/drm/panel/panel-simple.c > as a new panel porting. That may less confuse. As long as you provide a specific compatible, and not re-use the rpi one, that's fine. It just sounded like you were intending to reuse that here, but from this message it seems like I misunderstood. Thanks, Conor.
diff --git a/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml b/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml index 22a083f7bc8e..e4e6cb4d4e5b 100644 --- a/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml +++ b/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml @@ -22,7 +22,9 @@ description: |+ properties: compatible: - const: raspberrypi,7inch-touchscreen-panel + enum: + - raspberrypi,7inch-touchscreen-panel + - waveshare,7inch-touchscreen-panel reg: const: 0x45