From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] libahci: Add support to handle HOST_IRQ_STAT as edge trigger latch.
Date: Mon, 04 May 2015 16:08:08 +0300 [thread overview]
Message-ID: <55476F38.7080002@cogentembedded.com> (raw)
In-Reply-To: <1430667220-23477-2-git-send-email-stripathi@apm.com>
Hello.
On 5/3/2015 6:33 PM, Suman Tripathi wrote:
> This patch adds the support to handle HOST_IRQ_STAT as edge trigger
> latch.
> Signed-off-by: Suman Tripathi <stripathi@apm.com>
> ---
> drivers/ata/ahci.h | 2 ++
> drivers/ata/libahci.c | 19 +++++++++++++++++++
> 2 files changed, 21 insertions(+)
> diff --git a/drivers/ata/ahci.h b/drivers/ata/ahci.h
> index 71262e0..2df2237 100644
> --- a/drivers/ata/ahci.h
> +++ b/drivers/ata/ahci.h
[...]
> +++ b/drivers/ata/libahci.c
> @@ -1879,6 +1879,25 @@ static irqreturn_t ahci_single_irq_intr(int irq, void *dev_instance)
> */
> writel(irq_stat, mmio + HOST_IRQ_STAT);
>
> + /*
> + * HOST_IRQ_STAT behaves as edge trigger latch. When HOST_IRQ_STAT
> + * detects a egde from PORT_IRQ_STAT, it happens to loose interrupts
s/loose/lose/.
MBR, Sergei
next prev parent reply other threads:[~2015-05-04 13:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1430667220-23477-1-git-send-email-stripathi@apm.com>
[not found] ` <1430667220-23477-3-git-send-email-stripathi@apm.com>
2015-05-04 0:26 ` [PATCH v3 2/2] ata: ahci_xgene: Add AHCI Support for 2nd HW version of APM X-Gene SoC AHCI SATA Host controller Julian Calaby
2015-05-04 2:51 ` Suman Tripathi
2015-05-04 3:22 ` Julian Calaby
2015-05-04 4:33 ` Suman Tripathi
[not found] ` <1430667220-23477-2-git-send-email-stripathi@apm.com>
2015-05-04 13:08 ` Sergei Shtylyov [this message]
2015-05-04 15:47 ` [PATCH v3 1/2] libahci: Add support to handle HOST_IRQ_STAT as edge trigger latch Tejun Heo
2015-05-04 16:43 ` Suman Tripathi
2015-05-04 18:26 ` Tejun Heo
2015-05-05 5:55 ` Suman Tripathi
2015-05-05 13:18 ` Tejun Heo
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=55476F38.7080002@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-arm-kernel@lists.infradead.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).