From: Roman Weissgaerber <weissg@vienna•at>
To: "Kári Davíðsson" <kd@flaga•is>
Cc: "linuxppc-embedded@lists•linuxppc.org"
<linuxppc-embedded@lists•linuxppc.org>,
"linux-usb-devel@lists•sourceforge.net"
<linux-usb-devel@lists•sourceforge.net>
Subject: Re:USB questions (for the MPC8xx)
Date: Fri, 16 Mar 2001 20:43:38 +0100 [thread overview]
Message-ID: <3AB26CEA.E4111263@vienna.at> (raw)
In-Reply-To: EADB10BAC266A14A85ECBF8686A73E3108AFCF@kolkrabbi.flaga.is
Kári Davíðsson wrote:
> Hi,
>
> In the m8xxhci.c hci driver for the mpc one can select to use TIMER1 for
> the SOF generator.
> A interruopt handler, m8xxhci_timer_interrupt() is registered to handle
> this interrupt and generate the SOF.
> Why is it then that the timer is also exported to PA6?
> Why is it the the USE_TIMER1_FOR_SOF is defined within the
> USE_UCODE_PATCH which is for external generated SOF-interrupt?
> Isn't the timer option exactly for the case where you do not have
> externally generated SOF-interrupt?
> If we can use a timer for generating the SOF why can't we just use a
> regular kernel timer instead, and therfore free one timer or baud rate
> generator?
>
The microcode patch needs an external 1kHz Signal on dreq input.
Timer 1 is one option to generate that external signal.
The interrupt handler is not needed anymore so my patch should have
changed a little bit more. The timer can run without interrupt handler
it just must generate the external 1kHz Signal.
- Roman
> Thanks,
>
> K.D.
>
> P.S. sorry for the x-post I am not shure if this belongs to the embedded
> list or the usb list.
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
parent reply other threads:[~2001-03-16 19:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <EADB10BAC266A14A85ECBF8686A73E3108AFCF@kolkrabbi.flaga.is>]
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=3AB26CEA.E4111263@vienna.at \
--to=weissg@vienna$(echo .)at \
--cc=kd@flaga$(echo .)is \
--cc=linux-usb-devel@lists$(echo .)sourceforge.net \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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