linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: "ext Taneja, Archit" <archit@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: DSS2: DSI: Check for TX FIFO emptiness when sending long packets
Date: Mon, 26 Jul 2010 13:20:08 +0300	[thread overview]
Message-ID: <1280139608.2427.27.camel@tubuntu.research.nokia.com> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC3560870305FAB05B@dbde02.ent.ti.com>

On Mon, 2010-07-26 at 11:28 +0200, ext Taneja, Archit wrote:
> Hi,
> 
> I had a little query. We check for TX FIFO not full before
> sending a short packet in dsi_vc_send_short(), but we
> don't have a similar check in dsi_vc_send_long() before
> writing to the long packet header.
> 
> There is a check of the static fifo size of the channel and
> the length of data we are pushing, but that does not reflect
> the state of the TX FIFO at that point of time.
> 
> Do you think we should have a check using DSI_TX_FIFO_VC_EMPTINESS
> before writing to the long packet header?

Yes, I think we should check that. Otherwise the transfer will break
with DSI_VC_IRQ_FIFO_TX_OVF interrupt, although I think the lcd driver
doesn't currently see this in any way.

Although I'm not sure which would be better, return an error (EBUSY?
EWOULDBLOCK?) if the FIFO cannot hold the whole message, or block until
the FIFO can hold the whole message...

 Tomi



  reply	other threads:[~2010-07-26 10:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26  9:28 DSS2: DSI: Check for TX FIFO emptiness when sending long packets Taneja, Archit
2010-07-26 10:20 ` Tomi Valkeinen [this message]
2010-07-26 11:18   ` Taneja, Archit
2010-07-27  7:16     ` Tomi Valkeinen

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=1280139608.2427.27.camel@tubuntu.research.nokia.com \
    --to=tomi.valkeinen@nokia.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;
as well as URLs for NNTP newsgroup(s).