From: Krzysztof Kozlowski <krzk@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
bjorn.andersson@oss.qualcomm.com, konradybcio@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-pci@vger.kernel.org, wenst@chromium.org, arnd@arndb.de,
mani@kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v2] arm64: defconfig: Enable PCI M.2 power sequencing driver
Date: Wed, 13 May 2026 21:41:42 +0200 [thread overview]
Message-ID: <d04d7187-54ba-4ba7-b7d3-131fd4f3a98f@kernel.org> (raw)
In-Reply-To: <20260501164440.11788-1-manivannan.sadhasivam@oss.qualcomm.com>
On 01/05/2026 18:44, Manivannan Sadhasivam wrote:
> POWER_SEQUENCING_PCIE_M2 driver handles power supply to the PCIe M.2
> connectors and is required on wide variety of ARM64 platforms such as
> Qcom Snapdragon X Elite laptops and Mediatek Dojo Chromebooks.
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
> ---
>
> Changes in v2:
>
> * Dropped PCI_PWRCTRL_GENERIC change since it was already applied
> * Reworded commit message to include ARM64 platforms making use of this driver
> * Added R-b tag
>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
CC list suggests this will go via Bjorn's tree, but I think it did not
happen. Can you double check no one picked it up and send it to the
soc@lists.linux.dev in such case?
Best regards,
Krzysztof
next parent reply other threads:[~2026-05-13 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260501164440.11788-1-manivannan.sadhasivam@oss.qualcomm.com>
2026-05-13 19:41 ` Krzysztof Kozlowski [this message]
2026-05-14 6:46 ` [PATCH v2] arm64: defconfig: Enable PCI M.2 power sequencing driver Manivannan Sadhasivam
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=d04d7187-54ba-4ba7-b7d3-131fd4f3a98f@kernel.org \
--to=krzk@kernel.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@kernel.org \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=wenst@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox