Re: 答复: [PATCH v2 6/6] drm/panel: Add Ilitek ILI9341 DBI panel driver
On 07/09/2020 14:57, Paul Cercueil wrote: > > > Le dim. 30 août 2020 à 22:28, Sam Ravnborg a écrit : >> Hi Laurent. >> >>> > >>> > Please read the cover letter, it explains why it's done this way. The >>> > whole point of this patchset is to merge DSI and DBI frameworks in a >>> > way that can be maintained. >>> >>> I think this proves the point that the proposed naming is confusing. At >>> least a rename would be required. >> >> Do you have any inputs on the amount of rename we are looking into. >> Is this a simple s/struct mipi_dsi_device/struct mipi_dxi_device/ >> or something more? >> >> We should script the rename as it will tocuh a lot of files, >> and without a script we would chase this. But once it is scripted >> it would be trivial to perform. >> >> I did not look at this enough, but I had an idea that we >> would have do to a s/dsi/dxi/ in a lot of places. >> >> (dxi is my best proposal at the moment for something covering both dsi >> and dbi). > > dcs? > > Since DBI and DSI panels generally all use DCS commands. mipi_disp / mipi_display ? since it's all about mipi display interfaces with different transport protocols. Neil > > -Paul > > > ___ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: 答复: [PATCH v2 6/6] drm/panel: Add Ilitek ILI9341 DBI panel driver
Le dim. 30 août 2020 à 22:28, Sam Ravnborg a écrit : Hi Laurent. > > Please read the cover letter, it explains why it's done this way. The > whole point of this patchset is to merge DSI and DBI frameworks in a > way that can be maintained. I think this proves the point that the proposed naming is confusing. At least a rename would be required. Do you have any inputs on the amount of rename we are looking into. Is this a simple s/struct mipi_dsi_device/struct mipi_dxi_device/ or something more? We should script the rename as it will tocuh a lot of files, and without a script we would chase this. But once it is scripted it would be trivial to perform. I did not look at this enough, but I had an idea that we would have do to a s/dsi/dxi/ in a lot of places. (dxi is my best proposal at the moment for something covering both dsi and dbi). dcs? Since DBI and DSI panels generally all use DCS commands. -Paul ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: 答复: [PATCH v2 6/6] drm/panel: Add Ilitek ILI9341 DBI panel driver
Hi Leon,
Le dim. 30 août 2020 à 16:36, 何小龙 (Leon He)
a écrit :
+struct ili9341 {
+ struct drm_panel panel;
+ struct mipi_dsi_device *dsi;
+ const struct ili9341_pdata *pdata;
+
+ struct gpio_desc*reset_gpiod;
+ u32 rotation;
+};
+
Hi Paul, you put the mipi_dsi_device inside the struct. I think it
maybe not
a good idea. That means the panel has a MIPI-DSI interface but it
doesn't
have actually.
+static int ili9341_probe(struct mipi_dsi_device *dsi)
+{
+ struct device *dev = >dev;
+ struct ili9341 *priv;
+ int ret;
+
+ /* See comment for mipi_dbi_spi_init() */
+ if (!dev->coherent_dma_mask) {
+ ret = dma_coerce_mask_and_coherent(dev,
DMA_BIT_MASK(32));
+ if (ret) {
+ dev_warn(dev, "Failed to set dma mask
%d\n", ret);
+ return ret;
+ }
+ }
+
+ priv = devm_kzalloc(dev, sizeof(*priv), GFP_KERNEL);
+ if (!priv)
+ return -ENOMEM;
+
+ mipi_dsi_set_drvdata(dsi, priv);
+ priv->dsi = dsi;
+
+ device_property_read_u32(dev, "rotation", >rotation);
+
+ priv->pdata = device_get_match_data(dev);
+ if (!priv->pdata)
+ return -EINVAL;
+
+ drm_panel_init(>panel, dev, _funcs,
+ DRM_MODE_CONNECTOR_DPI);
+
+ priv->reset_gpiod = devm_gpiod_get(dev, "reset",
GPIOD_OUT_HIGH);
+ if (IS_ERR(priv->reset_gpiod)) {
+ dev_err(dev, "Couldn't get our reset GPIO\n");
+ return PTR_ERR(priv->reset_gpiod);
+ }
+
+ ret = drm_panel_of_backlight(>panel);
+ if (ret < 0) {
+ if (ret != -EPROBE_DEFER)
+ dev_err(dev, "Failed to get backlight
handle\n");
+ return ret;
+ }
+
+ drm_panel_add(>panel);
+
+ dsi->bus_type = priv->pdata->bus_type;
+ dsi->lanes = priv->pdata->lanes;
+ dsi->format = MIPI_DSI_FMT_RGB565;
+
+ ret = mipi_dsi_attach(dsi);
+ if (ret) {
+ dev_err(dev, "Failed to attach DSI panel\n");
+ goto err_panel_remove;
+ }
+
+ ret = mipi_dsi_maybe_register_tiny_driver(dsi);
+ if (ret) {
+ dev_err(dev, "Failed to init TinyDRM driver\n");
+ goto err_mipi_dsi_detach;
+ }
+
+ return 0;
+
+err_mipi_dsi_detach:
+ mipi_dsi_detach(dsi);
+err_panel_remove:
+ drm_panel_remove(>panel);
+ return ret;
+}
+
+static int ili9341_remove(struct mipi_dsi_device *dsi)
+{
+ struct ili9341 *priv = mipi_dsi_get_drvdata(dsi);
+
+ mipi_dsi_detach(dsi);
+ drm_panel_remove(>panel);
+
+ drm_panel_disable(>panel);
+ drm_panel_unprepare(>panel);
+
+ return 0;
+}
+
+static const struct ili9341_pdata yx240qv29_pdata = {
+ .mode = { DRM_SIMPLE_MODE(240, 320, 37, 49) },
+ .width_mm = 0, // TODO
+ .height_mm = 0, // TODO
+ .bus_type = MIPI_DCS_BUS_TYPE_DBI_SPI_C3,
+ .lanes = 1,
+};
+
+static const struct of_device_id ili9341_of_match[] = {
+ { .compatible = "adafruit,yx240qv29", .data =
_pdata },
+ { }
+};
+MODULE_DEVICE_TABLE(of, ili9341_of_match);
+
+static struct mipi_dsi_driver ili9341_dsi_driver = {
+ .probe = ili9341_probe,
+ .remove = ili9341_remove,
+ .driver = {
+ .name = "ili9341-dsi",
+ .of_match_table = ili9341_of_match,
+ },
+};
+module_mipi_dsi_driver(ili9341_dsi_driver);
Again, you treat this driver as a mipi dsi driver but for a MIPI-DBI
(I8080/SPI)
panel device. That will make developers confused.
Is it possible to just add a mipi_dbi_driver for I8080/SPI interface
panel?
Thanks!
Please read the cover letter, it explains why it's done this way. The
whole point of this patchset is to merge DSI and DBI frameworks in a
way that can be maintained.
Cheers,
-Paul
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: 答复: [PATCH v2 6/6] drm/panel: Add Ilitek ILI9341 DBI panel driver
Hi Laurent. > > > > Please read the cover letter, it explains why it's done this way. The > > whole point of this patchset is to merge DSI and DBI frameworks in a > > way that can be maintained. > > I think this proves the point that the proposed naming is confusing. At > least a rename would be required. Do you have any inputs on the amount of rename we are looking into. Is this a simple s/struct mipi_dsi_device/struct mipi_dxi_device/ or something more? We should script the rename as it will tocuh a lot of files, and without a script we would chase this. But once it is scripted it would be trivial to perform. I did not look at this enough, but I had an idea that we would have do to a s/dsi/dxi/ in a lot of places. (dxi is my best proposal at the moment for something covering both dsi and dbi). PS. I am travelling for a few days, so do not expect quick responses. Sam ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: 答复: [PATCH v2 6/6] drm/panel: Add Ilitek ILI9341 DBI panel driver
Hi Paul,
On Sun, Aug 30, 2020 at 06:48:12PM +0200, Paul Cercueil wrote:
> Le dim. 30 août 2020 à 16:36, 何小龙 (Leon He) a écrit :
> >> +struct ili9341 {
> >> + struct drm_panel panel;
> >> + struct mipi_dsi_device *dsi;
> >> + const struct ili9341_pdata *pdata;
> >> +
> >> + struct gpio_desc*reset_gpiod;
> >> + u32 rotation;
> >> +};
> >> +
> >
> > Hi Paul, you put the mipi_dsi_device inside the struct. I think it
> > maybe not
> > a good idea. That means the panel has a MIPI-DSI interface but it
> > doesn't
> > have actually.
> >
> >> +static int ili9341_probe(struct mipi_dsi_device *dsi)
> >> +{
> >> + struct device *dev = >dev;
> >> + struct ili9341 *priv;
> >> + int ret;
> >> +
> >> + /* See comment for mipi_dbi_spi_init() */
> >> + if (!dev->coherent_dma_mask) {
> >> + ret = dma_coerce_mask_and_coherent(dev,
> >> DMA_BIT_MASK(32));
> >> + if (ret) {
> >> + dev_warn(dev, "Failed to set dma mask
> >> %d\n", ret);
> >> + return ret;
> >> + }
> >> + }
> >> +
> >> + priv = devm_kzalloc(dev, sizeof(*priv), GFP_KERNEL);
> >> + if (!priv)
> >> + return -ENOMEM;
> >> +
> >> + mipi_dsi_set_drvdata(dsi, priv);
> >> + priv->dsi = dsi;
> >> +
> >> + device_property_read_u32(dev, "rotation", >rotation);
> >> +
> >> + priv->pdata = device_get_match_data(dev);
> >> + if (!priv->pdata)
> >> + return -EINVAL;
> >> +
> >> + drm_panel_init(>panel, dev, _funcs,
> >> + DRM_MODE_CONNECTOR_DPI);
> >> +
> >> + priv->reset_gpiod = devm_gpiod_get(dev, "reset",
> >> GPIOD_OUT_HIGH);
> >> + if (IS_ERR(priv->reset_gpiod)) {
> >> + dev_err(dev, "Couldn't get our reset GPIO\n");
> >> + return PTR_ERR(priv->reset_gpiod);
> >> + }
> >> +
> >> + ret = drm_panel_of_backlight(>panel);
> >> + if (ret < 0) {
> >> + if (ret != -EPROBE_DEFER)
> >> + dev_err(dev, "Failed to get backlight
> >> handle\n");
> >> + return ret;
> >> + }
> >> +
> >> + drm_panel_add(>panel);
> >> +
> >> + dsi->bus_type = priv->pdata->bus_type;
> >> + dsi->lanes = priv->pdata->lanes;
> >> + dsi->format = MIPI_DSI_FMT_RGB565;
> >> +
> >> + ret = mipi_dsi_attach(dsi);
> >> + if (ret) {
> >> + dev_err(dev, "Failed to attach DSI panel\n");
> >> + goto err_panel_remove;
> >> + }
> >> +
> >> + ret = mipi_dsi_maybe_register_tiny_driver(dsi);
> >> + if (ret) {
> >> + dev_err(dev, "Failed to init TinyDRM driver\n");
> >> + goto err_mipi_dsi_detach;
> >> + }
> >> +
> >> + return 0;
> >> +
> >> +err_mipi_dsi_detach:
> >> + mipi_dsi_detach(dsi);
> >> +err_panel_remove:
> >> + drm_panel_remove(>panel);
> >> + return ret;
> >> +}
> >> +
> >> +static int ili9341_remove(struct mipi_dsi_device *dsi)
> >> +{
> >> + struct ili9341 *priv = mipi_dsi_get_drvdata(dsi);
> >> +
> >> + mipi_dsi_detach(dsi);
> >> + drm_panel_remove(>panel);
> >> +
> >> + drm_panel_disable(>panel);
> >> + drm_panel_unprepare(>panel);
> >> +
> >> + return 0;
> >> +}
> >> +
> >> +static const struct ili9341_pdata yx240qv29_pdata = {
> >> + .mode = { DRM_SIMPLE_MODE(240, 320, 37, 49) },
> >> + .width_mm = 0, // TODO
> >> + .height_mm = 0, // TODO
> >> + .bus_type = MIPI_DCS_BUS_TYPE_DBI_SPI_C3,
> >> + .lanes = 1,
> >> +};
> >> +
> >> +static const struct of_device_id ili9341_of_match[] = {
> >> + { .compatible = "adafruit,yx240qv29", .data =
> >> _pdata },
> >> + { }
> >> +};
> >> +MODULE_DEVICE_TABLE(of, ili9341_of_match);
> >> +
> >> +static struct mipi_dsi_driver ili9341_dsi_driver = {
> >> + .probe = ili9341_probe,
> >> + .remove = ili9341_remove,
> >> + .driver = {
> >> + .name = "ili9341-dsi",
> >> + .of_match_table = ili9341_of_match,
> >> + },
> >> +};
> >> +module_mipi_dsi_driver(ili9341_dsi_driver);
> >
> > Again, you treat this driver as a mipi dsi driver but for a MIPI-DBI
> > (I8080/SPI)
> > panel device. That will make developers confused.
> >
> > Is it possible to just add a mipi_dbi_driver for I8080/SPI interface
> > panel?
> > Thanks!
>
> Please read the cover letter, it explains why it's done this way. The
> whole point of this patchset is to merge DSI and DBI frameworks in a
> way that can be maintained.
I think this proves the point that the proposed naming is confusing. At
least a rename would be required.
--
Regards,
Laurent Pinchart
___
dri-devel mailing list
答复: [PATCH v2 6/6] drm/panel: Add Ilitek ILI9341 DBI panel driver
> +struct ili9341 {
> + struct drm_panel panel;
> + struct mipi_dsi_device *dsi;
> + const struct ili9341_pdata *pdata;
> +
> + struct gpio_desc*reset_gpiod;
> + u32 rotation;
> +};
> +
Hi Paul, you put the mipi_dsi_device inside the struct. I think it maybe not
a good idea. That means the panel has a MIPI-DSI interface but it doesn't
have actually.
> +static int ili9341_probe(struct mipi_dsi_device *dsi)
> +{
> + struct device *dev = >dev;
> + struct ili9341 *priv;
> + int ret;
> +
> + /* See comment for mipi_dbi_spi_init() */
> + if (!dev->coherent_dma_mask) {
> + ret = dma_coerce_mask_and_coherent(dev, DMA_BIT_MASK(32));
> + if (ret) {
> + dev_warn(dev, "Failed to set dma mask %d\n", ret);
> + return ret;
> + }
> + }
> +
> + priv = devm_kzalloc(dev, sizeof(*priv), GFP_KERNEL);
> + if (!priv)
> + return -ENOMEM;
> +
> + mipi_dsi_set_drvdata(dsi, priv);
> + priv->dsi = dsi;
> +
> + device_property_read_u32(dev, "rotation", >rotation);
> +
> + priv->pdata = device_get_match_data(dev);
> + if (!priv->pdata)
> + return -EINVAL;
> +
> + drm_panel_init(>panel, dev, _funcs,
> + DRM_MODE_CONNECTOR_DPI);
> +
> + priv->reset_gpiod = devm_gpiod_get(dev, "reset", GPIOD_OUT_HIGH);
> + if (IS_ERR(priv->reset_gpiod)) {
> + dev_err(dev, "Couldn't get our reset GPIO\n");
> + return PTR_ERR(priv->reset_gpiod);
> + }
> +
> + ret = drm_panel_of_backlight(>panel);
> + if (ret < 0) {
> + if (ret != -EPROBE_DEFER)
> + dev_err(dev, "Failed to get backlight handle\n");
> + return ret;
> + }
> +
> + drm_panel_add(>panel);
> +
> + dsi->bus_type = priv->pdata->bus_type;
> + dsi->lanes = priv->pdata->lanes;
> + dsi->format = MIPI_DSI_FMT_RGB565;
> +
> + ret = mipi_dsi_attach(dsi);
> + if (ret) {
> + dev_err(dev, "Failed to attach DSI panel\n");
> + goto err_panel_remove;
> + }
> +
> + ret = mipi_dsi_maybe_register_tiny_driver(dsi);
> + if (ret) {
> + dev_err(dev, "Failed to init TinyDRM driver\n");
> + goto err_mipi_dsi_detach;
> + }
> +
> + return 0;
> +
> +err_mipi_dsi_detach:
> + mipi_dsi_detach(dsi);
> +err_panel_remove:
> + drm_panel_remove(>panel);
> + return ret;
> +}
> +
> +static int ili9341_remove(struct mipi_dsi_device *dsi)
> +{
> + struct ili9341 *priv = mipi_dsi_get_drvdata(dsi);
> +
> + mipi_dsi_detach(dsi);
> + drm_panel_remove(>panel);
> +
> + drm_panel_disable(>panel);
> + drm_panel_unprepare(>panel);
> +
> + return 0;
> +}
> +
> +static const struct ili9341_pdata yx240qv29_pdata = {
> + .mode = { DRM_SIMPLE_MODE(240, 320, 37, 49) },
> + .width_mm = 0, // TODO
> + .height_mm = 0, // TODO
> + .bus_type = MIPI_DCS_BUS_TYPE_DBI_SPI_C3,
> + .lanes = 1,
> +};
> +
> +static const struct of_device_id ili9341_of_match[] = {
> + { .compatible = "adafruit,yx240qv29", .data = _pdata },
> + { }
> +};
> +MODULE_DEVICE_TABLE(of, ili9341_of_match);
> +
> +static struct mipi_dsi_driver ili9341_dsi_driver = {
> + .probe = ili9341_probe,
> + .remove = ili9341_remove,
> + .driver = {
> + .name = "ili9341-dsi",
> + .of_match_table = ili9341_of_match,
> + },
> +};
> +module_mipi_dsi_driver(ili9341_dsi_driver);
Again, you treat this driver as a mipi dsi driver but for a MIPI-DBI (I8080/SPI)
panel device. That will make developers confused.
Is it possible to just add a mipi_dbi_driver for I8080/SPI interface panel?
Thanks!
Best regards
This email (including its attachments) is intended only for the person or
entity to which it is addressed and may contain information that is privileged,
confidential or otherwise protected from disclosure. Unauthorized use,
dissemination, distribution or copying of this email or the information herein
or taking any action in reliance on the contents of this email or the
information herein, by anyone other than the intended recipient, or an employee
or agent responsible for delivering the message to the intended recipient, is
strictly prohibited. If you are not the intended recipient, please do not read,
copy, use or disclose any part of this e-mail to others. Please notify the
sender immediately and permanently delete this e-mail and any attachments if
you received it in error. Internet communications cannot be guaranteed to be
timely, secure, error-free or virus-free. The sender does not accept liability
for any errors or omissions.
