From: Andrzej Hajda <a.hajda@samsung.com>
To: Inki Dae <inki.dae@samsung.com>, dri-devel@lists.freedesktop.org
Cc: linux-samsung-soc@vger.kernel.org, treding@nvidia.com
Subject: Re: [PATCH v2 1/2] drm/mipi-dsi: add (LPM) Low Power Mode transfer support
Date: Mon, 28 Jul 2014 18:09:58 +0200 [thread overview]
Message-ID: <53D675D6.2000309@samsung.com> (raw)
In-Reply-To: <1406512857-7213-2-git-send-email-inki.dae@samsung.com>
On 07/28/2014 04:00 AM, Inki Dae wrote:
> This patch adds below two flags for LPM transfer, and it attaches LPM flags
> to a msg in accordance with master's mode_flags set by LCD Panel driver.
>
> MIPI_DSI_MODE_CMD_LPM
> - If this flag is set by Panel driver, MIPI-DSI controller will tranfer
> command data to Panel device in Low Power Mode.
What do you mean by command data? It could be:
- all transfer in command mode of operations,
- transfer initialized by the driver by writing to DSIM registers.
>
> MIPI_DSI_MODE_VIDEO_LPM
> - If this flag is set by Panel driver, MIPI-DSI controller will tranfer
> image data to Panel device in Low Power Mode.
What is the meaning of this flag in case of command mode of operation?
Maybe it would be better to create flags based on source of data/FIFOs:
- commands send by SFR registers,
- commands generated from data sent from Display Controller.
>
> And above two flags can be combined together to transfer command and video
> data to Panel device.
>
> MIPI DSI spec says,
> "the host processor controls the desired mode of clock operation.
> Host protocol and applications control Clock Lane operating mode
> (High Speed or Low Power mode). System designers are responsible
> for understanding the clock requirements for peripherals attached
> to DSI and controlling clock behavior in accordance with those
> requirements."
>
> Some LCD Panel devices, nt35502a, would need LPM transfer support
> because they should receive some initial commands with LPM by default
> hardware setting.
Is this requirement for initial commands, or for all commands.
Btw what is the mode of operation of nt35502a? What flags do you need
for it?
>
> Changelog v2: just add more descriptions.
>
> Signed-off-by: Inki Dae <inki.dae@samsung.com>
> Acked-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
> drivers/gpu/drm/drm_mipi_dsi.c | 3 +++
> include/drm/drm_mipi_dsi.h | 4 ++++
> 2 files changed, 7 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_mipi_dsi.c b/drivers/gpu/drm/drm_mipi_dsi.c
> index e633df2..6b2bbda 100644
> --- a/drivers/gpu/drm/drm_mipi_dsi.c
> +++ b/drivers/gpu/drm/drm_mipi_dsi.c
> @@ -232,6 +232,9 @@ int mipi_dsi_dcs_write(struct mipi_dsi_device *dsi, unsigned int channel,
> break;
> }
>
> + if (dsi->mode_flags & MIPI_DSI_MODE_CMD_LPM)
> + msg.flags = MIPI_DSI_MSG_USE_LPM;
> +
> return ops->transfer(dsi->host, &msg);
> }
Shouldn't this be also the same for dcs read?
Anyway I think check in the DSIM should be used instead, as panel driver
can issue other dsi transfers without MIPI_DSI_MSG_USE_LPM flag set.
Regards
Andrzej
> EXPORT_SYMBOL(mipi_dsi_dcs_write);
> diff --git a/include/drm/drm_mipi_dsi.h b/include/drm/drm_mipi_dsi.h
> index 944f33f..1c41e49 100644
> --- a/include/drm/drm_mipi_dsi.h
> +++ b/include/drm/drm_mipi_dsi.h
> @@ -94,6 +94,10 @@ void mipi_dsi_host_unregister(struct mipi_dsi_host *host);
> #define MIPI_DSI_MODE_VSYNC_FLUSH BIT(8)
> /* disable EoT packets in HS mode */
> #define MIPI_DSI_MODE_EOT_PACKET BIT(9)
> +/* command low power mode */
> +#define MIPI_DSI_MODE_CMD_LPM BIT(10)
> +/* video low power mode */
> +#define MIPI_DSI_MODE_VIDEO_LPM BIT(11)
>
> enum mipi_dsi_pixel_format {
> MIPI_DSI_FMT_RGB888,
>
next prev parent reply other threads:[~2014-07-28 16:09 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 2:00 [PATCH v2 0/2] drm/mipi-dsi: support lpm (low power mode) transfer Inki Dae
2014-07-28 2:00 ` [PATCH v2 1/2] drm/mipi-dsi: add (LPM) Low Power Mode transfer support Inki Dae
2014-07-28 16:09 ` Andrzej Hajda [this message]
2014-07-29 0:57 ` YoungJun Cho
2014-07-29 10:23 ` Andrzej Hajda
2014-08-03 7:03 ` Inki Dae
2014-08-03 7:16 ` Inki Dae
2014-08-05 8:12 ` Andrzej Hajda
2014-07-29 3:30 ` Inki Dae
2014-08-05 11:12 ` Thierry Reding
2014-08-06 7:11 ` Inki Dae
2014-08-06 7:43 ` Thierry Reding
2014-08-06 17:09 ` Inki Dae
2014-08-07 6:58 ` Thierry Reding
2014-08-07 7:51 ` Inki Dae
2014-08-07 9:09 ` Thierry Reding
2014-08-07 10:49 ` Inki Dae
2014-08-07 11:09 ` Thierry Reding
2014-08-07 13:05 ` Inki Dae
2014-08-07 13:17 ` Thierry Reding
2014-08-07 13:39 ` Inki Dae
2014-08-07 13:55 ` Thierry Reding
2014-08-08 1:45 ` Inki Dae
2014-08-08 7:03 ` Thierry Reding
2014-08-08 7:37 ` Inki Dae
2014-08-08 9:02 ` Andrzej Hajda
2014-08-08 9:40 ` Andrzej Hajda
2014-08-11 7:09 ` Inki Dae
2014-08-11 7:44 ` Andrzej Hajda
2014-08-11 8:01 ` Inki Dae
2014-08-11 8:05 ` Andrzej Hajda
2014-08-12 11:54 ` YoungJun Cho
2014-08-12 13:08 ` Inki Dae
2014-08-08 9:55 ` Thierry Reding
2014-08-11 5:19 ` Inki Dae
2014-08-11 7:24 ` Thierry Reding
2014-08-11 7:35 ` Inki Dae
2014-08-11 7:50 ` Thierry Reding
2014-08-11 8:15 ` Inki Dae
2014-08-11 9:11 ` Thierry Reding
2014-08-12 2:51 ` Inki Dae
2014-07-28 2:00 ` [PATCH v2 2/2] drm/exynos: dsi: add LPM (Low Power Mode) " Inki Dae
2014-07-28 15:50 ` Andrzej Hajda
2014-07-29 3:42 ` Inki Dae
2014-07-29 11:39 ` Andrzej Hajda
2014-07-29 12:08 ` Inki Dae
2014-07-29 13:16 ` Andrzej Hajda
2014-08-07 7:09 ` 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=53D675D6.2000309@samsung.com \
--to=a.hajda@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=treding@nvidia.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 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.