All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Inki Dae <inki.dae@samsung.com>
Cc: airlied@linux.ie, daniel@ffwll.ch,
	dri-devel@lists.freedesktop.org,
	linux-samsung-soc@vger.kernel.org
Subject: Re: [GIT PULL] exynos-drm-next
Date: Tue, 28 Mar 2023 19:31:08 +0200	[thread overview]
Message-ID: <ZCMkXPW5vdps3xQE@phenom.ffwll.local> (raw)
In-Reply-To: <20230328040524.49278-1-inki.dae@samsung.com>

On Tue, Mar 28, 2023 at 01:05:24PM +0900, Inki Dae wrote:
> Hi Dave and Daniel,
> 
>    Just one patch series that moves the existing Exynos DSI driver
>    to drm/bridge directory to support both SoCs family - Exynos
>    and I.MX - because same Exynos MIPI DSI ip can be used by the two
>    different SoC family.
> 
>    Of course, there are some concerns about this patch series because Exynos
>    and I.MX SoCs have different HW characteristic but use the same HW driver.
>    However, I believe that there should be no problem as Exynos and I.MX
>    developers have conducted tests and reviews enough for about a year
>    since last April.
> 
>    This would be the first case that we allow different vendor SoCs to use
>    same device driver at least in DRM world so we anticipate experiencing
>    and resolving new issues through ongoing maintenance, and ultimately,
>    the experiences gained here will undoubtedly be able to contribute
>    the development of the community as well.
> 
>    Please kindly let me know if there is any problem.
> 
> Thanks,
> Inki Dae
> 
> The following changes since commit 46f28427f6f824b6cff06fa025a55350b7de454a:
> 
>   Merge tag 'drm-rcar-next-20230325' of git://git.kernel.org/pub/scm/linux/kernel/git/pinchartl/linux into drm-next (2023-03-27 18:20:20 +0200)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v6.4

Merged, but usually all drm bridge stuff goes through drm-misc, least so
that there's some amount of collaboration and not so much inter-tree
syncing.

Please apply for drm-misc commit rights (at least a quick check shows no
one from samsung) and land future bridge patches through that tree.

Cheers, Daniel

> 
> for you to fetch changes up to b2cfec52feb3bb737c4b65018ef4bfe9789e4be8:
> 
>   drm: bridge: samsung-dsim: Add i.MX8M Plus support (2023-03-28 09:05:41 +0900)
> 
> ----------------------------------------------------------------
> A patch series for moving MIPI-DSI driver for Exynos DRM to drm/bridge
> directory so that I.MX SoC family can also share the same device driver.
> Samsung MIPI DSIM device is a common IP that can be used by Exynos and I.MX8M
> Mini/Nano/Plus SoC. Regarding this, this patch series has added several
> things below to existing MIPI DSI driver,
> 	- Add exynos_dsi_type enum type to provide controller data from different
> 	  platforms.
> 	- Add two pipeline detection ways support - existing Exynos DSI child node
> 	  and I.MX family of-graph port or ports.
> 	- Consider component and bridged based DRM drivers.
> 	- Add device tree binding support of I.MX family.
> 
> ----------------------------------------------------------------
> Jagan Teki (14):
>       drm: exynos: dsi: Drop explicit call to bridge detach
>       drm: exynos: dsi: Lookup OF-graph or Child node devices
>       drm: exynos: dsi: Mark PHY as optional
>       drm: exynos: dsi: Add platform PLL_P (PMS_P) offset
>       drm: exynos: dsi: Introduce hw_type platform data
>       drm: exynos: dsi: Add atomic check
>       drm: exynos: dsi: Add input_bus_flags
>       drm: exynos: dsi: Add atomic_get_input_bus_fmts
>       drm: exynos: dsi: Consolidate component and bridge
>       drm: exynos: dsi: Add host helper for te_irq_handler
>       drm: bridge: Generalize Exynos-DSI driver into a Samsung DSIM bridge
>       dt-bindings: display: exynos: dsim: Add NXP i.MX8M Mini/Nano support
>       drm: bridge: samsung-dsim: Add i.MX8M Mini/Nano support
>       dt-bindings: display: exynos: dsim: Add NXP i.MX8M Plus support
> 
> Marek Szyprowski (1):
>       drm: exynos: dsi: Handle proper host initialization
> 
> Marek Vasut (1):
>       drm: bridge: samsung-dsim: Add i.MX8M Plus support
> 
>  .../bindings/display/exynos/exynos_dsim.txt        |    2 +
>  MAINTAINERS                                        |    9 +
>  drivers/gpu/drm/bridge/Kconfig                     |   12 +
>  drivers/gpu/drm/bridge/Makefile                    |    1 +
>  drivers/gpu/drm/bridge/samsung-dsim.c              | 1967 ++++++++++++++++++++
>  drivers/gpu/drm/exynos/Kconfig                     |    1 +
>  drivers/gpu/drm/exynos/exynos_drm_dsi.c            | 1813 +-----------------
>  include/drm/bridge/samsung-dsim.h                  |  115 ++
>  8 files changed, 2191 insertions(+), 1729 deletions(-)
>  create mode 100644 drivers/gpu/drm/bridge/samsung-dsim.c
>  create mode 100644 include/drm/bridge/samsung-dsim.h

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Inki Dae <inki.dae@samsung.com>
Cc: airlied@linux.ie, linux-samsung-soc@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [GIT PULL] exynos-drm-next
Date: Tue, 28 Mar 2023 19:31:08 +0200	[thread overview]
Message-ID: <ZCMkXPW5vdps3xQE@phenom.ffwll.local> (raw)
In-Reply-To: <20230328040524.49278-1-inki.dae@samsung.com>

