From: Damien Le Moal <dlemoal@kernel.org>
To: Manivannan Sadhasivam <mani@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>
Cc: manivannan.sadhasivam@oss.qualcomm.com,
Bjorn Helgaas <bhelgaas@google.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Niklas Cassel <cassel@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Stephan Gerhold <stephan.gerhold@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
linux-pm@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH v5 5/5] power: sequencing: Add the Power Sequencing driver for the PCIe M.2 connectors
Date: Fri, 9 Jan 2026 10:02:10 +0100 [thread overview]
Message-ID: <375ea14c-b089-4ae4-9827-5c19139f69c4@kernel.org> (raw)
In-Reply-To: <xd5uvfqcx3vcbcqerji556ejstmgvtci4chfzxclkzhizqmqxa@xusf2skt6xhh>
On 1/9/26 07:02, Manivannan Sadhasivam wrote:
> On Thu, Jan 08, 2026 at 01:15:12PM +0100, Bartosz Golaszewski wrote:
>> On Wed, Jan 7, 2026 at 3:11 PM Manivannan Sadhasivam via B4 Relay
>> <devnull+manivannan.sadhasivam.oss.qualcomm.com@kernel.org> wrote:
>>>
>>> From: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
>>>
>>> This driver is used to control the PCIe M.2 connectors of different
>>> Mechanical Keys attached to the host machines and supporting different
>>> interfaces like PCIe/SATA, USB/UART etc...
>>>
>>> Currently, this driver supports only the Mechanical Key M connectors with
>>> PCIe interface. The driver also only supports driving the mandatory 3.3v
>>> and optional 1.8v power supplies. The optional signals of the Key M
>>> connectors are not currently supported.
>>>
>>> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
>>
>> This looks good to me, though there are some nits I may fix when applying.
>>
>> I'll pick it up for v7.0 once the bindings are reviewed.
>>
>
> Ok. I'm expecting patch 1 to go through ATA tree, patch 2 through DT, and
> patches 3,4 through PCI tree.
Patch 1 seems to be completely unrelated to the power changes, so please send it
to the ata list separately. It is otherwise very complicated and confusing for
everyone to have patches from one series being applied through multiple trees.
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2026-01-09 9:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 14:11 [PATCH v5 0/5] PCI: Add initial support for handling PCIe M.2 connectors in devicetree Manivannan Sadhasivam via B4 Relay
2026-01-07 14:11 ` [PATCH v5 1/5] dt-bindings: ata: sata: Document the graph port Manivannan Sadhasivam via B4 Relay
2026-01-13 16:37 ` Rob Herring (Arm)
2026-01-14 10:31 ` Damien Le Moal
2026-01-07 14:11 ` [PATCH v5 2/5] dt-bindings: connector: Add PCIe M.2 Mechanical Key M connector Manivannan Sadhasivam via B4 Relay
2026-01-13 16:37 ` Rob Herring
2026-01-13 16:48 ` Manivannan Sadhasivam
2026-01-07 14:11 ` [PATCH v5 3/5] PCI/pwrctrl: Add support for handling PCIe M.2 connectors Manivannan Sadhasivam via B4 Relay
2026-01-07 14:11 ` [PATCH v5 4/5] PCI/pwrctrl: Create pwrctrl device if the graph port is found Manivannan Sadhasivam via B4 Relay
2026-01-07 14:11 ` [PATCH v5 5/5] power: sequencing: Add the Power Sequencing driver for the PCIe M.2 connectors Manivannan Sadhasivam via B4 Relay
2026-01-08 12:15 ` Bartosz Golaszewski
2026-01-09 6:02 ` Manivannan Sadhasivam
2026-01-09 8:24 ` Bartosz Golaszewski
2026-01-09 9:02 ` Damien Le Moal [this message]
2026-01-12 7:58 ` Manivannan Sadhasivam
2026-01-07 14:36 ` [PATCH v5 0/5] PCI: Add initial support for handling PCIe M.2 connectors in devicetree Niklas Cassel
2026-01-07 16:48 ` 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=375ea14c-b089-4ae4-9827-5c19139f69c4@kernel.org \
--to=dlemoal@kernel.org \
--cc=bhelgaas@google.com \
--cc=brgl@kernel.org \
--cc=cassel@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mani@kernel.org \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=stephan.gerhold@linaro.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