dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Anitha Chrisanthus <anitha.chrisanthus@intel.com>
Cc: daniel.vetter@intel.com, edmund.j.dea@intel.com,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v7 0/4] Add support for KeemBay DRM driver
Date: Thu, 10 Sep 2020 10:42:15 +0200	[thread overview]
Message-ID: <20200910084215.GK438822@phenom.ffwll.local> (raw)
In-Reply-To: <1598904172-30865-1-git-send-email-anitha.chrisanthus@intel.com>

On Mon, Aug 31, 2020 at 01:02:48PM -0700, Anitha Chrisanthus wrote:
> This is a new DRM driver for Intel's KeemBay SOC.
> The SoC couples an ARM Cortex A53 CPU with an Intel
> Movidius VPU.
> 
> This driver is tested with the KMB EVM board which is the refernce baord
> for Keem Bay SOC. The SOC's display pipeline is as follows
> 
> +--------------+    +---------+    +-----------------------+
> |LCD controller| -> |Mipi DSI | -> |Mipi to HDMI Converter |
> +--------------+    +---------+    +-----------------------+
> 
> LCD controller and Mipi DSI transmitter are part of the SOC and
> mipi to HDMI converter is ADV7535 for KMB EVM board.
> 
> The DRM driver is a basic KMS atomic modesetting display driver and
> has no 2D or 3D graphics.It calls into the ADV bridge driver at
> the connector level.
> 
> Only 1080p resolution and single plane is supported at this time.
> The usecase is for debugging video and camera outputs.
> 
> Device tree patches are under review here
> https://lore.kernel.org/linux-arm-kernel/20200708175020.194436-1-daniele.alessandrelli@linux.intel.com/T/

I've looked at the code, and imo looks fairly reasonable. I think the
remaining things can also be polished in-tree, and we could start merging
the code already. For that 2 things are missing:

- Need a MAINTAINERS entry for this (I'm assuming you're volunteering)
- You need drm-misc commit rights set up so you can push patches, see

https://dri.freedesktop.org/docs/drm/gpu/drm-uapi.html#validating-changes-with-igt

The docs there also have howto and everything.

Cheers, Daniel

