From: <Manikandan.M@microchip.com>
To: <dmitry.baryshkov@linaro.org>, <mripard@kernel.org>
Cc: <neil.armstrong@linaro.org>, <quic_jesszhan@quicinc.com>,
<airlied@gmail.com>, <simona@ffwll.ch>,
<maarten.lankhorst@linux.intel.com>, <tzimmermann@suse.de>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<thierry.reding@gmail.com>, <sam@ravnborg.org>,
<dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <Dharma.B@microchip.com>
Subject: Re: [PATCH v2 2/2] drm/panel: simple: Add Microchip AC69T88A LVDS Display panel
Date: Tue, 1 Oct 2024 09:33:31 +0000 [thread overview]
Message-ID: <9a5e3ed8-b7fd-4c1b-b0da-2c047ace0af7@microchip.com> (raw)
In-Reply-To: <aehcvf55b52p6u5ai3uri7jzo2dywdhv6mxo4pxz3lhajjoxqe@izk23gt2yvdn>
On 27/09/24 4:51 am, Dmitry Baryshkov wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Thu, Sep 26, 2024 at 03:58:11PM GMT, Maxime Ripard wrote:
>> On Thu, Sep 26, 2024 at 04:32:59PM GMT, Dmitry Baryshkov wrote:
>>> On Thu, Sep 26, 2024 at 08:17:09AM GMT, Manikandan.M@microchip.com wrote:
>>>> On 23/09/24 11:37 am, Dmitry Baryshkov wrote:
>>>>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>>>>
>>>>> On Mon, Sep 23, 2024 at 05:50:22AM GMT, Manikandan.M@microchip.com wrote:
>>>>>> On 20/09/24 9:13 pm, Dmitry Baryshkov wrote:
>>>>>>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>>>>>>
>>>>>>> On Thu, Sep 19, 2024 at 02:45:48PM GMT, Manikandan Muralidharan wrote:
>>>>>>>> Add support for Microchip AC69T88A 5 inch TFT LCD 800x480
>>>>>>>> Display module with LVDS interface.The panel uses the Sitronix
>>>>>>>> ST7262 800x480 Display driver
>>>>>>>
>>>>>>> AC69T88A seems to be a module name, rather than a panel name. What is
>>>>>>> the actual panel name present on this module?
>>>>>> Both names, "Microchip AC69T88A" and "MPU32-LVDS-DISPLAY-WVGA" are
>>>>>> present on the display module
>>>>>
>>>>> Which panel was used for the module? I don't think that Microchip
>>>>> produces LVDS panels.
>>>> Its a new LVDS display from Microchip that uses Sitronix ST7262 TFT LCD
>>>> driver
>>>>
>>>> https://www.crystalfontz.com/controllers/datasheet-viewer.php?id=486
>>>
>>> Ok. Anyway if somebody ends up looking for the panel, they'll probably
>>> find the module and vice versa.
>>>
>>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>>
>> Given that aside from that mail, the module name isn't mentionned
>> anywhere, I'm not sure they would.
>>
>> The way we usually deal with controllers is to have a separate driver
>> for panels based on that controller, even more so since that controller
>> seems to be able to affect the display.
>
> But in this case it's panel-simple, no special driver for the
> controller. From my understanding the AC69T88A is the module name (at
> least the datasheet uses that name). The on-board EEPROM also carries
> that name and the name of the controller.
Yes, as per the proposed on-board EEPROM spec, it holds the module name
and the LCD driver used.
>
> --
> With best wishes
> Dmitry
--
Thanks and Regards,
Manikandan M.
next prev parent reply other threads:[~2024-10-01 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 9:15 [PATCH v2 1/2] dt-bindings: display: panel-simple: Document support for Microchip AC69T88A Manikandan Muralidharan
2024-09-19 9:15 ` [PATCH v2 2/2] drm/panel: simple: Add Microchip AC69T88A LVDS Display panel Manikandan Muralidharan
2024-09-20 15:43 ` Dmitry Baryshkov
2024-09-23 5:50 ` Manikandan.M
2024-09-23 6:07 ` Dmitry Baryshkov
2024-09-26 8:17 ` Manikandan.M
2024-09-26 13:32 ` Dmitry Baryshkov
2024-09-26 13:58 ` Maxime Ripard
2024-09-26 23:21 ` Dmitry Baryshkov
2024-10-01 9:33 ` Manikandan.M [this message]
2024-09-21 0:56 ` [PATCH v2 1/2] dt-bindings: display: panel-simple: Document support for Microchip AC69T88A Rob Herring (Arm)
2024-10-19 14:57 ` Dmitry Baryshkov
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=9a5e3ed8-b7fd-4c1b-b0da-2c047ace0af7@microchip.com \
--to=manikandan.m@microchip.com \
--cc=Dharma.B@microchip.com \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--cc=robh@kernel.org \
--cc=sam@ravnborg.org \
--cc=simona@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®