From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Vineet.Gupta1@synopsys.com" <Vineet.Gupta1@synopsys.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"alan@linux.intel.com" <alan@linux.intel.com>
Subject: Re: [PATCH v2] serial/8250_dw: use platform_get_irq() instead of platform_get_resource()
Date: Tue, 3 Mar 2015 15:33:41 +0000 [thread overview]
Message-ID: <1425396820.17965.16.camel@synopsys.com> (raw)
In-Reply-To: <1425396362.14897.143.camel@linux.intel.com>
Hi Andy,
On Tue, 2015-03-03 at 17:26 +0200, Andy Shevchenko wrote:
> On Tue, 2015-03-03 at 18:11 +0300, Alexey Brodkin wrote:
> > It is not recommened to use platform_get_resource(pdev, IORESOURCE_IRQ)
> > for requesting IRQ's resources any more, as they can be not ready yet in
> > case of DT-booting.
> >
> > platform_get_irq() instead is a recommended way for getting IRQ even if
> > it was not retrieved earlier.
> >
> > It also makes code simpler because we're getting "int" value right away
> > and no conversion from resource to int is required.
> >
> > Changes in v2:
> > * Suppress error message if platform_get_irq() returns -EPROBE_DEFER
>
> Do we really need that message at all?
IMHO it makes sense.
For example it was useful for me when debugging stacked interrupt
controllers setup - I got explicitly notified why this particular device
failed on probe.
Note that IRQ is a pretty specific resource due to the fact of INTC
stacking and situations when each and every INTC gets finally probed.
Still if you believe we may drop this message with no loss of usability
- I'm fine with that as well.
-Alexey
next prev parent reply other threads:[~2015-03-03 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 15:11 [PATCH v2] serial/8250_dw: use platform_get_irq() instead of platform_get_resource() Alexey Brodkin
2015-03-03 15:26 ` Andy Shevchenko
2015-03-03 15:33 ` Alexey Brodkin [this message]
2015-03-03 15:43 ` Andy Shevchenko
2015-03-03 15:47 ` Alexey Brodkin
2015-03-03 15:59 ` Andy Shevchenko
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=1425396820.17965.16.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=alan@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--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 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).