All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	amitkumar.karwar@nxp.com, sherry.sun@nxp.com
Subject: Re: [PATCH v2] Bluetooth: btnxpuart: Uses threaded IRQ for host wakeup handling
Date: Mon, 11 Aug 2025 16:40:06 +0000	[thread overview]
Message-ID: <175493040649.1801125.3657849160282054995.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250804103015.1104289-1-neeraj.sanjaykale@nxp.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Mon,  4 Aug 2025 16:00:15 +0530 you wrote:
> This replaces devm_request_irq() with devm_request_threaded_irq().
> 
> On iMX93 11x11 EVK platform, the BT chip's BT_WAKE_OUT pin is connected
> to an I2C GPIO expander instead of directly been connected to iMX GPIO.
> 
> When I2C GPIO expander's (PCAL6524) host driver receives an interrupt on
> it's INTR line, the driver's interrupt handler needs to query the
> interrupt source with PCAL6524 first, and then call the actual interrupt
> handler, in this case the IRQ handler in BTNXPUART.
> 
> [...]

Here is the summary with links:
  - [v2] Bluetooth: btnxpuart: Uses threaded IRQ for host wakeup handling
    https://git.kernel.org/bluetooth/bluetooth-next/c/3f9a516852b6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-08-11 16:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04 10:30 [PATCH v2] Bluetooth: btnxpuart: Uses threaded IRQ for host wakeup handling Neeraj Sanjay Kale
2025-08-04 11:10 ` [v2] " bluez.test.bot
2025-08-06  7:02 ` [PATCH v2] " Sherry Sun
2025-08-11 16:40 ` patchwork-bot+bluetooth [this message]

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=175493040649.1801125.3657849160282054995.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=amitkumar.karwar@nxp.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=neeraj.sanjaykale@nxp.com \
    --cc=sherry.sun@nxp.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 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.