All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH v5 1/3] Documentation: dt: net: add ath9k wireless device binding
Date: Mon, 22 Aug 2016 11:08:56 +0200	[thread overview]
Message-ID: <2913835.hr5kg63Vcv@wuerfel> (raw)
In-Reply-To: <20160821143105.27487-2-martin.blumenstingl@googlemail.com>

On Sunday, August 21, 2016 4:31:03 PM CEST Martin Blumenstingl wrote:
> +pci {
> +       pcie at 0 {
> +               reg = <0 0 0 0 0>;

It's not clear what these two nodes refer to in the example. Is the top-level
node the PCI host bridge, and the second node the first PCIe port?

Maybe add the properties from a real system here to make this a little
clearer.

The unit address for the slot should be "00,0", not "0" here.

> +               #interrupt-cells = <1>;
> +               #size-cells = <2>;
> +               #address-cells = <3>;
> +               device_type = "pci";
> +

I think this needs an empty "ranges" property to be a valid bridge node.

> +               ath9k at 0,0 {

According to the PCI binding, the name should be the same as the
compatible string here, or match the class code in the table.

> +                       compatible = "pci168c,0030";
> +                       reg = <0 0 0 0 0>;

Are the device/fn numbers all zero on your system? This is a bit
confusing, as it's not immediately clear what the reg properties
refers to. Also, I think the length should reflect the actual length
of the config space, either 0x100 or 0x1000.

> +                       qca,disable-5ghz;
> +               };
> +       };
> +};

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: ath9k-devel@lists.ath9k.org, devicetree@vger.kernel.org,
	linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com,
	mcgrof@do-not-panic.com, mark.rutland@arm.com,
	robh+dt@kernel.org, kvalo@codeaurora.org,
	chunkeey@googlemail.com, arend.vanspriel@broadcom.com,
	julian.calaby@gmail.com, bjorn@mork.no, linux@rempel-privat.de
Subject: Re: [PATCH v5 1/3] Documentation: dt: net: add ath9k wireless device binding
Date: Mon, 22 Aug 2016 11:08:56 +0200	[thread overview]
Message-ID: <2913835.hr5kg63Vcv@wuerfel> (raw)
In-Reply-To: <20160821143105.27487-2-martin.blumenstingl@googlemail.com>

On Sunday, August 21, 2016 4:31:03 PM CEST Martin Blumenstingl wrote:
> +pci {
> +       pcie@0 {
> +               reg = <0 0 0 0 0>;

It's not clear what these two nodes refer to in the example. Is the top-level
node the PCI host bridge, and the second node the first PCIe port?

Maybe add the properties from a real system here to make this a little
clearer.

The unit address for the slot should be "00,0", not "0" here.

> +               #interrupt-cells = <1>;
> +               #size-cells = <2>;
> +               #address-cells = <3>;
> +               device_type = "pci";
> +

I think this needs an empty "ranges" property to be a valid bridge node.

> +               ath9k@0,0 {

According to the PCI binding, the name should be the same as the
compatible string here, or match the class code in the table.

> +                       compatible = "pci168c,0030";
> +                       reg = <0 0 0 0 0>;

Are the device/fn numbers all zero on your system? This is a bit
confusing, as it's not immediately clear what the reg properties
refers to. Also, I think the length should reflect the actual length
of the config space, either 0x100 or 0x1000.

> +                       qca,disable-5ghz;
> +               };
> +       };
> +};

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	arend.vanspriel@broadcom.com, mcgrof@do-not-panic.com,
	julian.calaby@gmail.com, linux-wireless@vger.kernel.org,
	ath9k-devel@qca.qualcomm.com, robh+dt@kernel.org,
	ath9k-devel@lists.ath9k.org, bjorn@mork.no,
	chunkeey@googlemail.com, kvalo@codeaurora.org
Subject: Re: [PATCH v5 1/3] Documentation: dt: net: add ath9k wireless device binding
Date: Mon, 22 Aug 2016 11:08:56 +0200	[thread overview]
Message-ID: <2913835.hr5kg63Vcv@wuerfel> (raw)
In-Reply-To: <20160821143105.27487-2-martin.blumenstingl@googlemail.com>

