From: Michal Simek <michal.simek@petalogix.com>
To: johnlinn@comcast.net
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
joe@perches.com, grant likely <grant.likely@secretlab.ca>,
John Linn <john.linn@xilinx.com>
Subject: Re: [PATCH V4] tty/serial: add support for Xilinx PS UART
Date: Fri, 06 May 2011 14:11:44 +0200 [thread overview]
Message-ID: <4DC3E580.9090500@petalogix.com> (raw)
In-Reply-To: <1013673718.2094564.1304113268455.JavaMail.root@sz0140a.emeryville.ca.mail.comcast.net>
johnlinn@comcast.net wrote:
>>> Yes I'll have a look at it, sorry for the hassle.
>>>
>>> I'm assuming I need to try it against linus
>>> tree as something may have changed. Or some other tree?
>> Or you are assuimg NO_IRQ is defined everywhere which it isn't. The
>> kernel mainstream just uses zero as intended not a define for it.
>>
>> Alan
>
> Ahh... maybe I see, it's only defined in ARM and that's what I was building
> for. I'm a little slow sometimes, but I'll get there.
>
> Gotcha, replace with 0. Thanks.
I don't agree with this change. NO_IRQ for microblaze, arm and other is -1. BTW:
For ppc is 0. Using NO_IRQ seems to me reasonable.
you are including linux/irq.h which include asm/irq.h for all platforms except
s390. I think that is better to find out where the real problem is instead of
using any hardcoded value.
If I look at xuartps_get_port function then you don't even need to initialize it
to NO_IRQ because if there is no IRQ connected driver is not probed. That's why
"port->irq = res2->start;" is enough.
I would suggest to completely remove that line from xuartps_get_port
Michal
--
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
next prev parent reply other threads:[~2011-05-06 12:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 18:17 [PATCH V4] tty/serial: add support for Xilinx PS UART johnlinn
2011-04-27 18:17 ` johnlinn
2011-04-27 20:40 ` Alan Cox
2011-04-27 20:40 ` Alan Cox
2011-04-27 20:57 ` johnlinn
2011-04-29 21:14 ` Greg KH
2011-04-29 21:14 ` Greg KH
2011-04-29 21:29 ` johnlinn
2011-04-29 21:29 ` johnlinn
2011-04-29 21:32 ` Alan Cox
2011-04-29 21:41 ` johnlinn
2011-05-06 12:11 ` Michal Simek [this message]
2011-05-06 12:23 ` Alan Cox
2011-05-06 16:41 ` Grant Likely
2011-04-29 22:02 ` johnlinn
2011-04-29 22:02 ` johnlinn
2011-04-29 23:29 ` Greg KH
2011-04-29 23:29 ` Greg KH
[not found] <681890114.2094084.1304112868616.JavaMail.root@sz0140a.emeryville.ca.mail.comcast.net>
2011-04-29 21:35 ` johnlinn
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=4DC3E580.9090500@petalogix.com \
--to=michal.simek@petalogix.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=grant.likely@secretlab.ca \
--cc=greg@kroah.com \
--cc=joe@perches.com \
--cc=john.linn@xilinx.com \
--cc=johnlinn@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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.