From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <ath10k@lists.infradead.org>
Cc: <devicetree-discuss@lists.ozlabs.org>,
<linux-wireless@vger.kernel.org>, <toshik@chromium.org>
Subject: [PATCH v3 0/2] ath10k: device tree support
Date: Thu, 27 Nov 2014 14:00:14 +0200 [thread overview]
Message-ID: <20141127115922.28539.9482.stgit@potku.adurom.net> (raw)
Hi,
here's ath10k device tree support which Toshi and me have been working
on. Please review.
Device tree maintainers: please review the bindings document
carefully, this is the first time I have written one.
v3:
* add a debug message to ath10k
* write bindings file
* use ar->dev.of_node instead of pci_device_to_OF_node()
v2:
* fixed a bug that returns an uninitialized value if the node is not
found
---
Kalle Valo (1):
dt: bindings: add ath10k wireless device
Toshi Kikuchi (1):
ath10k: read calibration data from Device Tree
.../bindings/net/wireless/qcom,ath10k.txt | 30 +++++++++
drivers/net/wireless/ath/ath10k/core.c | 70 ++++++++++++++++++++
drivers/net/wireless/ath/ath10k/core.h | 3 +
3 files changed, 102 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath10k@lists.infradead.org
Cc: devicetree-discuss@lists.ozlabs.org,
linux-wireless@vger.kernel.org, toshik@chromium.org
Subject: [PATCH v3 0/2] ath10k: device tree support
Date: Thu, 27 Nov 2014 14:00:14 +0200 [thread overview]
Message-ID: <20141127115922.28539.9482.stgit@potku.adurom.net> (raw)
Hi,
here's ath10k device tree support which Toshi and me have been working
on. Please review.
Device tree maintainers: please review the bindings document
carefully, this is the first time I have written one.
v3:
* add a debug message to ath10k
* write bindings file
* use ar->dev.of_node instead of pci_device_to_OF_node()
v2:
* fixed a bug that returns an uninitialized value if the node is not
found
---
Kalle Valo (1):
dt: bindings: add ath10k wireless device
Toshi Kikuchi (1):
ath10k: read calibration data from Device Tree
.../bindings/net/wireless/qcom,ath10k.txt | 30 +++++++++
drivers/net/wireless/ath/ath10k/core.c | 70 ++++++++++++++++++++
drivers/net/wireless/ath/ath10k/core.h | 3 +
3 files changed, 102 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2014-11-27 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 12:00 Kalle Valo [this message]
2014-11-27 12:00 ` [PATCH v3 0/2] ath10k: device tree support Kalle Valo
2014-11-27 12:00 ` [PATCH v3 1/2] dt: bindings: add ath10k wireless device Kalle Valo
2014-11-27 12:00 ` Kalle Valo
2014-11-27 12:00 ` [PATCH v3 2/2] ath10k: read calibration data from Device Tree Kalle Valo
2014-11-27 12:00 ` Kalle Valo
2014-11-27 12:04 ` [PATCH v3 0/2] ath10k: device tree support Kalle Valo
2014-11-27 12:04 ` Kalle Valo
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=20141127115922.28539.9482.stgit@potku.adurom.net \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-wireless@vger.kernel.org \
--cc=toshik@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 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.