From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Samuel Iglesias Gonsálvez" <siglesias@igalia.com>
Cc: Federico Vaga <federico.vaga@cern.ch>,
Jens Taprogge <jens.taprogge@taprogge.org>,
industrypack-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipoctal: request_irq after configuration
Date: Thu, 3 Jul 2014 13:55:49 -0700 [thread overview]
Message-ID: <20140703205549.GA11109@kroah.com> (raw)
In-Reply-To: <1404377815.4537.20.camel@fourier>
On Thu, Jul 03, 2014 at 10:56:55AM +0200, Samuel Iglesias Gonsálvez wrote:
> On Thu, 2014-07-03 at 10:53 +0200, Federico Vaga wrote:
> > The request for an IRQ handler must be done after whole configuration. This
> > was not the case for this driver which request the IRQ in the middle of
> > the configuration. Sometimes, it happens that something is not completely
> > configured, we recieve an interrupt thus we stumble into troubles in the
> > IRQ handler.
> >
> > Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
> > ---
> > drivers/ipack/devices/ipoctal.c | 15 ++++++++-------
> > 1 file changed, 8 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/ipack/devices/ipoctal.c b/drivers/ipack/devices/ipoctal.c
> > index a7ec6f9..72fd761 100644
> > --- a/drivers/ipack/devices/ipoctal.c
> > +++ b/drivers/ipack/devices/ipoctal.c
> > @@ -344,13 +344,6 @@ static int ipoctal_inst_slot(struct ipoctal *ipoctal, unsigned int bus_nr,
> > &block_regs[i].w.imr);
> > }
> >
> > - /*
> > - * IP-OCTAL has different addresses to copy its IRQ vector.
> > - * Depending of the carrier these addresses are accesible or not.
> > - * More info in the datasheet.
> > - */
> > - ipoctal->dev->bus->ops->request_irq(ipoctal->dev,
> > - ipoctal_irq_handler, ipoctal);
> > /* Dummy write */
> > iowrite8(1, ipoctal->mem8_space + 1);
> >
> > @@ -411,6 +404,14 @@ static int ipoctal_inst_slot(struct ipoctal *ipoctal, unsigned int bus_nr,
> > dev_set_drvdata(tty_dev, channel);
> > }
> >
> > + /*
> > + * IP-OCTAL has different addresses to copy its IRQ vector.
> > + * Depending of the carrier these addresses are accesible or not.
> > + * More info in the datasheet.
> > + */
> > + ipoctal->dev->bus->ops->request_irq(ipoctal->dev,
> > + ipoctal_irq_handler, ipoctal);
> > +
> > return 0;
> > }
> >
>
> Acked-by: Samuel Iglesias Gonsalvez <siglesias@igalia.com>
>
> Greg, Would you mind picking this patch through your driver-core tree?
> Together with "ipoctal: protect only the real critical section" patch.
Ok, will do, thanks.
greg k-h
prev parent reply other threads:[~2014-07-03 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 8:53 [PATCH] ipoctal: request_irq after configuration Federico Vaga
2014-07-03 8:56 ` Samuel Iglesias Gonsálvez
2014-07-03 20:55 ` Greg Kroah-Hartman [this message]
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=20140703205549.GA11109@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=federico.vaga@cern.ch \
--cc=industrypack-devel@lists.sourceforge.net \
--cc=jens.taprogge@taprogge.org \
--cc=linux-kernel@vger.kernel.org \
--cc=siglesias@igalia.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