From: Jean-Baptiste MUR <jeanbaptiste@maunakeatech.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-devel@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ieee1394/ohci1394 : CycleTooLong interrupt management
Date: Thu, 23 Mar 2006 10:15:29 +0100 [thread overview]
Message-ID: <200603231015.29960.jeanbaptiste@maunakeatech.com> (raw)
In-Reply-To: <tkrat.6f7cb1ffe1d70bc4@s5r6.in-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]
Sorry for pollution. I have updated the patch accordingly to your comments.
It seems my mailer don't like tab very much so I send it as an attachment.
I hope this will be ok.
Jean-Baptiste
On Friday 17 March 2006 22:01, Stefan Richter wrote:
> Jean-Baptiste MUR wrote:
> ...
> > Kernel version : 2.6.16-rc4
>
> (actually plus an ohci1394 patch from the linux1394 development tree)
>
> ...
> > + /* If this event occurs, we try to reactivate the "cycle
> > master" bit. */
> > + reg_write(ohci, OHCI1394_LinkControlSet,
> > OHCI1394_LinkControl_CycleMaster);
> ...
>
> Three minor nits:
>
> There are tabs replaced by spaces and superfluous line breaks inserted
> in your posting. Take care that the mailer does not mangle whitespace.
> If you cannot prevent this nor switch the mailer, send the patch as
> attachment without recoding (i.e. 7bit encoding, not base64 or the
> like).
>
> Take care of a maximum line length of 80 characters. For example:
>
> /* Try to reactivate the "cycle master" bit. */
> reg_write(ohci, OHCI1394_LinkControlSet,
> OHCI1394_LinkControl_CycleMaster);
>
> The comment is unnecessary since the actual code is clear enough, at
> least IMO.
>
> Anyway, thanks again for identifying this problem.
> --
> Stefan Richter
> -=====-=-==- --== =---=
> http://arcgraph.de/sr/
>
[-- Attachment #2: CycleTooLong.patch --]
[-- Type: text/x-diff, Size: 1027 bytes --]
diff --git a/drivers/ieee1394/ohci1394.c b/drivers/ieee1394/ohci1394.c
index ab01a54..a240b2a 100644
--- a/drivers/ieee1394/ohci1394.c
+++ b/drivers/ieee1394/ohci1394.c
@@ -580,6 +580,7 @@ static void ohci_initialize(struct ti_oh
OHCI1394_isochRx |
OHCI1394_isochTx |
OHCI1394_postedWriteErr |
+ OHCI1394_cycleTooLong |
OHCI1394_cycleInconsistent);
/* Enable link */
@@ -2386,6 +2387,15 @@ static irqreturn_t ohci_irq_handler(int
PRINT(KERN_ERR, "physical posted write error");
/* no recovery strategy yet, had to involve protocol drivers */
}
+ if (event & OHCI1394_cycleTooLong) {
+ if(printk_ratelimit())
+ PRINT(KERN_WARNING, "isochronous cycle too long");
+ else
+ DBGMSG("OHCI1394_cycleTooLong");
+ reg_write(ohci, OHCI1394_LinkControlSet,
+ OHCI1394_LinkControl_CycleMaster);
+ event &= ~OHCI1394_cycleTooLong;
+ }
if (event & OHCI1394_cycleInconsistent) {
/* We subscribe to the cycleInconsistent event only to
* clear the corresponding event bit... otherwise,
prev parent reply other threads:[~2006-03-23 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 13:37 Jean-Baptiste MUR
2006-03-17 21:01 ` Stefan Richter
2006-03-23 9:15 ` Jean-Baptiste MUR [this message]
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=200603231015.29960.jeanbaptiste@maunakeatech.com \
--to=jeanbaptiste@maunakeatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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
Powered by JetHome