From: Alan Cox <alan@linux.intel.com>
To: Thomas Abraham <thomas.abraham@linaro.org>
Cc: linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
grant.likely@secretlab.ca, ben-linux@fluff.org
Subject: Re: [PATCH 1/2] serial: samsung: Add unified interrupt handler for s3c64xx and later SoC's
Date: Wed, 10 Aug 2011 12:55:31 +0100 [thread overview]
Message-ID: <20110810125531.38226d7a@bob.linux.org.uk> (raw)
In-Reply-To: <1312971680-3898-2-git-send-email-thomas.abraham@linaro.org>
On Wed, 10 Aug 2011 15:51:19 +0530
Thomas Abraham <thomas.abraham@linaro.org> wrote:
> s3c64xx and later SoC's include the interrupt mask and pending
> registers in the uart controller, unlike the s3c24xx SoC's which have
> these registers in the interrupt controller. When the mask and
> pending registers are part of the uart controller, a unified
> interrupt handler can handle the tx/rx interrupt. With this, the
> static reservation of interrupt numbers for the uart tx/rx/err
> interrupts in the linux irq space is not required and simplifies
> adding device tree support.
Really only hardware changes so for the tty touching aspect of it
Acked-by: Alan Cox <alan@linux.intel.com>
next prev parent reply other threads:[~2011-08-10 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 10:21 [PATCH 0/2] Update uart irq handling for s3c64xx and later SoC's Thomas Abraham
2011-08-10 10:21 ` [PATCH 1/2] serial: samsung: Add unified interrupt handler " Thomas Abraham
2011-08-10 10:21 ` [PATCH 2/2] ARM: SAMSUNG: Remove uart irq handling from plaform code Thomas Abraham
2011-08-10 11:55 ` Alan Cox [this message]
2011-08-13 11:26 ` [PATCH 0/2] Update uart irq handling for s3c64xx and later SoC's Tomasz Figa
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=20110810125531.38226d7a@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=ben-linux@fluff.org \
--cc=grant.likely@secretlab.ca \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=thomas.abraham@linaro.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).