mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Michal Simek <michal.simek@xilinx.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"monstr@monstr.eu" <monstr@monstr.eu>,
	Borsodi Petr <Petr.Borsodi@i.cz>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [PATCH] gpio: Wakeup gpio controller when it is used as IRQ controller
Date: Mon, 16 Oct 2017 15:40:28 +0200	[thread overview]
Message-ID: <c50a9e0c-2bba-aa54-0c9a-8551bc0e180c@xilinx.com> (raw)
In-Reply-To: <CACRpkdaQZiyfbBQh-CZZuiw96iqA6bZvN+V7HddJZcR7yz4Cmw@mail.gmail.com>

Hi Linus,

On 21.9.2017 14:19, Linus Walleij wrote:
> On Wed, Sep 20, 2017 at 10:07 PM, Grygorii Strashko
> <grygorii.strashko@ti.com> wrote:
>> On 09/20/2017 02:14 AM, Michal Simek wrote:
>>> From: Borsodi Petr <Petr.Borsodi@i.cz>
>>>
>>> There is a problem with GPIO driver when used as IRQ controller.
>>> It is not working because the module is sleeping (clock is disabled).
>>> The patch enables clocks when IP is used as IRQ controller.
>>
>> I think, it should be solved already in genirq core.
>> commit be45beb "genirq: Add runtime power management support for IRQ chips"
> 
> Michal, can you verify?

sorry for delay. I have just confirmed that this patch is not needed.
At least I am not able to replicate the issue again that's why please
skip this patch.

Thanks,
Michal

  reply	other threads:[~2017-10-16 13:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20  7:14 Michal Simek
2017-09-20 20:07 ` Grygorii Strashko
2017-09-21 12:19   ` Linus Walleij
2017-10-16 13:40     ` Michal Simek [this message]
2017-09-22  0:08 ` kbuild test robot

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=c50a9e0c-2bba-aa54-0c9a-8551bc0e180c@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=Petr.Borsodi@i.cz \
    --cc=grygorii.strashko@ti.com \
    --cc=jonathanh@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monstr@monstr.eu \
    /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
all inboxes | Powered by JetHome®