public inbox for linux-arm-msm@vger.kernel.org
 help / color / mirror / Atom feed
From: Akash Asthana <akashast@codeaurora.org>
To: Stephen Boyd <swboyd@chromium.org>, gregkh@linuxfoundation.org
Cc: linux-arm-msm@vger.kernel.org, linux-serial@vger.kernel.org,
	mgautam@codeaurora.org, bjorn.andersson@linaro.org
Subject: Re: [PATCH V2 1/2] tty: serial: qcom_geni_serial: IRQ cleanup
Date: Fri, 11 Oct 2019 13:09:06 +0530	[thread overview]
Message-ID: <010dd569-d172-fdcf-0bfa-8caaf41a4d46@codeaurora.org> (raw)
In-Reply-To: <5d9f3dfa.1c69fb81.84c4b.30bf@mx.google.com>


On 10/10/2019 7:49 PM, Stephen Boyd wrote:
> Quoting Akash Asthana (2019-10-10 02:46:03)
>> diff --git a/drivers/tty/serial/qcom_geni_serial.c b/drivers/tty/serial/qcom_geni_serial.c
>> index 14c6306..5180cd8 100644
>> --- a/drivers/tty/serial/qcom_geni_serial.c
>> +++ b/drivers/tty/serial/qcom_geni_serial.c
>> @@ -1297,11 +1291,21 @@ static int qcom_geni_serial_probe(struct platform_device *pdev)
>>          port->rx_fifo_depth = DEF_FIFO_DEPTH_WORDS;
>>          port->tx_fifo_width = DEF_FIFO_WIDTH_BITS;
>>   
>> +       scnprintf(port->name, sizeof(port->name), "qcom_geni_serial_%s%d",
>> +               (uart_console(uport) ? "console" : "uart"), uport->line);
> Drop useless parenthesis. Also, it might make more sense to make this a
> devm_kasprintf() call now.

OK

>>          irq = platform_get_irq(pdev, 0);
>>          if (irq < 0)
>>                  return irq;
>>          uport->irq = irq;
>>   
>> +       irq_set_status_flags(uport->irq, IRQ_NOAUTOEN);
> Is there a reason why we can't always leave the irq enabled and request
> it later once the uart structure has been fully initialized?

According to current design we are requesting IRQ handler in probe, and 
we enable and disable it from the startup(port open) and shutdown(port 
close) function respectively.

We need to call for disable_irq in shutdown function because client has 
closed the port and we don't expect any transfer requests after it.

>>request it later once the uart structure has been fully initialized?

     Is the ask is to move request irq later in probe after the uport is 
fully initialized?

>> +       ret = devm_request_irq(uport->dev, uport->irq, qcom_geni_serial_isr,
>> +                       IRQF_TRIGGER_HIGH, port->name, uport);
>> +       if (ret) {
>> +               dev_err(uport->dev, "Failed to get IRQ ret %d\n", ret);
>> +               return ret;
>> +       }
>> +
>>          uport->private_data = drv;
>>          platform_set_drvdata(pdev, port);
>>          port->handle_rx = console ? handle_rx_console : handle_rx_uart;

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,\na Linux Foundation Collaborative Project


  reply	other threads:[~2019-10-11  7:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10  9:46 [PATCH V2 1/2] tty: serial: qcom_geni_serial: IRQ cleanup Akash Asthana
2019-10-10 14:19 ` Stephen Boyd
2019-10-11  7:39   ` Akash Asthana [this message]
2019-10-15 20:11     ` Stephen Boyd
2019-10-17 11:10       ` Akash Asthana

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=010dd569-d172-fdcf-0bfa-8caaf41a4d46@codeaurora.org \
    --to=akashast@codeaurora.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=mgautam@codeaurora.org \
    --cc=swboyd@chromium.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