From: Conor Dooley <conor.dooley@microchip.com>
To: Shengyang Chen <shengyang.chen@starfivetech.com>
Cc: Conor Dooley <conor@kernel.org>, <devicetree@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>, <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>, <jack.zhu@starfivetech.com>,
<linux-rpi-kernel@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/2] dt-bindings: display: panel: raspberrypi: Add compatible property for waveshare 7inch touchscreen panel
Date: Thu, 7 Dec 2023 09:34:59 +0000 [thread overview]
Message-ID: <20231207-dullness-deprive-ece2d47ff69d@wendy> (raw)
In-Reply-To: <53b992e8-1b36-4540-a993-fde8e550faf9@starfivetech.com>
[-- Attachment #1.1: Type: text/plain, Size: 2371 bytes --]
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.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor.dooley@microchip.com>
To: Shengyang Chen <shengyang.chen@starfivetech.com>
Cc: Conor Dooley <conor@kernel.org>, <devicetree@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>, <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>, <jack.zhu@starfivetech.com>,
<linux-rpi-kernel@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/2] dt-bindings: display: panel: raspberrypi: Add compatible property for waveshare 7inch touchscreen panel
Date: Thu, 7 Dec 2023 09:34:59 +0000 [thread overview]
Message-ID: <20231207-dullness-deprive-ece2d47ff69d@wendy> (raw)
In-Reply-To: <53b992e8-1b36-4540-a993-fde8e550faf9@starfivetech.com>
[-- Attachment #1: Type: text/plain, Size: 2371 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor.dooley@microchip.com>
To: Shengyang Chen <shengyang.chen@starfivetech.com>
Cc: dri-devel@lists.freedesktop.org, eric@anholt.net,
thierry.reding@gmail.com, krzysztof.kozlowski+dt@linaro.org,
florian.fainelli@broadcom.com, sam@ravnborg.org,
bcm-kernel-feedback-list@broadcom.com, quic_jesszhan@quicinc.com,
devicetree@vger.kernel.org, conor+dt@kernel.org,
mripard@kernel.org, robh+dt@kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, neil.armstrong@linaro.org,
keith.zhao@starfivetech.com, linux-kernel@vger.kernel.org,
Conor Dooley <conor@kernel.org>,
jack.zhu@starfivetech.com, tzimmermann@suse.de,
changhuang.liang@starfivetech.com
Subject: Re: [PATCH v1 1/2] dt-bindings: display: panel: raspberrypi: Add compatible property for waveshare 7inch touchscreen panel
Date: Thu, 7 Dec 2023 09:34:59 +0000 [thread overview]
Message-ID: <20231207-dullness-deprive-ece2d47ff69d@wendy> (raw)
In-Reply-To: <53b992e8-1b36-4540-a993-fde8e550faf9@starfivetech.com>
[-- Attachment #1: Type: text/plain, Size: 2371 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-12-07 9:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 10:44 [PATCH v1 0/2] Add waveshare 7inch touchscreen panel support Shengyang Chen
2023-11-24 10:44 ` Shengyang Chen
2023-11-24 10:44 ` Shengyang Chen
2023-11-24 10:44 ` [PATCH v1 1/2] dt-bindings: display: panel: raspberrypi: Add compatible property for waveshare 7inch touchscreen panel Shengyang Chen
2023-11-24 10:44 ` Shengyang Chen
2023-11-24 10:44 ` Shengyang Chen
2023-11-24 12:31 ` Conor Dooley
2023-11-24 12:31 ` Conor Dooley
2023-11-24 12:31 ` Conor Dooley
2023-12-06 9:43 ` Shengyang Chen
2023-12-06 9:43 ` Shengyang Chen
2023-12-06 9:43 ` Shengyang Chen
2023-12-06 15:40 ` Conor Dooley
2023-12-06 15:40 ` Conor Dooley
2023-12-06 15:40 ` Conor Dooley
2023-12-07 3:48 ` Shengyang Chen
2023-12-07 3:48 ` Shengyang Chen
2023-12-07 3:48 ` Shengyang Chen
2023-12-07 9:34 ` Conor Dooley [this message]
2023-12-07 9:34 ` Conor Dooley
2023-12-07 9:34 ` Conor Dooley
2023-11-24 10:44 ` [PATCH v1 2/2] gpu: drm: panel: raspberrypi: add new display mode and new probing process Shengyang Chen
2023-11-24 10:44 ` Shengyang Chen
2023-11-24 10:44 ` Shengyang Chen
2023-11-24 14:54 ` [PATCH v1 0/2] Add waveshare 7inch touchscreen panel support Stefan Wahren
2023-11-24 14:54 ` Stefan Wahren
2023-11-24 14:54 ` Stefan Wahren
2023-11-24 16:04 ` Dave Stevenson
2023-11-24 16:04 ` Dave Stevenson
2023-11-24 16:04 ` Dave Stevenson
2023-12-06 8:55 ` Keith Zhao
2023-12-06 8:55 ` Keith Zhao
2023-12-06 8:55 ` Keith Zhao
2023-12-06 14:56 ` Dave Stevenson
2023-12-06 14:56 ` Dave Stevenson
2023-12-06 14:56 ` Dave Stevenson
2023-12-07 2:16 ` Keith Zhao
2023-12-07 2:16 ` Keith Zhao
2023-12-07 2:16 ` Keith Zhao
2023-12-06 9:53 ` Shengyang Chen
2023-12-06 9:53 ` Shengyang Chen
2023-12-06 9:53 ` Shengyang Chen
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=20231207-dullness-deprive-ece2d47ff69d@wendy \
--to=conor.dooley@microchip.com \
--cc=airlied@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=florian.fainelli@broadcom.com \
--cc=jack.zhu@starfivetech.com \
--cc=keith.zhao@starfivetech.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=shengyang.chen@starfivetech.com \
--cc=thierry.reding@gmail.com \
--cc=tzimmermann@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.