> 
> Changes since v1:
> - Removed redundant license text, updated license
> - Rearranged include blocks
> - renamed global vars and removed extern in c
> - Used upclassing for dev_private
> - Used drm_dev_init in drm device create
> - minor cleanups
> 
> Changes since v2:
> - squashed all commits to a single commit
> - logging changed to drm_info, drm_dbg etc.
> - used devm_drm_dev_alloc()
> - removed commented out sections and general cleanup
> 
> Changes since v3:
> - renamed dev_p to kmb
> - moved clocks under kmb_clock, consolidated clk initializations
> - use drmm functions
> - use DRM_GEM_CMA_DRIVER_OPS_VMAP
> - more cleanups
> 
> Changes since v4:
> - corrected spellings
> 
> Changes since v5:
> - corrected checkpatch warnings/checks
>    -Please ignore checkpatch checks on Camelcase - this is how it is
>    named in the databook
>    - Please ignore checkpatch warnings on misspelled for hsa, dout,
>    widthn etc. - they are spelled as in the databook
>    - Please ignore checkpatch checks on macro arguments reuse -
>    its confirmed ok
> 
> Changes since v6:
> - review changes Sam Ravnborg and Thomas Zimmerman
> 	split patch into 4 parts, part1 register definitions, part2 display
> 	driver files, part3 mipi dsi, part4 build files (Sam)
> 	removed kmb_crtc.h kmb_crtc_cleanup (Thomas)
> 	renamed mode_set, kmb_load, inlined unload (Thomas)
> 	moved remaining logging to drm_*(Thomas)
> 	re-orged driver initialization (Thomas)
> 	moved plane_status to drm_private (Sam)
> 	removed unnecessary logs and defines and ifdef codes (Sam)
> 	split dphy_init_sequence smaller (Sam)
> 	removed redundant checks in kmb_dsi (Sam)
> 	changed kmb_dsi_init to drm_bridge_connector_init and
> 	drm_connector_attach_encoder to bridge's connector (Sam)
> 	call helper_check in plane_atomic_check (Sam)
> 	renamed set to get for bpp and format functions(Sam)
> 	use drm helper functions for reset, duplicate/destroy state instead
> 	of kmb functions (Sam)
> 	removed kmb_priv from kmb_plane and removed kmb_plane_state (Sam)
> 
> Anitha Chrisanthus (4):
>   drm/kmb: Keem Bay driver register definition
>   drm/kmb: Add support for KeemBay Display
>   drm/kmb: Mipi DSI part of the display driver
>   drm/kmb: Build files for KeemBay Display driver
> 
>  drivers/gpu/drm/Kconfig         |    2 +
>  drivers/gpu/drm/Makefile        |    1 +
>  drivers/gpu/drm/kmb/Kconfig     |   13 +
>  drivers/gpu/drm/kmb/Makefile    |    2 +
>  drivers/gpu/drm/kmb/kmb_crtc.c  |  224 ++++++
>  drivers/gpu/drm/kmb/kmb_drv.c   |  676 +++++++++++++++++
>  drivers/gpu/drm/kmb/kmb_drv.h   |  170 +++++
>  drivers/gpu/drm/kmb/kmb_dsi.c   | 1523 +++++++++++++++++++++++++++++++++++++++
>  drivers/gpu/drm/kmb/kmb_dsi.h   |  350 +++++++++
>  drivers/gpu/drm/kmb/kmb_plane.c |  480 ++++++++++++
>  drivers/gpu/drm/kmb/kmb_plane.h |  110 +++
>  drivers/gpu/drm/kmb/kmb_regs.h  |  748 +++++++++++++++++++
>  12 files changed, 4299 insertions(+)
>  create mode 100644 drivers/gpu/drm/kmb/Kconfig
>  create mode 100644 drivers/gpu/drm/kmb/Makefile
>  create mode 100644 drivers/gpu/drm/kmb/kmb_crtc.c
>  create mode 100644 drivers/gpu/drm/kmb/kmb_drv.c
>  create mode 100644 drivers/gpu/drm/kmb/kmb_drv.h
>  create mode 100644 drivers/gpu/drm/kmb/kmb_dsi.c
>  create mode 100644 drivers/gpu/drm/kmb/kmb_dsi.h
>  create mode 100644 drivers/gpu/drm/kmb/kmb_plane.c
>  create mode 100644 drivers/gpu/drm/kmb/kmb_plane.h
>  create mode 100644 drivers/gpu/drm/kmb/kmb_regs.h
> 
> -- 
> 2.7.4
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-09-10  8:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 20:02 [PATCH v7 0/4] Add support for KeemBay DRM driver Anitha Chrisanthus
2020-08-31 20:02 ` [PATCH v7 1/4] drm/kmb: Keem Bay driver register definition Anitha Chrisanthus
2020-08-31 20:02 ` [PATCH v7 2/4] drm/kmb: Add support for KeemBay Display Anitha Chrisanthus
2020-09-10  8:30   ` Daniel Vetter
2020-09-10 18:33     ` Sam Ravnborg
2020-09-11  8:56       ` Daniel Vetter
2020-09-22 18:20     ` Chrisanthus, Anitha
2020-09-23 15:22       ` Daniel Vetter
2020-10-01 18:02     ` Chrisanthus, Anitha
2020-10-02  9:19       ` Daniel Vetter
2020-10-03  4:58         ` Chrisanthus, Anitha
2020-10-05 13:49           ` Daniel Vetter
2020-10-06  0:22             ` Chrisanthus, Anitha
2020-09-10  8:40   ` Daniel Vetter
2020-09-10  9:32   ` Neil Armstrong
2020-09-11 20:54     ` Chrisanthus, Anitha
2020-09-12 20:20       ` Sam Ravnborg
2020-08-31 20:02 ` [PATCH v7 3/4] drm/kmb: Mipi DSI part of the display driver Anitha Chrisanthus
2020-09-10  8:38   ` Daniel Vetter
2020-08-31 20:02 ` [PATCH v7 4/4] drm/kmb: Build files for KeemBay Display driver Anitha Chrisanthus
2020-09-10  8:42 ` Daniel Vetter [this message]
2020-09-10 22:45   ` [PATCH v7 0/4] Add support for KeemBay DRM driver Chrisanthus, Anitha
2020-10-07 13:37 ` Rob Herring

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=20200910084215.GK438822@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=anitha.chrisanthus@intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=edmund.j.dea@intel.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