All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] RFC: 16550A pci serial board support
Date: Wed, 05 Jan 2011 21:18:32 +0100	[thread overview]
Message-ID: <4D24D218.3070709@domain.hid> (raw)
In-Reply-To: <4D24CF69.8040809@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1902 bytes --]

Am 05.01.2011 21:07, Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Am 05.01.2011 20:40, Stefan Kisdaroczi wrote:
>>> Am Dienstag 04 Januar 2011, 20:49:59 schrieben Sie:
>>>> Stefan Kisdaroczi wrote:
>>>>> Hi,
>>>>>
>>>>> the attached patch adds pci support to the 16550A serial driver. I have
>>>>> a Moxa CP-132 board and the first tests are looking good. If there is a
>>>>> chance to get the patch applied I kindly request you to review it. I'll
>>>>> add support for more Moxa boards if there is a interest to apply the
>>>>> patch.
>>>>>
>>>>> thanks
>>>>> Stefan
>>>> Looks fine to me, however, nit-picking a bit, could we do this differently:
>>> new patches attached.
>>>
>>
>> Looks good to me as well except for a minor white space damage:
>>
>>> +static int __devinit rt_16550_pci_probe(       struct pci_dev *pdev,
>>                                            ^^^^^^^
>>
>> I have one further suggestion which can be done on top: The RTDM_IRQTYPE
>> flags should be customized as well. So far we assume edge-type devices,
>> but PCI is level-triggered. Requesting edge works, but is suboptimal.
> 
> Well, on vanilla linux, the edge handler does not mask the interrupt
> line before invoking the handler, so, using the edge handler for level
> interrupts should not work and lock-up (except if IRQF_DISABLED is
> passed, which should now be the default, OK).

IRQF_DISABLED is a (soon to be removed) nop these days, all handlers are
called with interrupts disabled.

> 
> Anyway, is a driver the right place to pass these flags? Since the
> interrupt controller pins to which the PCI interrupts are wired really
> depends on the board more than on the device driver.
> 

I know. But can we always obtain the required information from Linux? If
Xenomai could set the right types automatically, that would be much
better of course.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2011-01-05 20:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 15:57 [Xenomai-help] RFC: 16550A pci serial board support Stefan Kisdaroczi
2011-01-04 19:49 ` Gilles Chanteperdrix
2011-01-05 19:40   ` Stefan Kisdaroczi
2011-01-05 19:55     ` Jan Kiszka
2011-01-05 20:07       ` Gilles Chanteperdrix
2011-01-05 20:18         ` Jan Kiszka [this message]
2011-01-05 22:03       ` Stefan Kisdaroczi
2011-01-07  8:28         ` Jan Kiszka
2011-01-07 22:21           ` Stefan Kisdaroczi
2011-01-07 23:04             ` Gilles Chanteperdrix

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=4D24D218.3070709@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=xenomai@xenomai.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.