From: "Shimoda, Yoshihiro" <yoshihiro.shimoda.uh@renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v4 2/6] sh: add a resource name for shdma
Date: Thu, 12 Jan 2012 01:09:11 +0000 [thread overview]
Message-ID: <4F0E32B7.7060902@renesas.com> (raw)
In-Reply-To: <4F0D39F5.90208@renesas.com>
2012/01/11 18:05, Guennadi Liakhovetski wrote:
> Unrelated to your patch, just something that caught my eye:
>
[ snip ]
>
> The above two platforms seem incorrect. Back then, as I switched sh_dma.c
> to use resources for interrupts [1], I just reproduced the behaviour of
> the original driver, but a verification with the header or the datasheet
> shows, that sh7780 and sh7785 have separate interrupts per channel, so, if
> anyone cares about those platforms, they might need a fix.
The interrupts of SH7780 DMAC and Sh7785 DMAC are strange.
Would you check the commit bdaa6e8062 "sh: multiple vectors per irq - base"?
- The SH7780 and SH7785 have separate INTEVT per channel, but the INT2MSKR
for the DMAC has one bit.
-- In this case, the commit log says:
"If multiple vectors shar the same enum then only the
first vector will be avilable as a linux irq."
- I think that the DMTE4_IRQ of SH7780 and SH7785 in
the "arch/sh/include/cpu-sh4/cpu/dma-sh4a.h" is breaking.
But, the old DMA API driver doesn't use this actually because the get_dmte_irq()
in dma-sh.c will change the IRQ number...
Best regards,
Yoshihiro Shimoda
> Thanks
> Guennadi
>
> [1] http://thread.gmane.org/gmane.linux.ports.sh.devel/7269/focusr70
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
> http://www.open-technology.de/
>
--
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
EC No.
prev parent reply other threads:[~2012-01-12 1:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 7:27 [PATCH v4 2/6] sh: add a resource name for shdma Shimoda, Yoshihiro
2012-01-11 9:05 ` Guennadi Liakhovetski
2012-01-12 1:09 ` Shimoda, Yoshihiro [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=4F0E32B7.7060902@renesas.com \
--to=yoshihiro.shimoda.uh@renesas.com \
--cc=linux-sh@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).