On Tue, Mar 28, 2023 at 01:05:24PM +0900, Inki Dae wrote:
> Hi Dave and Daniel,
> 
>    Just one patch series that moves the existing Exynos DSI driver
>    to drm/bridge directory to support both SoCs family - Exynos
>    and I.MX - because same Exynos MIPI DSI ip can be used by the two
>    different SoC family.
> 
>    Of course, there are some concerns about this patch series because Exynos
>    and I.MX SoCs have different HW characteristic but use the same HW driver.
>    However, I believe that there should be no problem as Exynos and I.MX
>    developers have conducted tests and reviews enough for about a year
>    since last April.
> 
>    This would be the first case that we allow different vendor SoCs to use
>    same device driver at least in DRM world so we anticipate experiencing
>    and resolving new issues through ongoing maintenance, and ultimately,
>    the experiences gained here will undoubtedly be able to contribute
>    the development of the community as well.
> 
>    Please kindly let me know if there is any problem.
> 
> Thanks,
> Inki Dae
> 
> The following changes since commit 46f28427f6f824b6cff06fa025a55350b7de454a:
> 
>   Merge tag 'drm-rcar-next-20230325' of git://git.kernel.org/pub/scm/linux/kernel/git/pinchartl/linux into drm-next (2023-03-27 18:20:20 +0200)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v6.4

Merged, but usually all drm bridge stuff goes through drm-misc, least so
that there's some amount of collaboration and not so much inter-tree
syncing.

Please apply for drm-misc commit rights (at least a quick check shows no
one from samsung) and land future bridge patches through that tree.

Cheers, Daniel

> 
> for you to fetch changes up to b2cfec52feb3bb737c4b65018ef4bfe9789e4be8:
> 
>   drm: bridge: samsung-dsim: Add i.MX8M Plus support (2023-03-28 09:05:41 +0900)
> 
> ----------------------------------------------------------------
> A patch series for moving MIPI-DSI driver for Exynos DRM to drm/bridge
> directory so that I.MX SoC family can also share the same device driver.
> Samsung MIPI DSIM device is a common IP that can be used by Exynos and I.MX8M
> Mini/Nano/Plus SoC. Regarding this, this patch series has added several
> things below to existing MIPI DSI driver,
> 	- Add exynos_dsi_type enum type to provide controller data from different
> 	  platforms.
> 	- Add two pipeline detection ways support - existing Exynos DSI child node
> 	  and I.MX family of-graph port or ports.
> 	- Consider component and bridged based DRM drivers.
> 	- Add device tree binding support of I.MX family.
> 
> ----------------------------------------------------------------
> Jagan Teki (14):
>       drm: exynos: dsi: Drop explicit call to bridge detach
>       drm: exynos: dsi: Lookup OF-graph or Child node devices
>       drm: exynos: dsi: Mark PHY as optional
>       drm: exynos: dsi: Add platform PLL_P (PMS_P) offset
>       drm: exynos: dsi: Introduce hw_type platform data
>       drm: exynos: dsi: Add atomic check
>       drm: exynos: dsi: Add input_bus_flags
>       drm: exynos: dsi: Add atomic_get_input_bus_fmts
>       drm: exynos: dsi: Consolidate component and bridge
>       drm: exynos: dsi: Add host helper for te_irq_handler
>       drm: bridge: Generalize Exynos-DSI driver into a Samsung DSIM bridge
>       dt-bindings: display: exynos: dsim: Add NXP i.MX8M Mini/Nano support
>       drm: bridge: samsung-dsim: Add i.MX8M Mini/Nano support
>       dt-bindings: display: exynos: dsim: Add NXP i.MX8M Plus support
> 
> Marek Szyprowski (1):
>       drm: exynos: dsi: Handle proper host initialization
> 
> Marek Vasut (1):
>       drm: bridge: samsung-dsim: Add i.MX8M Plus support
> 
>  .../bindings/display/exynos/exynos_dsim.txt        |    2 +
>  MAINTAINERS                                        |    9 +
>  drivers/gpu/drm/bridge/Kconfig                     |   12 +
>  drivers/gpu/drm/bridge/Makefile                    |    1 +
>  drivers/gpu/drm/bridge/samsung-dsim.c              | 1967 ++++++++++++++++++++
>  drivers/gpu/drm/exynos/Kconfig                     |    1 +
>  drivers/gpu/drm/exynos/exynos_drm_dsi.c            | 1813 +-----------------
>  include/drm/bridge/samsung-dsim.h                  |  115 ++
>  8 files changed, 2191 insertions(+), 1729 deletions(-)
>  create mode 100644 drivers/gpu/drm/bridge/samsung-dsim.c
>  create mode 100644 include/drm/bridge/samsung-dsim.h

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  reply	other threads:[~2023-03-28 17:31 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230328040524epcas1p270b050efedfe53d8e59c7e9103d5b84c@epcas1p2.samsung.com>
2023-03-28  4:05 ` [GIT PULL] exynos-drm-next Inki Dae
2023-03-28  4:05   ` Inki Dae
2023-03-28 17:31   ` Daniel Vetter [this message]
2023-03-28 17:31     ` Daniel Vetter
2023-03-29  5:39     ` 대인기
2023-03-29  5:39       ` 대인기
2023-04-17  1:17       ` Inki Dae
2024-04-25  3:43 Inki Dae
  -- strict thread matches above, loose matches on Subject: below --
2023-12-12  5:11 Inki Dae
2023-12-12  5:11 ` Inki Dae
     [not found] <CGME20230809060216epcas1p31ee8f5adc0b079b3bf347369c04f2dfe@epcas1p3.samsung.com>
2023-08-09  6:02 ` Inki Dae
2023-08-09  6:02   ` Inki Dae
     [not found] <CGME20230130051056epcas1p3864c816bfccf0c8a6e7f8601b240b11e@epcas1p3.samsung.com>
2023-01-30  5:10 ` Inki Dae
2023-01-30  5:10   ` Inki Dae
     [not found] <CGME20220926020723epcas1p29e968d4d47ae3b95211c219fcd045d02@epcas1p2.samsung.com>
2022-09-26  2:07 ` Inki Dae
2022-09-26  2:07   ` Inki Dae
     [not found] <CGME20220712061009epcas1p2a58002c639023a32375700be9ee9dea5@epcas1p2.samsung.com>
2022-07-12  6:10 ` Inki Dae
2022-07-12  6:10   ` Inki Dae
2021-12-22  3:53 Inki Dae
2021-12-22  3:53 ` Inki Dae
2021-08-21 17:28 Inki Dae
     [not found] <CGME20210611024956epcas1p1c15767f446a585a62be9aec1482082c1@epcas1p1.samsung.com>
2021-06-11  2:59 ` Inki Dae
2021-06-11  2:59   ` Inki Dae
     [not found] <CGME20210330082100epcas1p14a343aa642e07f678d265cb4fd9e930a@epcas1p1.samsung.com>
2021-03-30  8:29 ` Inki Dae
2021-03-30  8:29   ` Inki Dae
     [not found] <CGME20201201044247epcas1p321782889404edc13c2a8bdea2800e9a0@epcas1p3.samsung.com>
2020-12-01  4:50 ` Inki Dae
2020-12-01  4:50   ` Inki Dae
     [not found] <CGME20200922083212epcas1p3874ca74fbb2d46214b69bc0dd757aaaf@epcas1p3.samsung.com>
2020-09-22  8:38 ` Inki Dae
2020-09-22  8:38   ` Inki Dae
     [not found] <CGME20200520052745epcas1p3ea5ad049aa682f5afbeaaeec9df8d835@epcas1p3.samsung.com>
2020-05-20  5:33 ` Inki Dae
2020-05-20  5:33   ` Inki Dae
     [not found] <CGME20200316010443epcas1p33627ec18d70b980b7a5c943de8cfa07d@epcas1p3.samsung.com>
2020-03-16  1:09 ` Inki Dae
2020-03-16  1:09   ` Inki Dae
2020-03-18  2:17   ` Dave Airlie
2020-03-18  2:17     ` Dave Airlie
2020-03-18  3:16     ` Inki Dae
2020-03-18  3:16       ` Inki Dae
     [not found] <CGME20200121004854epcas1p19ef322f1b88ce31f28a17bde2bacc3fc@epcas1p1.samsung.com>
2020-01-21  0:52 ` Inki Dae
2020-01-21  0:52   ` Inki Dae
2019-10-28 12:34 Inki Dae
2019-10-28 12:34 ` Inki Dae
2019-09-01 12:06 Inki Dae
2019-06-27 14:28 Inki Dae
     [not found] <CGME20190422095042epcas1p27726a67f8283fdc4beff8561d0254957@epcas1p2.samsung.com>
2019-04-22  9:51 ` Inki Dae
2019-04-24  2:03   ` Dave Airlie
2019-04-24  2:11     ` Inki Dae
     [not found] <CGME20190207113137epcas1p44bf0105c4de7200eacb9e069ae28f1fd@epcas1p4.samsung.com>
2019-02-07 11:31 ` Inki Dae
     [not found] <CGME20181205094053epcas1p118ccbb4387ce9bbc78e6d0988af94ff3@epcas1p1.samsung.com>
2018-12-05  9:40 ` Inki Dae
     [not found] <CGME20181001080136epcas2p25ea2774ba9a203331314084a2c1a342d@epcas2p2.samsung.com>
2018-10-01  8:01 ` Inki Dae
     [not found] <CGME20180725080228epcas1p2cdab6ad94e69018ba6f30c5bc82191c3@epcas1p2.samsung.com>
2018-07-25  8:02 ` Inki Dae
     [not found] <CGME20180514054053epcas1p252e78c047cd19b821e57ca0e63cc3dc3@epcas1p2.samsung.com>
2018-05-14  5:40 ` Inki Dae
     [not found] <CGME20180102003618epcas2p2d82ece8ab037e5213f1bc0b83cdb1a43@epcas2p2.samsung.com>
2018-01-02  0:36 ` Inki Dae
     [not found] <CGME20171026013709epcas2p2525d1249a7f2ad640ce9028df12e2436@epcas2p2.samsung.com>
2017-10-26  1:37 ` Inki Dae
2017-11-14  4:22   ` Dave Airlie
2017-11-15  1:26     ` Inki Dae
2017-11-15 10:27       ` Daniel Stone
2017-11-15 22:51         ` Inki Dae
2017-11-20  7:33       ` Daniel Vetter
2017-11-28 13:45         ` Marek Szyprowski
2017-11-29  9:52           ` Daniel Vetter
2017-11-28 22:40         ` Inki Dae
     [not found] <CGME20170825061857epcas1p4e7086e95f9b626ce8175a62af120e4a5@epcas1p4.samsung.com>
2017-08-25  6:18 ` Inki Dae
     [not found] <CGME20170418020509epcas5p2e54f307dee164846dabf0470c5f134eb@epcas5p2.samsung.com>
2017-04-18  2:05 ` Inki Dae
2017-04-18  2:15   ` Inki Dae
2017-04-18  2:21   ` Andi Shyti
2017-04-18  2:30     ` Inki Dae
2017-04-18  7:11       ` Krzysztof Kozlowski
2017-04-18 23:35   ` Dave Airlie
2017-04-19  1:56     ` Inki Dae
     [not found] <CGME20170207070737epcas1p3a485458c1d8294f9df82bf5063047860@epcas1p3.samsung.com>
2017-02-07  7:07 ` Inki Dae
     [not found] <CGME20170131004642epcas1p29b431d13f09984c7beff4eb9b654ad2f@epcas1p2.samsung.com>
2017-01-31  0:46 ` Inki Dae
2017-01-31  9:11   ` Inki Dae
2016-12-06  0:15 Inki Dae
2016-09-30 16:26 Inki Dae
2016-07-13 14:30 Inki Dae
2016-04-30  3:01 Inki Dae
2015-12-14  4:56 Inki Dae
2015-10-28  6:55 Inki Dae
2015-10-28 10:15 ` Daniel Stone
2015-10-28 10:48   ` Inki Dae
2015-10-28 10:58     ` Daniel Stone
2015-10-28 11:00       ` Daniel Stone
2015-10-28 11:16         ` Inki Dae
2015-10-28 11:52           ` Daniel Stone
2015-10-28 12:37             ` Inki Dae
2015-11-02 23:10               ` Dave Airlie
2015-11-03  2:11                 ` Inki Dae
2015-11-03  2:36                   ` Dave Airlie
2015-11-03  4:36               ` Inki Dae
2015-11-03 18:59                 ` Daniel Stone
2015-10-28 10:17 ` Inki Dae
2015-09-02 14:35 inki.dae
2015-08-30 16:22 inki.dae
2015-08-16 15:20 inki.dae
2015-06-22 16:42 inki.dae
2015-04-13  3:04 Inki Dae
2015-01-25 13:19 inki.dae
2014-11-25 12:41 Inki Dae
2014-08-04  5:02 Inki Dae
2014-06-02  6:22 Inki Dae
2014-04-03 17:34 inki.dae
2014-04-04  4:59 ` Tomasz Figa
2014-04-04  5:34   ` Inki Dae
2014-04-04  7:28     ` Tomasz Figa
2014-04-04  7:48       ` Inki Dae
2014-04-04  8:05         ` Tomasz Figa
2014-04-04  8:26           ` Inki Dae
2014-03-21  8:27 Inki Dae
2013-09-05  5:53 Inki Dae
2013-04-29  6:36 Inki Dae
2013-04-17  5:36 Inki Dae
2013-02-15  4:24 Inki Dae
2012-11-20  7:35 Inki Dae
2012-11-20  8:44 ` Marek Szyprowski
2012-11-21  7:29 ` Inki Dae
2012-10-04  2:12 Inki Dae

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=ZCMkXPW5vdps3xQE@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=inki.dae@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    /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.