From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
ath10k@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: net: wireless: qcom,ath10k: add PCI devices
Date: Sat, 14 Nov 2026 08:33:53 +0100 [thread overview]
Message-ID: <a84e2db6-17d5-455a-9b3a-eb3d787ce92c@kernel.org> (raw)
In-Reply-To: <CAKxU2N846Ebd50z8adJsNcy-kJBSNDSKU8_ZLf68fJzoc+r+xA@mail.gmail.com>
On 13/11/2026 22:34, Rosen Penev wrote:
> On Fri, Nov 13, 2026 at 3:11 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On Tue, Nov 10, 2026 at 07:44:18PM -0800, Rosen Penev wrote:
>>> ath10k PCI devices can be described as children of their PCI host
>>> bridge, for example to supply the MAC address and calibration data
>>> through nvmem cells. The only compatible for that was "qcom,ath10k",
>>> but the generic PCI device schema requires a node under a PCI bus to
>>> carry a "pciVVVV,DDDD" or "pciclass,..." compatible, so such nodes fail
>>> validation.
>>>
>>> Add the PCI vendor/device IDs handled by the ath10k PCI driver, as the
>>> ath9k and ath11k PCI bindings already do.
>>
>> We do not need to least all PCI devices here. Were is any actual DTS
>> user of these?
> I have some WIP patches that include the QCA988X. Reason for it is
> nvram calibration and MAC lookup.
>
> This is basically copy/paste of what's already present in ath9k.yaml.
>
> AFAIK this came up because of dtbs_check
It cannot come as dtbs_check result, because there are no DTS with these.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-11-14 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 3:44 [PATCH] dt-bindings: net: wireless: qcom,ath10k: add PCI devices Rosen Penev
2026-11-13 11:11 ` Krzysztof Kozlowski
2026-11-13 21:34 ` Rosen Penev
2026-11-14 7:33 ` Krzysztof Kozlowski [this message]
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=a84e2db6-17d5-455a-9b3a-eb3d787ce92c@kernel.org \
--to=krzk@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jjohnson@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=rosenp@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).