From: Shobhit Kumar <shobhit.kumar@intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>
Cc: Jani Nikula <jani.nikula@intel.com>,
Daniel Vetter <daniel.vetter@intel.com>,
jacob.jun.pan@intel.com, Shobhit Kumar <shobhit.kumar@intel.com>
Subject: [RFC v2 0/4] Crystal Cove PMIC based Panel and Backlight Control
Date: Fri, 2 Jan 2015 19:11:21 +0530 [thread overview]
Message-ID: <1420206085-2913-1-git-send-email-shobhit.kumar@intel.com> (raw)
Hi All
Please find modifed set of patches. Sending as a separate thread as initial
patches were a crude implementation to trigger discussion, but these have been
tested and also do not need intel_soc_pmic_writeb/readb functionaly, but uses
the regmap interface as suggested by Jacob.
These patches implement a drm_panel as a platform driver for the mfd_cell device
declared in intel_soc_pmic_core.c.
Still there are opens, where I need closure -
1. Added a new drm_panel, but how to find the panel in lack of OF info. For now
added a drm_panel function to find panel by name.
2. Backlight also needs similar pmic based control. Is it okay to add a backlight
class driver also as part of this panel driver ?
For now I am doing Backlight Enable/Disable also during panel/enable as this will
at least save power. Backlight control will need a backlight class driver.
Regards
Shobhit
Shobhit Kumar (4):
drm: Add support to find drm_panel by name
mfd: Add a new cell device for panel controlled by crystal cove pmic
drm/panel: Add new panel driver based on crystal cove pmic
drm/i915: Enable DSI panel enable/disable based on PMIC
drivers/gpu/drm/drm_panel.c | 18 +++
drivers/gpu/drm/i915/Kconfig | 1 +
drivers/gpu/drm/i915/intel_dsi.c | 16 +++
drivers/gpu/drm/i915/intel_dsi.h | 6 +
drivers/gpu/drm/i915/intel_dsi_panel_vbt.c | 1 +
drivers/gpu/drm/panel/Kconfig | 7 ++
drivers/gpu/drm/panel/Makefile | 1 +
drivers/gpu/drm/panel/panel-crystalcove.c | 191 +++++++++++++++++++++++++++++
drivers/mfd/intel_soc_pmic_crc.c | 3 +
include/drm/drm_panel.h | 3 +
10 files changed, 247 insertions(+)
create mode 100644 drivers/gpu/drm/panel/panel-crystalcove.c
--
1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-01-02 13:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 13:41 Shobhit Kumar [this message]
2015-01-02 13:41 ` [RFC v2 1/4] drm: Add support to find drm_panel by name Shobhit Kumar
2015-01-09 12:50 ` Jani Nikula
2015-01-12 7:37 ` Kumar, Shobhit
2015-01-12 23:08 ` [Intel-gfx] " Daniel Vetter
2015-01-13 15:14 ` Andrzej Hajda
2015-01-16 12:19 ` Thierry Reding
2015-01-02 13:41 ` [RFC v2 2/4] mfd: Add a new cell device for panel controlled by crystal cove pmic Shobhit Kumar
2015-01-02 13:41 ` [RFC v2 3/4] drm/panel: Add new panel driver based on " Shobhit Kumar
2015-01-09 13:08 ` Jani Nikula
2015-01-12 8:26 ` Kumar, Shobhit
2015-01-12 9:02 ` Kumar, Shobhit
2015-01-02 13:41 ` [RFC v2 4/4] drm/i915: Enable DSI panel enable/disable based on PMIC Shobhit Kumar
2015-01-09 13:17 ` Jani Nikula
2015-01-12 8:23 ` Kumar, Shobhit
2015-01-12 23:11 ` Daniel Vetter
2015-01-07 5:06 ` [RFC v2 0/4] Crystal Cove PMIC based Panel and Backlight Control Kumar, Shobhit
2015-01-09 13:20 ` Jani Nikula
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=1420206085-2913-1-git-send-email-shobhit.kumar@intel.com \
--to=shobhit.kumar@intel.com \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jacob.jun.pan@intel.com \
--cc=jani.nikula@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