From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [GIT PULL] Immutable tag between the Bluetooth and pwrseq branches for v6.11-rc1
Date: Wed, 12 Jun 2024 09:58:29 +0200 [thread overview]
Message-ID: <20240612075829.18241-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Hi Marcel, Luiz,
Please pull the following power sequencing changes into the Bluetooth tree
before applying the hci_qca patches I sent separately.
Link: https://lore.kernel.org/linux-kernel/20240605174713.GA767261@bhelgaas/T/
The following changes since commit 83a7eefedc9b56fe7bfeff13b6c7356688ffa670:
Linux 6.10-rc3 (2024-06-09 14:19:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/pwrseq-initial-for-v6.11
for you to fetch changes up to 2f1630f437dff20d02e4b3f07e836f42869128dd:
power: pwrseq: add a driver for the PMU module on the QCom WCN chipsets (2024-06-12 09:20:13 +0200)
----------------------------------------------------------------
Initial implementation of the power sequencing subsystem for linux v6.11
----------------------------------------------------------------
Bartosz Golaszewski (2):
power: sequencing: implement the pwrseq core
power: pwrseq: add a driver for the PMU module on the QCom WCN chipsets
MAINTAINERS | 8 +
drivers/power/Kconfig | 1 +
drivers/power/Makefile | 1 +
drivers/power/sequencing/Kconfig | 29 +
drivers/power/sequencing/Makefile | 6 +
drivers/power/sequencing/core.c | 1105 ++++++++++++++++++++++++++++
drivers/power/sequencing/pwrseq-qcom-wcn.c | 336 +++++++++
include/linux/pwrseq/consumer.h | 56 ++
include/linux/pwrseq/provider.h | 75 ++
9 files changed, 1617 insertions(+)
create mode 100644 drivers/power/sequencing/Kconfig
create mode 100644 drivers/power/sequencing/Makefile
create mode 100644 drivers/power/sequencing/core.c
create mode 100644 drivers/power/sequencing/pwrseq-qcom-wcn.c
create mode 100644 include/linux/pwrseq/consumer.h
create mode 100644 include/linux/pwrseq/provider.h
next reply other threads:[~2024-06-12 7:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 7:58 Bartosz Golaszewski [this message]
2024-06-12 14:43 ` [GIT PULL] Immutable tag between the Bluetooth and pwrseq branches for v6.11-rc1 Luiz Augusto von Dentz
2024-06-12 14:45 ` Bartosz Golaszewski
2024-06-12 14:54 ` Luiz Augusto von Dentz
2024-06-12 15:00 ` Bartosz Golaszewski
2024-06-19 7:35 ` Bartosz Golaszewski
2024-06-19 18:59 ` Luiz Augusto von Dentz
2024-06-19 19:33 ` Bartosz Golaszewski
2024-06-20 14:16 ` Luiz Augusto von Dentz
2024-06-20 14:18 ` Krzysztof Kozlowski
2024-06-20 14:20 ` Luiz Augusto von Dentz
2024-06-20 14:30 ` Krzysztof Kozlowski
2024-06-20 6:34 ` Krzysztof Kozlowski
2024-06-20 14:30 ` patchwork-bot+bluetooth
2024-06-20 14:35 ` Krzysztof Kozlowski
2024-06-20 14:44 ` Luiz Augusto von Dentz
2024-06-20 14:52 ` Bartosz Golaszewski
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=20240612075829.18241-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=bartosz.golaszewski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@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.