From: Rahul Samana <rahul.samana@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Rob Herring <robh@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_hbandi@quicinc.com, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, quic_anubhavg@quicinc.com,
quic_mohamull@quicinc.com,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH 2/3] arm64: dts: qcom: kodiak: mark PCIe root port as bridge
Date: Fri, 24 Jul 2026 13:32:12 +0530 [thread overview]
Message-ID: <7bc5d5cb-7f35-4eee-9e3a-695fcd39db6b@oss.qualcomm.com> (raw)
In-Reply-To: <6a30c443-ed57-4443-aa34-f6bbe5049370@kernel.org>
On 24-07-2026 01:01, Krzysztof Kozlowski wrote:
> On 23/07/2026 14:31, Rahul Samana wrote:
>> Add the PCI class compatible to pcie0_port so child nodes below the PCI
>> bridge can be matched against the enumerated PCI topology.
>>
>> This is needed by the M.2 E-key graph description used by the RB3 Gen 2
>> Industrial mezzanine Bluetooth UART overlay.
>
> NAK, there is no such overlay.
>
> Best regards,
> Krzysztof
Hi Dmitry, Krzysztof,
Ack, I will rework this patch in v2.
For the commit message, I will explain the reason first and then describe
the actual change.
For the overlay reference, I was referring to patch 3 in this same series,
but I agree the commit message should not justify the SoC dtsi change by
referring to a board overlay. I will make this patch stand on its own by
explaining that compatible = "pciclass,0604" is needed on the pcie0_port
node in kodiak.dtsi to allow the PCI subsystem to associate the DT node
with the PCI-to-PCI bridge device.
Thanks,
Rahul
next prev parent reply other threads:[~2026-07-24 8:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260723-rb3-industrial-bt-uart-v1-0-3c8e580c09d1@oss.qualcomm.com>
[not found] ` <20260723-rb3-industrial-bt-uart-v1-1-3c8e580c09d1@oss.qualcomm.com>
2026-07-23 15:46 ` Bluetooth: qca: enable QCC2072 on RB3 Gen 2 Industrial Mezz reworked for BT over UART bluez.test.bot
2026-07-23 19:06 ` [PATCH 1/3] Bluetooth: qca: add QCC2072 support Dmitry Baryshkov
2026-07-23 19:26 ` Krzysztof Kozlowski
2026-07-24 7:21 ` Rahul Samana
2026-07-23 19:19 ` Krzysztof Kozlowski
2026-07-24 7:38 ` Rahul Samana
[not found] ` <20260723-rb3-industrial-bt-uart-v1-2-3c8e580c09d1@oss.qualcomm.com>
2026-07-23 19:07 ` [PATCH 2/3] arm64: dts: qcom: kodiak: mark PCIe root port as bridge Dmitry Baryshkov
2026-07-23 19:31 ` Krzysztof Kozlowski
2026-07-24 8:02 ` Rahul Samana [this message]
[not found] ` <20260723-rb3-industrial-bt-uart-v1-3-3c8e580c09d1@oss.qualcomm.com>
2026-07-23 19:10 ` [PATCH 3/3] arm64: dts: qcom: rb3gen2: add Industrial BT UART overlay Dmitry Baryshkov
2026-07-24 8:10 ` Rahul Samana
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=7bc5d5cb-7f35-4eee-9e3a-695fcd39db6b@oss.qualcomm.com \
--to=rahul.samana@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=quic_anubhavg@quicinc.com \
--cc=quic_hbandi@quicinc.com \
--cc=quic_mohamull@quicinc.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox