From: Francesco Dolcini <francesco@dolcini.it>
To: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, amitkumar.karwar@nxp.com,
rohit.fule@nxp.com, sherry.sun@nxp.com,
linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: btnxpuart: Enable Power Save feature on startup
Date: Mon, 4 Mar 2024 20:29:52 +0100 [thread overview]
Message-ID: <20240304192952.GA17410@francesco-nb> (raw)
In-Reply-To: <20240304170753.500074-1-neeraj.sanjaykale@nxp.com>
On Mon, Mar 04, 2024 at 10:37:53PM +0530, Neeraj Sanjay Kale wrote:
> This sets the default power save mode setting to enabled.
>
> The power save feature is now stable and stress test issues, such as the
> TX timeout error, have been resolved.
I assume that the stability issue has been fixed in firmware, correct?
What's going to happen if running the updated driver with old firmware?
What about combo Wi-Fi/BT firmware files, were those updated? I'm
currently using this driver with this firmware [1]
[1] https://github.com/nxp-imx/imx-firmware/blob/lf-5.15.52_2.1.0/nxp/FwImage_IW416_SD/sdiouartiw416_combo_v0.bin
Francesco
next prev parent reply other threads:[~2024-03-04 19:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 17:07 [PATCH v2] Bluetooth: btnxpuart: Enable Power Save feature on startup Neeraj Sanjay Kale
2024-03-04 17:56 ` [v2] " bluez.test.bot
2024-03-04 19:29 ` Francesco Dolcini [this message]
2024-03-15 13:13 ` [PATCH v2] " Neeraj Sanjay Kale
2024-03-15 15:42 ` Francesco Dolcini
2024-05-10 10:18 ` Neeraj Sanjay Kale
2024-05-10 14:40 ` Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2024-06-14 8:20 Neeraj Sanjay Kale
2024-06-14 17:00 ` patchwork-bot+bluetooth
2024-06-03 6:22 Neeraj Sanjay Kale
2024-05-14 9:02 Neeraj Sanjay Kale
2024-05-17 7:17 ` Neeraj Sanjay Kale
2024-01-11 10:11 Neeraj Sanjay Kale
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=20240304192952.GA17410@francesco-nb \
--to=francesco@dolcini.it \
--cc=amitkumar.karwar@nxp.com \
--cc=johan.hedberg@gmail.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=rohit.fule@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.