From: Tony Lindgren <tony@atomide.com>
To: Dhruva Gole <d-gole@ti.com>
Cc: linux-omap@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] bus: ti-sysc: Drop legacy quirk handling for smartreflex
Date: Thu, 28 Mar 2024 13:34:05 +0200 [thread overview]
Message-ID: <20240328113405.GH5132@atomide.com> (raw)
In-Reply-To: <20240328112351.e7klcl7zjz6uov2j@dhruva>
* Dhruva Gole <d-gole@ti.com> [240328 11:23]:
> Hi,
>
> On Mar 27, 2024 at 10:15:07 +0200, Tony Lindgren wrote:
> > With the smartreflex driver no longer relying on the use of
> > pm_runtime_irq_safe(), we can finally drop the related legacy quirk
> > handling.
>
> Just for some more context can you describe from which commit of
> smartreflex driver did this happen?
That happened earlier with commit ed4520d6a10b ("soc: ti: Remove
pm_runtime_irq_safe() usage for smartreflex").
Regards,
Tony
next prev parent reply other threads:[~2024-03-28 11:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 8:15 [PATCH 0/5] Updates for ti-sysc interconnect target driver Tony Lindgren
2024-03-27 8:15 ` [PATCH 1/5] bus: ti-sysc: Move check for no-reset-on-init Tony Lindgren
2024-03-27 8:15 ` [PATCH 2/5] bus: ti-sysc: Add a description and copyrights Tony Lindgren
2024-03-28 11:19 ` Dhruva Gole
2024-03-28 11:36 ` Greg Kroah-Hartman
2024-03-28 11:47 ` Dhruva Gole
2024-03-28 11:38 ` Tony Lindgren
2024-03-27 8:15 ` [PATCH 3/5] bus: ti-sysc: Drop legacy quirk handling for uarts Tony Lindgren
2024-03-27 8:15 ` [PATCH 4/5] bus: ti-sysc: Drop legacy quirk handling for smartreflex Tony Lindgren
2024-03-28 11:23 ` Dhruva Gole
2024-03-28 11:34 ` Tony Lindgren [this message]
2024-03-27 8:15 ` [PATCH 5/5] bus: ti-sysc: Drop legacy idle quirk handling Tony Lindgren
2024-03-28 11:28 ` Dhruva Gole
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=20240328113405.GH5132@atomide.com \
--to=tony@atomide.com \
--cc=d-gole@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.