From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh-sci: console drainage
Date: Tue, 03 Mar 2009 06:18:01 +0000 [thread overview]
Message-ID: <20090303061801.GA30177@linux-sh.org> (raw)
On Tue, Feb 24, 2009 at 03:57:12PM +0900, Magnus Damm wrote:
> Modify the serial console code to wait for the transmit FIFO,
> make sure all bits have been put on the wire before returning.
On Tue, Feb 24, 2009 at 10:11:03PM +0900, Magnus Damm wrote:
> Add support for single IRQ hardware to the sh-rtc driver.
>
> This is useful for processors with limited interrupt masking
> support such as sh7750 and sh7780. With this patch in place we
> can add logic to the intc code that merges all RTC vectors into
> a single linux interrupt with proper masking/unmasking support.
>
> Specify a single IRQ in the platform data to use this new shared
> IRQ feature. Separate Periodic/Carry/Alarm IRQs are still supported.
On Tue, Feb 24, 2009 at 10:23:51PM +0900, Magnus Damm wrote:
> Fix iounmap() of pass-through P4 addresses. Without this patch
> iounmap() on the sh7780 rtc area results in a warning message.
On Tue, Feb 24, 2009 at 10:58:57PM +0900, Magnus Damm wrote:
> Instead of keeping the single vector -> single linux irq mapping
> we extend the intc code to support merging of vectors to a single
> linux irq. This helps processors such as sh7750, sh7780 and sh7785
> which have more vectors than masking ability. With this patch in
> place we can modify the intc tables to use one irq per maskable
> irq source. Please note the following:
>
> - If multiple vectors share the same enum then only the
> first vector will be available as a linux irq.
>
> - Drivers may need to be rewritten to get pending irq
> source from the hardware block instead of irq number.
>
> This patch together with the sh7785 specific intc tables solves
> DMA controller irq issues related to buggy interrupt masking.
>
> Signed-off-by: Magnus Damm <damm@igel.co.jp>
> Reported-by: Yoshihiro Shimoda <shimoda.yoshihiro@renesas.com>
Please try to keep the flow consistent here. Reported-by should always be
first, while Tested-by and so on tend to follow your Signed-off-by.
On Tue, Feb 24, 2009 at 10:59:04PM +0900, Magnus Damm wrote:
> Update intc tables and platform data to use one linux irq
> per maskable interrupt source instead of keeping the one-to-one
> mapping between vectors and linux irqs.
>
> This fixes potential irq masking issues for sh775x hardware
> blocks such as SCI/SCIF/RTC/DMAC/TMU2/REF.
On Tue, Feb 24, 2009 at 10:59:12PM +0900, Magnus Damm wrote:
> Update intc tables and platform data to use one linux irq
> per maskable interrupt source instead of keeping the one-to-one
> mapping between vectors and linux irqs.
>
> This fixes potential irq masking issues for sh7780 hardware
> blocks such as SCIF/RTC/DMAC/PCIC5/MMCIF/FLCTL/GPIO
On Tue, Feb 24, 2009 at 10:59:19PM +0900, Magnus Damm wrote:
> Update intc tables and platform data to use one linux irq
> per maskable interrupt source instead of keeping the one-to-one
> mapping between vectors and linux irqs.
>
> This fixes potential irq masking issues for sh7785 hardware
> blocks such as SCIF/DMAC/PCIC5/MMCIF/GDTA/FLCTL/GPIO
All applied, thanks.
next reply other threads:[~2009-03-03 6:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 6:18 Paul Mundt [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-24 6:57 [PATCH] sh-sci: console drainage Magnus Damm
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=20090303061801.GA30177@linux-sh.org \
--to=lethal@linux-sh.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.