public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Juha Yrjölä" <juha.yrjola@nokia.com>
To: ext Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] Convert drivers to new irq trigger modes
Date: Thu, 9 Feb 2006 08:25:36 +0200	[thread overview]
Message-ID: <20060209062536.GC11799@two.research.nokia.com> (raw)
In-Reply-To: <43EA4234.4070807@gmail.com>

On Wed, Feb 08, 2006 at 08:10:44PM +0100, Dirk Behme wrote:

> >> 	int			irq;
> >>+	int			irq_type;
> >
> >This doesn't seem to be used anywhere.
> 
> To which file do you refer here? isp1301_omap.c, tps65010.c 
> or omap_ts.h? I use irq_type in all of them.

Sorry, that part of the patch was obviously correct.  I don't know what I
was smoking at the time. =)

> >You should be ORring here.  Otherwise you lose the SA_SAMPLE_RANDOM flag.
> 
> It is intended to lose SA_SAMPLE_RANDOM here. 
> SA_SAMPLE_RANDOM is the default and shall be used by 
> request_irq() on boards which don't need special trigger 
> setting. But on boards which need special trigger level 
> setting this shall be overridden by the correct setting.

SA_SAMPLE_RANDOM doesn't have anything to do with triggering.  It's used to
indicate whether an IRQ source can be used to feed the kernel entropy pools. 
If the IRQ in question cannot be considered to happen at random intervals,
the flag must not be set.

Cheers,
Juha

  reply	other threads:[~2006-02-09  6:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 17:32 [PATCH] Convert drivers to new irq trigger modes Dirk Behme
2006-02-07 23:16 ` Tony Lindgren
2006-02-08  5:14 ` Juha Yrjölä
2006-02-08 19:10   ` Dirk Behme
2006-02-09  6:25     ` Juha Yrjölä [this message]
2006-02-12 15:43       ` Dirk Behme
2006-02-13  9:17         ` Juha Yrjölä

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=20060209062536.GC11799@two.research.nokia.com \
    --to=juha.yrjola@nokia.com \
    --cc=dirk.behme@googlemail.com \
    --cc=linux-omap-open-source@linux.omap.com \
    /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