From: Liu Ying <victor.liu@nxp.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Joseph Guo <qijian.guo@nxp.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jessica Zhang <quic_jesszhan@quicinc.com>,
Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] drm: bridge: Add waveshare DSI2DPI unit driver
Date: Tue, 5 Aug 2025 14:30:35 +0800 [thread overview]
Message-ID: <dcbcb017-e25b-4244-8ad3-9c07da99c253@nxp.com> (raw)
In-Reply-To: <e52b3630-5846-49ac-9abf-3b42e1d585f4@kernel.org>
On 08/05/2025, Krzysztof Kozlowski wrote:
> On 05/08/2025 08:11, Liu Ying wrote:
>> On 08/05/2025, Krzysztof Kozlowski wrote:
>>> On 05/08/2025 04:22, Liu Ying wrote:
>>>> Hi Joseph,
>>>>
>>>> On 08/04/2025, Joseph Guo wrote:
>>>>> Waveshare touchscreen consists of a DPI panel and a driver board.
>>>>> The waveshare driver board consists of ICN6211 and a MCU to
>>>>> convert DSI to DPI and control the backlight.
>>>>> This driver treats the MCU and ICN6211 board as a whole unit.
>>>>> It can support all resolution waveshare DSI2DPI based panel,
>>>>> the timing table should come from 'panel-dpi' panel in the device tree.
>>>>>
>>>>> Signed-off-by: Joseph Guo <qijian.guo@nxp.com>
>>>>
>>>> For next version, you may add:
>>>> Suggested-by: Liu Ying <victor.liu@nxp.com>
>>>
>>> Why?
>>
>> As I replied in the cover letter, I provided general idea for this
>> patch series in NXP down stream kernel. Same for the DT binding patches.
>
> General idea to add support for new driver? So like every patch being a
> result of for example task from manager means "Suggested-by"? Since when
> new device support is treated as suggested-by?
Not for new driver, but for architecture level, like treating the MCU and
ICN6211 as a whole unit/DRM bridge and treating the DPI panel as a simple
panel from both DT's point of view and DRM driver's point of view.
>
> I also do not understand how downstream kernel is relevant here.
That suggestion did happen when I reviewed this patch series for downstream
kernel. Just shared the information.
>
> Best regards,
> Krzysztof
--
Regards,
Liu Ying
next prev parent reply other threads:[~2025-08-05 6:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 2:07 [PATCH v2 0/3] Add support for Waveshare DSI2DPI unit Joseph Guo
2025-08-04 2:07 ` [PATCH v2 1/3] dt-bindings: display: bridge: Add waveshare DSI2DPI unit support Joseph Guo
2025-08-05 1:53 ` Liu Ying
2025-08-04 2:07 ` [PATCH v2 2/3] dt-bindings: display: panel: Add waveshare DPI panel support Joseph Guo
2025-08-05 1:54 ` Liu Ying
2025-08-05 6:00 ` Krzysztof Kozlowski
2025-08-05 5:59 ` Krzysztof Kozlowski
2025-08-05 6:48 ` Liu Ying
2025-08-04 2:07 ` [PATCH v2 3/3] drm: bridge: Add waveshare DSI2DPI unit driver Joseph Guo
2025-08-04 15:38 ` Neil Armstrong
2025-08-05 2:22 ` Liu Ying
2025-08-05 2:23 ` Joseph Guo
2025-08-05 6:00 ` Krzysztof Kozlowski
2025-08-05 6:11 ` Liu Ying
2025-08-05 6:18 ` Krzysztof Kozlowski
2025-08-05 6:30 ` Liu Ying [this message]
2025-08-05 2:46 ` Liu Ying
2025-08-05 3:34 ` Liu Ying
2025-08-05 1:49 ` [PATCH v2 0/3] Add support for Waveshare DSI2DPI unit Liu Ying
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=dcbcb017-e25b-4244-8ad3-9c07da99c253@nxp.com \
--to=victor.liu@nxp.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=qijian.guo@nxp.com \
--cc=quic_jesszhan@quicinc.com \
--cc=rfoss@kernel.org \
--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