From: Archit Taneja <architt@codeaurora.org>
To: Philippe CORNU <philippe.cornu@st.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
Thierry Reding <thierry.reding@gmail.com>,
David Airlie <airlied@linux.ie>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Yannick FERTRE <yannick.fertre@st.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"kernel@stlinux.com" <kernel@stlinux.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Fabien DESSENNE <fabien.dessenne@st.com>,
Mickael REULIER <mickael.reulier@st.com>,
Vincent ABRIOU <vincent.abriou@st.com>,
Gabriel FERNANDEZ <gabriel.fernandez@st.com>,
Ludovic BARRE <ludovic.barre@st.com>
Subject: Re: [PATCH v1 3/3] drm/stm: Add STM32 DSI host driver
Date: Tue, 16 May 2017 13:43:20 +0530 [thread overview]
Message-ID: <f8043f78-905f-c3cb-fe42-be58981cdaf6@codeaurora.org> (raw)
In-Reply-To: <250fc42c-8961-c57e-6f59-9b1a6523a0a4@st.com>
Hi,
On 05/15/2017 04:03 PM, Philippe CORNU wrote:
> Hi Neil,
> Many thanks for your comments.
>
> The PHY part of the MIPI DSI is the main difference between all chipsets
> based on the Synopsys DesignWare MIPI DSI.
> There is no "generic DSI PHY interface" and that is probably why all soc
> vendors have implemented their own drivers (RockChip, NXP/Freescale,
> HiSilicon and now STM32).
We don't really need a generic DSI PHY interface to ensure we use a common
bridge driver. We need to do what's been done in the DW HDMI bridge driver.
The dw_hdmi_plat_data struct contains phy ops, which can be used to abstract
vendor PHYs.
>
> Regarding creating a "generic dw MIPI DSI bridge" as the recent dw hdmi
> bridge, several attempts have been done in the past but without success:
> * Liu Ying from Freescale in February 2015
> (https://lkml.org/lkml/2015/2/12/38).
> * Chris Zhong from Rockchip in November 2015
> (http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1024586.html).
We can't have 3 almost identical DW MIPI DSI implementations in the kernel.
You'll need to separate out the vendor specific PHY pieces into ops (like
it's done in the DW HDMI) and post a bridge driver for this.
You don't need to convert the existing rockhip and hisilicon implementations
into bridge drivers. We can CC the authors of the rockchip and hisil so that
they can adapt to the bridge driver too.
Thanks,
Archit
>
> The Rockchip driver looks nice and is updated regularly.
> So, instead of creating a new driver for the STM32 family, we decided to
> use Rockchip’s in our own drm/stm directory and replace the
> Rockchip-specific PHY by the STM32.
>
> Comments are welcome :-)
> Many thanks,
> Philippe
>
>
> On 05/15/2017 10:22 AM, Neil Armstrong wrote:
>> On 05/12/2017 04:56 PM, Philippe CORNU wrote:
>>> This mipi dsi host driver is based on the Rockchip version of the
>>> Synopsys Designware mipi dsi driver (rockchip/dw-mipi-dsi.c)
>>> modified for the stm32 family:
>>> - replace Rockchip digital & phy specific extensions with stm32's ones.
>>> - add a bridge
>>>
>>> Signed-off-by: Philippe CORNU <philippe.cornu@st.com>
>>> ---
>>> drivers/gpu/drm/stm/Kconfig | 7 +
>>> drivers/gpu/drm/stm/Makefile | 2 +
>>> drivers/gpu/drm/stm/dw-mipi-dsi.c | 1197 +++++++++++++++++++++++++++++++++++++
>>> 3 files changed, 1206 insertions(+)
>>> create mode 100644 drivers/gpu/drm/stm/dw-mipi-dsi.c
>>>
>>> diff --git a/drivers/gpu/drm/stm/Kconfig b/drivers/gpu/drm/stm/Kconfig
>>> index 2c4817f..0007789 100644
>>> --- a/drivers/gpu/drm/stm/Kconfig
>>> +++ b/drivers/gpu/drm/stm/Kconfig
>>> @@ -14,3 +14,10 @@ config DRM_STM
>>> STMicroelectronics STM32 MCUs.
>>> To compile this driver as a module, choose M here: the module
>>> will be called stm-drm.
>>> +
>>> +config DRM_STM_DSI
>>> + tristate "MIPI DSI support for STMicroelectronics SoC"
>>> + depends on DRM_STM
>>> + select DRM_MIPI_DSI
>>> + help
>>> + Choose this option for MIPI DSI support on STMicroelectronics SoC.
>>> diff --git a/drivers/gpu/drm/stm/Makefile b/drivers/gpu/drm/stm/Makefile
>>> index e114d45..e448a93 100644
>>> --- a/drivers/gpu/drm/stm/Makefile
>>> +++ b/drivers/gpu/drm/stm/Makefile
>>> @@ -4,4 +4,6 @@ stm-drm-y := \
>>> drv.o \
>>> ltdc.o
>>>
>>> +obj-$(CONFIG_DRM_STM_DSI) += dw-mipi-dsi.o
>>> +
>>> obj-$(CONFIG_DRM_STM) += stm-drm.o
>>> diff --git a/drivers/gpu/drm/stm/dw-mipi-dsi.c b/drivers/gpu/drm/stm/dw-mipi-dsi.c
>>> new file mode 100644
>>> index 0000000..4b7f7b9
>>> --- /dev/null
>>> +++ b/drivers/gpu/drm/stm/dw-mipi-dsi.c
>>
>>
>> Hi Philippe,
>>
>> First question, why couldn't this be transformed as a bridge driver along the Synopsys DW-HDMI driver ?
>>
>> Neil
>>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-05-16 8:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 14:56 [PATCH v1 0/3] STM32 DSI HOST Philippe CORNU
2017-05-12 14:56 ` [PATCH v1 1/3] drm/stm: ltdc: Add bridge support Philippe CORNU
[not found] ` <1494600989-13507-2-git-send-email-philippe.cornu-qxv4g6HH51o@public.gmane.org>
2017-05-18 18:31 ` Eric Anholt
2017-05-12 14:56 ` [PATCH v1 2/3] dt-bindings: display: Add STM32 DSI host driver Philippe CORNU
[not found] ` <1494600989-13507-3-git-send-email-philippe.cornu-qxv4g6HH51o@public.gmane.org>
2017-05-18 21:42 ` Rob Herring
2017-05-19 16:25 ` Philippe CORNU
2017-05-22 12:58 ` Rob Herring
2017-05-12 14:56 ` [PATCH v1 3/3] drm/stm: " Philippe CORNU
2017-05-15 8:22 ` Neil Armstrong
2017-05-15 10:33 ` Philippe CORNU
2017-05-15 14:38 ` Neil Armstrong
2017-05-16 8:13 ` Archit Taneja [this message]
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=f8043f78-905f-c3cb-fe42-be58981cdaf6@codeaurora.org \
--to=architt@codeaurora.org \
--cc=airlied@linux.ie \
--cc=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=benjamin.gaignard@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabien.dessenne@st.com \
--cc=gabriel.fernandez@st.com \
--cc=kernel@stlinux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=ludovic.barre@st.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mickael.reulier@st.com \
--cc=narmstrong@baylibre.com \
--cc=philippe.cornu@st.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vincent.abriou@st.com \
--cc=yannick.fertre@st.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;
as well as URLs for NNTP newsgroup(s).