From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Archit Taneja <archit@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 10/10] OMAP: DSS2: DSI Video mode support
Date: Mon, 05 Sep 2011 09:52:13 +0300 [thread overview]
Message-ID: <1315205533.2130.17.camel@deskari> (raw)
In-Reply-To: <4E646397.9030107@ti.com>
On Mon, 2011-09-05 at 11:22 +0530, Archit Taneja wrote:
> On Friday 02 September 2011 01:25 PM, Valkeinen, Tomi wrote:
> > On Fri, 2011-09-02 at 11:43 +0530, Archit Taneja wrote:
> >>> Sending a null packet to start the DDR clk is rather OMAP specific
> >>> internal thing, so I don't want to require the panel driver to need
> >> to
> >>> know that it must send a null packet to start the clock. So if the
> >> ddr
> >>> clk is not started automatically, I think we should have a function
> >> to
> >>> do that (dsi_start_ddr_clk or whatever), which will then send the
> >> null
> >>> packet (and perhaps return an error if DDR_CLK_ALWAYS_ON is not set,
> >>> dunno...).
> >>
> >> Okay, If we can confirm that a panel asks for DDR_CLK_ALWAYS_ON
> >> mainly
> >> because it doesn't have its own fclk, then the dsi driver surely
> >> needs
> >> to start the DDR clock by sending a NULL packet.
> >>
> >> If this is to be done, one thing that has to be thought of is:
> >>
> >> - We need one of the requested VC's to be in HS mode for this. Do we
> >> enable HS for a VC in the dsi driver itself? Currently, its the job
> >> of
> >> the panel driver to enable HSmode for a VC. Is this a clean approach?
> >
> > I have to say I don't have any idea what would be the best approach...
> >
> > What comes to my mind is that the DSI driver could automatically send
> > the null packet, when:
> >
> > a) ddr_clk_always_on is set
> > b) a channel is changed to HS and enabled (I guess it needs to be
> > enabled also, does it?)
>
> This approach sounds fine. The only drawback is that we send a NULL
> packet each time we enable a high speed channel. So if a panel is using
> 2 VCs, and it wants high speed for both channels(for some reason), we
> will be sending a NULL packet unnecessarily.
True. I don't see that doing any harm, though, so I guess it's ok.
> One observation was that the DDR clock has to be enabled only after the
> bridge chip is reset. Enabling HS, and sending a NULL packet before
> doing a hw reset of the bridge chip doesn't bring up the panel(that is a
> bit peculiar). So we can't do this within omapdss_dsi_display_enable().
Well that does sound strange. What happens there? Any errors? Commands
still going through?
Hmm, although... Well, I'm guessing, but if the HW reset for the chip
causes the chip to pull down the DSI lanes, or something similar, it
could cause errors in the OMAP side. But is that happening or something
else?
Tomi
next prev parent reply other threads:[~2011-09-05 6:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 10:51 [PATCH 00/10] OMAP: DSS2: DSI: Initial DSI video mode support Archit Taneja
2011-08-30 10:51 ` [PATCH 01/10] OMAP: DSS2: Use MIPI DSI transacition types and commands from include/video/mipi_display.h Archit Taneja
2011-08-30 10:51 ` [PATCH 02/10] OMAP: DSS2: DSI: Represent L4 and VP as sources of VC instead of modes Archit Taneja
2011-08-30 10:51 ` [PATCH 03/10] OMAP: DSS2: Create enum for DSI operation modes Archit Taneja
2011-08-30 10:51 ` [PATCH 04/10] OMAP: DSS2: DSI: Introduce generic write functions Archit Taneja
2011-08-30 10:51 ` [PATCH 05/10] OMAP: DSS2: DSI: Remove functions dsi_vc_dcs_read_1() and dsi_vc_dcs_read_2() Archit Taneja
2011-08-30 10:51 ` [PATCH 06/10] OMAP: DSS2: DSI: Split dsi_vc_dcs_read() into 2 functions Archit Taneja
2011-08-30 10:51 ` [PATCH 07/10] OMAP: DSS2: DSI: Introduce generic read functions Archit Taneja
2011-08-30 10:51 ` [PATCH 08/10] OMAP: DSS2: Clean up stallmode and io pad mode selection Archit Taneja
2011-08-30 10:51 ` [PATCH 09/10] OMAP: DSS2: Create an enum for DSI pixel formats Archit Taneja
2011-08-30 10:51 ` [PATCH 10/10] OMAP: DSS2: DSI Video mode support Archit Taneja
2011-09-01 13:14 ` Tomi Valkeinen
2011-09-02 5:15 ` Archit Taneja
2011-09-02 5:32 ` Tomi Valkeinen
2011-09-02 6:13 ` Archit Taneja
2011-09-02 7:55 ` Tomi Valkeinen
2011-09-05 5:52 ` Archit Taneja
2011-09-05 6:52 ` Tomi Valkeinen [this message]
2011-09-05 7:11 ` Archit Taneja
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=1315205533.2130.17.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=archit@ti.com \
--cc=linux-omap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox