From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Samuel Mendoza-Jonas <sam@mendozajonas.com>, linuxppc-dev@ozlabs.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
"# 4 . 1 . x-" <stable@vger.kernel.org>,
Alistair Popple <alistair@popple.id.au>
Subject: Re: [PATCH 2/2] tty/hvc: Use opal irqchip interface if available
Date: Tue, 28 Jun 2016 13:35:12 +1000 [thread overview]
Message-ID: <1467084912.20278.117.camel@kernel.crashing.org> (raw)
In-Reply-To: <1467084869.20278.116.camel@kernel.crashing.org>
On Tue, 2016-06-28 at 13:34 +1000, Benjamin Herrenschmidt wrote:
> On Tue, 2016-06-28 at 13:11 +1000, Samuel Mendoza-Jonas wrote:
> > Update the hvc driver to use the OPAL irqchip if made available by
> > the
> > running firmware. If it is not present, the driver falls back to
> > the
> > existing OPAL event number.
>
> One thing that worries me a bit with the original transition to using
> an interrupt from the old OPAL callback is that when passed an
> interrupt,
> the HVC thread assumes interrupts work reliably and thus stops
> polling.
Note to Greg: This patch is fine, this is a reflexion about a change
that was already done.
> However, not all platforms have a functional serial interrupt. For
> example rhesus doesn't. In fact we don't always know when we build
> the device-tree whether the serial interrupt will work or not.
>
> Now we might be saved by the OPAL heartbeat ... we do call
> opal_poll_events regularily there. But I'd like you to verify it
> by disabling the LPC interrupt for example on an openpower machine
> and see how the console beahves.
>
> Cheers,
> Ben.
>
>
> > Signed-off-by: Samuel Mendoza-Jonas <sam@mendozajonas.com>
> > Cc: <stable@vger.kernel.org> # 4.1.x-
> > ---
> > drivers/tty/hvc/hvc_opal.c | 12 +++++++++++-
> > 1 file changed, 11 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/tty/hvc/hvc_opal.c
> > b/drivers/tty/hvc/hvc_opal.c
> > index b7cd0ae..8c53f5b 100644
> > --- a/drivers/tty/hvc/hvc_opal.c
> > +++ b/drivers/tty/hvc/hvc_opal.c
> > @@ -170,6 +170,8 @@ static int hvc_opal_probe(struct
> > platform_device *dev)
> > hv_protocol_t proto;
> > unsigned int termno, irq, boot = 0;
> > const __be32 *reg;
> > + u32 prop;
> > + int rc;
> >
> > if (of_device_is_compatible(dev->dev.of_node, "ibm,opal-
> > console-raw")) {
> > proto = HV_PROTOCOL_RAW;
> > @@ -214,7 +216,15 @@ static int hvc_opal_probe(struct
> > platform_device *dev)
> > dev->dev.of_node->full_name,
> > boot ? " (boot console)" : "");
> >
> > - irq = opal_event_request(ilog2(OPAL_EVENT_CONSOLE_INPUT));
> > + rc = of_property_read_u32(dev->dev.of_node, "interrupts",
> > &prop);
> > + if (rc) {
> > + pr_info("hvc%d: No interrupts property, using OPAL
> > event\n",
> > + termno);
> > + irq =
> > opal_event_request(ilog2(OPAL_EVENT_CONSOLE_INPUT));
> > + } else {
> > + irq = irq_of_parse_and_map(dev->dev.of_node, 0);
> > + }
> > +
> > if (!irq) {
> > pr_err("hvc_opal: Unable to map interrupt for
> > device %s\n",
> > dev->dev.of_node->full_name);
next prev parent reply other threads:[~2016-06-28 4:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 3:11 [PATCH 1/2] tty/hvc: Use IRQF_SHARED for OPAL hvc consoles Samuel Mendoza-Jonas
2016-06-28 3:11 ` [PATCH 2/2] tty/hvc: Use opal irqchip interface if available Samuel Mendoza-Jonas
2016-06-28 3:34 ` Benjamin Herrenschmidt
2016-06-28 3:35 ` Benjamin Herrenschmidt [this message]
2016-07-05 5:31 ` [2/2] " Michael Ellerman
2016-07-05 6:07 ` Samuel Mendoza-Jonas
2016-07-06 9:51 ` Michael Ellerman
2016-07-05 5:34 ` [1/2] tty/hvc: Use IRQF_SHARED for OPAL hvc consoles Michael Ellerman
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=1467084912.20278.117.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=alistair@popple.id.au \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sam@mendozajonas.com \
--cc=stable@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).