On Sunday, August 21, 2016 4:31:03 PM CEST Martin Blumenstingl wrote:
> +pci {
> +       pcie@0 {
> +               reg = <0 0 0 0 0>;

It's not clear what these two nodes refer to in the example. Is the top-level
node the PCI host bridge, and the second node the first PCIe port?

Maybe add the properties from a real system here to make this a little
clearer.

The unit address for the slot should be "00,0", not "0" here.

> +               #interrupt-cells = <1>;
> +               #size-cells = <2>;
> +               #address-cells = <3>;
> +               device_type = "pci";
> +

I think this needs an empty "ranges" property to be a valid bridge node.

> +               ath9k@0,0 {

According to the PCI binding, the name should be the same as the
compatible string here, or match the class code in the table.

> +                       compatible = "pci168c,0030";
> +                       reg = <0 0 0 0 0>;

Are the device/fn numbers all zero on your system? This is a bit
confusing, as it's not immediately clear what the reg properties
refers to. Also, I think the length should reflect the actual length
of the config space, either 0x100 or 0x1000.

> +                       qca,disable-5ghz;
> +               };
> +       };
> +};

	Arnd

  reply	other threads:[~2016-08-22  9:08 UTC|newest]

Thread overview: 161+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24 12:34 [ath9k-devel] [RFC v3] ath9k: add devicetree support to ath9k Martin Blumenstingl
2016-06-24 12:34 ` Martin Blumenstingl
2016-06-24 12:34 ` [ath9k-devel] [PATCH RFC v3 1/3] Documentation: dt: net: add ath9k wireless device binding Martin Blumenstingl
2016-06-24 12:34   ` Martin Blumenstingl
2016-06-27  0:20   ` [ath9k-devel] " Julian Calaby
2016-06-27  0:20     ` Julian Calaby
2016-06-27  9:49   ` [ath9k-devel] " Kalle Valo
2016-06-27  9:49     ` Kalle Valo
2016-06-24 12:34 ` [ath9k-devel] [PATCH v3 2/3] ath9k: add a helper to get the string representation of ath_bus_type Martin Blumenstingl
2016-06-24 12:34   ` Martin Blumenstingl
2016-06-27 10:26   ` [ath9k-devel] " Felix Fietkau
2016-06-27 10:26     ` Felix Fietkau
2016-06-29 22:37     ` [ath9k-devel] " Martin Blumenstingl
2016-06-29 22:37       ` Martin Blumenstingl
2016-06-24 12:34 ` [ath9k-devel] [PATCH RFC v3 3/3] ath9k: parse the device configuration from an OF node Martin Blumenstingl
2016-06-24 12:34   ` Martin Blumenstingl
2016-06-25 12:01   ` [ath9k-devel] " Christian Lamparter
2016-06-25 12:01     ` Christian Lamparter
2016-06-25 15:08     ` [ath9k-devel] " Martin Blumenstingl
2016-06-25 15:08       ` Martin Blumenstingl
2016-06-25 19:26       ` [ath9k-devel] " Christian Lamparter
2016-06-25 19:26         ` Christian Lamparter
2016-06-26 23:38         ` [ath9k-devel] " Martin Blumenstingl
2016-06-26 23:38           ` Martin Blumenstingl
2016-07-07  0:47           ` Luis R. Rodriguez
2016-07-07  1:03             ` [ath9k-devel] " Luis R. Rodriguez
2016-07-09 23:28 ` [ath9k-devel] [PATCH v4 0/3] add devicetree support to ath9k Martin Blumenstingl
2016-07-09 23:28   ` Martin Blumenstingl
2016-07-09 23:28   ` Martin Blumenstingl
2016-07-09 23:28   ` [ath9k-devel] [PATCH v4 1/3] Documentation: dt: net: add ath9k wireless device binding Martin Blumenstingl
2016-07-09 23:28     ` Martin Blumenstingl
2016-07-09 23:28     ` Martin Blumenstingl
2016-07-10 20:52     ` [ath9k-devel] " Arnd Bergmann
2016-07-10 20:52       ` Arnd Bergmann
2016-07-10 20:52       ` Arnd Bergmann
2016-07-10 20:54       ` [ath9k-devel] " Martin Blumenstingl
2016-07-10 20:54         ` Martin Blumenstingl
2016-07-10 20:54         ` Martin Blumenstingl
2016-07-10 22:01         ` [ath9k-devel] " Arnd Bergmann
2016-07-10 22:01           ` Arnd Bergmann
2016-07-10 22:01           ` Arnd Bergmann
2016-07-11 21:21           ` [ath9k-devel] " Martin Blumenstingl
2016-07-11 21:21             ` Martin Blumenstingl
2016-07-11 21:21             ` Martin Blumenstingl
2016-07-14 12:33             ` [ath9k-devel] " Arnd Bergmann
2016-07-14 12:33               ` Arnd Bergmann
2016-07-14 12:33               ` Arnd Bergmann
2016-07-13  7:02     ` [ath9k-devel] " Kalle Valo
2016-07-13  7:02       ` Kalle Valo
2016-07-13  7:02       ` Kalle Valo
2016-07-13  7:47       ` [ath9k-devel] " Arnd Bergmann
2016-07-13  7:47         ` Arnd Bergmann
2016-07-13  7:47         ` Arnd Bergmann
2016-07-09 23:28   ` [ath9k-devel] [PATCH v4 2/3] ath9k: add a helper to get the string representation of ath_bus_type Martin Blumenstingl
2016-07-09 23:28     ` Martin Blumenstingl
2016-07-09 23:28     ` Martin Blumenstingl
2016-07-09 23:28   ` [ath9k-devel] [PATCH v4 3/3] ath9k: parse the device configuration from an OF node Martin Blumenstingl
2016-07-09 23:28     ` Martin Blumenstingl
2016-07-09 23:28     ` Martin Blumenstingl
2016-07-10  0:19     ` Bjørn Mork
2016-07-10  0:32       ` [ath9k-devel] " Bjørn Mork
2016-07-10  0:19       ` Bjørn Mork
2016-07-10  9:28       ` [ath9k-devel] " Oleksij Rempel
2016-07-10  9:28         ` Oleksij Rempel
2016-07-10  9:28         ` Oleksij Rempel
2016-07-10 20:56       ` [ath9k-devel] " Martin Blumenstingl
2016-07-10 20:56         ` Martin Blumenstingl
2016-07-10 20:56         ` Martin Blumenstingl
2016-08-21 14:31   ` [ath9k-devel] [PATCH v5 0/3] add devicetree support to ath9k Martin Blumenstingl
2016-08-21 14:31     ` Martin Blumenstingl
2016-08-21 14:31     ` Martin Blumenstingl
2016-08-21 14:31     ` [ath9k-devel] [PATCH v5 1/3] Documentation: dt: net: add ath9k wireless device binding Martin Blumenstingl
2016-08-21 14:31       ` Martin Blumenstingl
2016-08-21 14:31       ` Martin Blumenstingl
2016-08-22  9:08       ` Arnd Bergmann [this message]
2016-08-22  9:08         ` Arnd Bergmann
2016-08-22  9:08         ` Arnd Bergmann
2016-08-28 20:51         ` [ath9k-devel] " Martin Blumenstingl
2016-08-28 20:51           ` Martin Blumenstingl
2016-08-28 20:51           ` Martin Blumenstingl
2016-08-29 12:12           ` [ath9k-devel] " Arnd Bergmann
2016-08-29 12:12             ` Arnd Bergmann
2016-08-29 12:12             ` Arnd Bergmann
2016-08-21 14:31     ` [ath9k-devel] [PATCH v5 2/3] ath9k: add a helper to get the string representation of ath_bus_type Martin Blumenstingl
2016-08-21 14:31       ` Martin Blumenstingl
2016-08-21 14:31       ` Martin Blumenstingl
2016-08-21 14:31     ` [ath9k-devel] [PATCH v5 3/3] ath9k: parse the device configuration from an OF node Martin Blumenstingl
2016-08-21 14:31       ` Martin Blumenstingl
2016-08-21 14:31       ` Martin Blumenstingl
2016-09-06 21:46     ` [ath9k-devel] [PATCH v6 0/3] add devicetree support to ath9k Martin Blumenstingl
2016-09-06 21:46       ` Martin Blumenstingl
2016-09-06 21:46       ` Martin Blumenstingl
2016-09-06 21:46       ` [ath9k-devel] [PATCH v6 1/3] Documentation: dt: net: add ath9k wireless device binding Martin Blumenstingl
2016-09-06 21:46         ` Martin Blumenstingl
2016-09-06 21:46         ` Martin Blumenstingl
2016-09-09  7:48         ` [ath9k-devel] " Oleksij Rempel
2016-09-09  7:48           ` Oleksij Rempel
2016-09-09  7:48           ` Oleksij Rempel
2016-09-09 20:57           ` [ath9k-devel] " Martin Blumenstingl
2016-09-09 20:57             ` Martin Blumenstingl
2016-09-09 20:57             ` Martin Blumenstingl
2016-09-13  7:28             ` [ath9k-devel] " Oleksij Rempel
2016-09-13  7:28               ` Oleksij Rempel
2016-09-13  7:28               ` Oleksij Rempel
2016-09-16 12:45             ` Rob Herring
2016-09-16 12:45               ` [ath9k-devel] " Rob Herring
2016-09-16 12:45               ` Rob Herring
2016-09-18 21:51               ` [ath9k-devel] " Martin Blumenstingl
2016-09-18 21:51                 ` Martin Blumenstingl
2016-09-18 21:51                 ` Martin Blumenstingl
2016-09-16 12:37         ` Rob Herring
2016-09-16 12:55           ` [ath9k-devel] " Rob Herring
2016-09-16 12:37           ` Rob Herring
2016-09-06 21:46       ` [ath9k-devel] [PATCH v6 2/3] ath9k: add a helper to get the string representation of ath_bus_type Martin Blumenstingl
2016-09-06 21:46         ` Martin Blumenstingl
2016-09-06 21:46         ` Martin Blumenstingl
2016-09-06 21:46       ` [ath9k-devel] [PATCH v6 3/3] ath9k: parse the device configuration from an OF node Martin Blumenstingl
2016-09-06 21:46         ` Martin Blumenstingl
2016-09-06 21:46         ` Martin Blumenstingl
2016-10-02 21:47       ` [ath9k-devel] [PATCH v7 0/3] add devicetree support to ath9k Martin Blumenstingl
2016-10-02 21:47         ` Martin Blumenstingl
2016-10-02 21:47         ` Martin Blumenstingl
2016-10-02 21:47         ` [ath9k-devel] [PATCH v7 1/3] Documentation: dt: net: add ath9k wireless device binding Martin Blumenstingl
2016-10-02 21:47           ` Martin Blumenstingl
2016-10-02 21:47           ` Martin Blumenstingl
2016-10-07 12:17           ` [v7, " Kalle Valo
2016-10-07 12:17           ` Kalle Valo
2016-10-07 12:17             ` Kalle Valo
2016-10-07 12:17           ` [ath9k-devel] " Kalle Valo
2016-10-07 12:17             ` Kalle Valo
2016-10-08 22:50           ` [PATCH v7 " Rob Herring
2016-10-09  1:28           ` Rob Herring
2016-10-09  1:29             ` [ath9k-devel] " Rob Herring
2016-10-09  1:28             ` Rob Herring
2016-10-09  9:54             ` [ath9k-devel] " Martin Blumenstingl
2016-10-09  9:54               ` Martin Blumenstingl
2016-10-09  9:54               ` Martin Blumenstingl
2016-10-02 21:47         ` [ath9k-devel] [PATCH v7 2/3] ath9k: add a helper to get the string representation of ath_bus_type Martin Blumenstingl
2016-10-02 21:47           ` Martin Blumenstingl
2016-10-02 21:47           ` Martin Blumenstingl
2016-10-02 21:47         ` [ath9k-devel] [PATCH v7 3/3] ath9k: parse the device configuration from an OF node Martin Blumenstingl
2016-10-02 21:47           ` Martin Blumenstingl
2016-10-02 21:47           ` Martin Blumenstingl
2016-10-16 20:59         ` [ath9k-devel] [PATCH v8 0/3] add devicetree support to ath9k Martin Blumenstingl
2016-10-16 20:59           ` Martin Blumenstingl
2016-10-16 20:59           ` Martin Blumenstingl
2016-10-16 20:59           ` [ath9k-devel] [PATCH v8 1/3] Documentation: dt: net: add ath9k wireless device binding Martin Blumenstingl
2016-10-16 20:59             ` Martin Blumenstingl
2016-10-16 20:59             ` Martin Blumenstingl
2016-10-18 15:31             ` Rob Herring
2016-10-18 15:31               ` [ath9k-devel] " Rob Herring
2016-10-18 15:31               ` Rob Herring
2016-11-15 14:56             ` [ath9k-devel] [v8, " Kalle Valo
2016-11-15 14:56               ` Kalle Valo
2016-11-15 14:56               ` Kalle Valo
2016-10-16 20:59           ` [ath9k-devel] [PATCH v8 2/3] ath9k: add a helper to get the string representation of ath_bus_type Martin Blumenstingl
2016-10-16 20:59             ` Martin Blumenstingl
2016-10-16 20:59             ` Martin Blumenstingl
2016-10-16 20:59           ` [ath9k-devel] [PATCH v8 3/3] ath9k: parse the device configuration from an OF node Martin Blumenstingl
2016-10-16 20:59             ` Martin Blumenstingl
2016-10-16 20:59             ` Martin Blumenstingl

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=2913835.hr5kg63Vcv@wuerfel \
    --to=arnd@arndb.de \
    --cc=ath9k-devel@lists.ath9k.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.