From: Peter Hurley <peter@hurleysoftware.com>
To: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
Michal Simek <michal.simek@xilinx.com>,
linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Moritz Fischer <moritz.fischer@ettus.com>
Subject: Re: [PATCH LINUX v4 06/13] tty: xuartps: Move request_irq to after setting up the HW
Date: Tue, 15 Dec 2015 15:26:46 -0800 [thread overview]
Message-ID: <5670A1B6.6050708@hurleysoftware.com> (raw)
In-Reply-To: <20151215154136.GU3358@xsjsorenbubuntu>
On 12/15/2015 07:41 AM, Sören Brinkmann wrote:
> On Thu, 2015-12-10 at 01:41PM -0800, Peter Hurley wrote:
>> On 12/05/2015 08:39 PM, Soren Brinkmann wrote:
>>> Request_irq() should be _after_ h/w programming, otherwise an
>>> interrupt could be triggered and in-progress before the h/w has been
>>> setup.
>>
>> Slight misunderstanding. My fault; I should have been more explicit.
>>
>> 1. Any setup necessary for the isr not to be confused and misdirect spurious
>> interrupts (or hang) should be before installing the isr with request_irq()
>> None of this code should trigger an interrupt.
>> 2. Clear pending interrupts
>> 3. Install the isr with request_irq()
>> 4. Enable interrupts
>
> Isn't that what the startup function is doing now - more or less. I
> think 3 and 4 are swapped to release the lock and then do the
> request_irq, but I believe that should be OK.
> The startup function configures the HW. Clears the ISR. Enables the
> intended IRQs and then does the request_irq call.
If the driver enables interrupts before installing the isr with request_irq()
and an interrupt occurs there will the no handler to catch it and EOI the
device.
>> For extra safety, first disable interrupts before starting h/w programming.
>
> It's done within spin_lock_irqsave, which gives us at least locally
> disabled IRQs. I guess we could add a disabling all IRQs in the UART
> core, but it should not really be necessary.
Similar issue.
What I mean is to mask interrupts from this device so that h/w programming
doesn't accidentally trigger an interrupt for which no isr is installed.
It's a bit overkill; that's why I said "extra safety".
Regards,
Peter Hurley
>> I would do the v5 series in the same order as the v3 series only up to
>> what I reviewed. Then do another series with the remainder plus new changes, ok?
>
> Sure.
>
> Sören
>
>>
>> Regards,
>> Peter Hurley
>>
>>> Reported-by: Peter Hurley <peter@hurleysoftware.com>
>>> Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com>
>>> ---
>>> v4:
>>> - this patch has been added. Thanks to Peter for pointing it out and providing
>>> commit message
>>> ---
>>> drivers/tty/serial/xilinx_uartps.c | 9 ++-------
>>> 1 file changed, 2 insertions(+), 7 deletions(-)
>>>
>>> diff --git a/drivers/tty/serial/xilinx_uartps.c b/drivers/tty/serial/xilinx_uartps.c
>>> index 6ffd3bbe3e18..1e9053656610 100644
>>> --- a/drivers/tty/serial/xilinx_uartps.c
>>> +++ b/drivers/tty/serial/xilinx_uartps.c
>>> @@ -759,12 +759,7 @@ static void cdns_uart_set_termios(struct uart_port *port,
>>> static int cdns_uart_startup(struct uart_port *port)
>>> {
>>> unsigned long flags;
>>> - unsigned int retval = 0, status = 0;
>>> -
>>> - retval = request_irq(port->irq, cdns_uart_isr, 0, CDNS_UART_NAME,
>>> - (void *)port);
>>> - if (retval)
>>> - return retval;
>>> + unsigned int status = 0;
>>>
>>> spin_lock_irqsave(&port->lock, flags);
>>>
>>> @@ -818,7 +813,7 @@ static int cdns_uart_startup(struct uart_port *port)
>>>
>>> spin_unlock_irqrestore(&port->lock, flags);
>>>
>>> - return retval;
>>> + return request_irq(port->irq, cdns_uart_isr, 0, CDNS_UART_NAME, port);
>>> }
>>>
>>> /**
>>>
>>
next prev parent reply other threads:[~2015-12-15 23:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 4:39 [PATCH LINUX v4 00/13] tty: xuartps: Fix lock ups Soren Brinkmann
2015-12-06 4:39 ` [PATCH LINUX v4 01/13] tty: xuartps: Beautify read-modify writes Soren Brinkmann
2015-12-06 4:39 ` [PATCH LINUX v4 02/13] tty: xuartps: Use spinlock to serialize HW access Soren Brinkmann
2015-12-06 4:39 ` [PATCH LINUX v4 03/13] tty: xuartps: Don't consider circular buffer when enabling transmitter Soren Brinkmann
2015-12-06 4:39 ` [PATCH LINUX v4 04/13] tty: xuartps: Clear interrupt status register in shutdown Soren Brinkmann
2015-12-06 4:39 ` [PATCH LINUX v4 05/13] tty: xuartps: Improve startup function Soren Brinkmann
2015-12-06 4:39 ` [PATCH LINUX v4 06/13] tty: xuartps: Move request_irq to after setting up the HW Soren Brinkmann
2015-12-10 21:41 ` Peter Hurley
2015-12-15 15:41 ` Sören Brinkmann
2015-12-15 23:26 ` Peter Hurley [this message]
2015-12-16 9:03 ` Sören Brinkmann
2015-12-16 14:37 ` Peter Hurley
2015-12-17 10:00 ` Sören Brinkmann
2015-12-06 4:39 ` [PATCH LINUX v4 07/13] tty: xuartps: Keep lock for whole ISR Soren Brinkmann
2015-12-06 4:39 ` [PATCH LINUX v4 08/13] tty: xuartps: Acquire port lock for shutdown Soren Brinkmann
2015-12-06 4:39 ` [PATCH LINUX v4 09/13] tty: xuartps: Move RX path into helper function Soren Brinkmann
2015-12-06 4:39 ` [PATCH LINUX v4 10/13] tty: xuartps: Refactor IRQ handling Soren Brinkmann
2015-12-06 4:39 ` [PATCH LINUX v4 11/13] tty: xuartps: Cleanup: Reformat if-else Soren Brinkmann
2015-12-06 4:39 ` [PATCH LINUX v4 12/13] tty: xuartps: Improve sysrq handling Soren Brinkmann
2015-12-06 4:39 ` [PATCH LINUX v4 13/13] tty: xuartps: Remove '_OFFSET' suffix from #defines Soren Brinkmann
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=5670A1B6.6050708@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=moritz.fischer@ettus.com \
--cc=soren.brinkmann@xilinx.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;
as well as URLs for NNTP newsgroup(s).