linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Bordug <vitb@kernel.crashing.org>
To: "Samuel Ortiz" <samuel@sortiz.org>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] [POWERPC] 8xx: PQ SoC IRDA support
Date: Thu, 10 May 2007 02:36:11 +0400	[thread overview]
Message-ID: <20070510023611.3a1be1d9@localhost.localdomain> (raw)
In-Reply-To: <irUYA8PN.1178718371.1966580.samuel@sortiz.org>

On 9 May 2007 13:46:11 -0000
Samuel Ortiz wrote:

> >So to recap, similar handling path for similar SoC device existing
> >in current kernel for a while now, and working good.  
> 
> I'm sure it works good, but doing the whole RX path from an interrupt
> handler doesn't sound like the best thing to do, at least to me. And
> with a SIR IrDA device, you can afford to offload your interrupt
> processing to a BH, nobody will notice the difference in terms of
> performance.
> I'm not against your proposed implementation, but I just think there's
> a nicer way to achieve the same result.
May I ask to point to the code you're keeping in mind here?

I'm not going to touch this path or else the code will miss this merge window as well, 
but I'm going to keep improving it, and this rework might be useful not only for this particular driver,
but for similar kernel pieces too.


-- 
Sincerely, Vitaly

  reply	other threads:[~2007-05-09 22:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 22:42 [PATCH] [POWERPC] 8xx: PQ SoC IRDA support Vitaly Bordug
2007-05-09  8:42 ` Samuel Ortiz
2007-05-09 10:53   ` Vitaly Bordug
2007-05-09 13:46     ` Samuel Ortiz
2007-05-09 22:36       ` Vitaly Bordug [this message]
2007-05-09 23:53 ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2007-05-08  5:27 Vitaly Bordug
2007-05-08 14:36 ` Loeliger Jon-LOELIGER
2007-05-08 16:18   ` Vitaly Bordug
2007-05-08  1:30 Vitaly Bordug
2007-05-08 13:33 ` Kumar Gala
2007-05-08 16:19   ` Vitaly Bordug

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=20070510023611.3a1be1d9@localhost.localdomain \
    --to=vitb@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=samuel@sortiz.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).