From: Nishanth Menon <menon.nishanth@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] DeAsserting UART Interrupt line on OMAP3530 for uboot
Date: Thu, 05 Mar 2009 16:34:25 +0200 [thread overview]
Message-ID: <49AFE2F1.10609@gmail.com> (raw)
In-Reply-To: <VSNLCHNFE001biP2rv8000720db@VSNLCHNFE001.VSNLXCHANGE.COM>
Rahanesh said the following on 03/05/2009 04:21 PM:
> Can anyone help me to de-assert the uart interrupt line.
>
Please read the OMAP3530 TRM. it explains how to handle the UART registers.
> I have enabled the UART interrupt only for reception of data.
>
> Processor get the interrupt and data is read to a local buffer. Since the
> Interrupt line is not deasserted , i keep on getting the same interrupt.
>
> How can i deassert the UART interrupt in OMAP 3530? Is it in the UART side
> or Interrupt Controller Side?
>
> How does Ubot handle this? How is the Interrupt line cleared in Uboot?
>
>
I would recommend doing the following:
git clone git://git.denx.de/u-boot.git
vim drivers/serial/ns16550.c
You'd see that it is not using interrupts, it does a poll on interrupt
status register..
Regards,
Nishanth Menon
prev parent reply other threads:[~2009-03-05 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 14:21 [U-Boot] DeAsserting UART Interrupt line on OMAP3530 for uboot Rahanesh
2009-03-05 14:34 ` Nishanth Menon [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=49AFE2F1.10609@gmail.com \
--to=menon.nishanth@gmail.com \
--cc=u-boot@lists.denx.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