platform-driver-x86.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "tiantao (H)" <tiantao6@huawei.com>
To: Hans de Goede <hdegoede@redhat.com>,
	Tian Tao <tiantao6@hisilicon.com>, <luzmaximilian@gmail.com>,
	<mgross@linux.intel.com>, Thomas Gleixner <tglx@linutronix.de>
Cc: <platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH] platform/surface: aggregator: move to use request_irq by IRQF_NO_AUTOEN flag
Date: Wed, 7 Apr 2021 20:30:56 +0800	[thread overview]
Message-ID: <6e1db99e-8d12-dcd0-536d-7d205117f6b4@huawei.com> (raw)
In-Reply-To: <ddaed29b-f788-fed9-2522-8b2b3d1f46ec@redhat.com>


在 2021/4/7 17:51, Hans de Goede 写道:
> Hi,
>
> On 4/7/21 9:00 AM, Tian Tao wrote:
>> disable_irq() after request_irq() still has a time gap in which
>> interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
>> disable IRQ auto-enable because of requesting.
> Thank you for your patch, it is good to see the issue of there not
> being a simply way to request IRQs in a way where they are initially
> disabled being solved.
>
>> this patch is made base on "add IRQF_NO_AUTOEN for request_irq" which
>> is being merged: https://lore.kernel.org/patchwork/patch/1388765/
> So this is not yet in Linus' tree. When you write "which is being merged",
> I assume that means that this is going upstream in the 5.13 window.
this is already in linux-next.git.

cbe16f3 genirq: Add IRQF_NO_AUTOEN for request_irq/nmi()
>
> So what is the plan to merge follow-up patches using the new API which
> the "add IRQF_NO_AUTOEN for request_irq" patch introduces?
>
> Will there be an immutable branch provided with that patch which other
> subsystem maintainers can merge ?
>
> Regards,
>
> Hans
>
>
>
>
>> Signed-off-by: Tian Tao <tiantao6@hisilicon.com>
>> ---
>>   drivers/platform/surface/aggregator/controller.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/platform/surface/aggregator/controller.c b/drivers/platform/surface/aggregator/controller.c
>> index aa6f37b..00e3828 100644
>> --- a/drivers/platform/surface/aggregator/controller.c
>> +++ b/drivers/platform/surface/aggregator/controller.c
>> @@ -2483,7 +2483,8 @@ int ssam_irq_setup(struct ssam_controller *ctrl)
>>   	 * interrupt, and let the SAM resume callback during the controller
>>   	 * resume process clear it.
>>   	 */
>> -	const int irqf = IRQF_SHARED | IRQF_ONESHOT | IRQF_TRIGGER_RISING;
>> +	const int irqf = IRQF_SHARED | IRQF_ONESHOT |
>> +			 IRQF_TRIGGER_RISING | IRQF_NO_AUTOEN;
>>   
>>   	gpiod = gpiod_get(dev, "ssam_wakeup-int", GPIOD_ASIS);
>>   	if (IS_ERR(gpiod))
>> @@ -2501,7 +2502,6 @@ int ssam_irq_setup(struct ssam_controller *ctrl)
>>   		return status;
>>   
>>   	ctrl->irq.num = irq;
>> -	disable_irq(ctrl->irq.num);
>>   	return 0;
>>   }
>>   
>>
> .
>


  reply	other threads:[~2021-04-07 12:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07  7:00 [PATCH] platform/surface: aggregator: move to use request_irq by IRQF_NO_AUTOEN flag Tian Tao
2021-04-07  8:39 ` Maximilian Luz
2021-04-07  9:51 ` Hans de Goede
2021-04-07 12:30   ` tiantao (H) [this message]
2021-04-07 12:34     ` Hans de Goede
2021-04-07 18:05 ` Hans de Goede

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=6e1db99e-8d12-dcd0-536d-7d205117f6b4@huawei.com \
    --to=tiantao6@huawei.com \
    --cc=hdegoede@redhat.com \
    --cc=luzmaximilian@gmail.com \
    --cc=mgross@linux.intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tiantao6@hisilicon.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).