All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: ath9k-devel@qca.qualcomm.com, linux-wireless@vger.kernel.org,
	ath9k-devel@lists.ath9k.org
Cc: nbd@nbd.name, chunkeey@googlemail.com, mark.rutland@arm.com,
	robh+dt@kernel.org
Subject: [RFC v2] ath9k: add devicetree support to ath9k
Date: Thu, 23 Jun 2016 19:45:34 +0200	[thread overview]
Message-ID: <20160623174536.5967-1-martin.blumenstingl@googlemail.com> (raw)

This series adds support for configuring ath9k based devices via
devicetree. This was tested on PCI(e) based devices. This should work
for AHB based devices as well as soon as the ath79 platform is ready
to populate the ath9k wmac via devicetree.

This series depends on my previous series:
"ath9k: extend and improve handling of ath9k_platform_data"

changes in v1 -> v2:
This addresses all issues found by Christian Lamparter (thanks!), the
detailed changes are documented in each patch.



WARNING: multiple messages have this Message-ID (diff)
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC v2] ath9k: add devicetree support to ath9k
Date: Thu, 23 Jun 2016 19:45:34 +0200	[thread overview]
Message-ID: <20160623174536.5967-1-martin.blumenstingl@googlemail.com> (raw)

This series adds support for configuring ath9k based devices via
devicetree. This was tested on PCI(e) based devices. This should work
for AHB based devices as well as soon as the ath79 platform is ready
to populate the ath9k wmac via devicetree.

This series depends on my previous series:
"ath9k: extend and improve handling of ath9k_platform_data"

changes in v1 -> v2:
This addresses all issues found by Christian Lamparter (thanks!), the
detailed changes are documented in each patch.

             reply	other threads:[~2016-06-23 17:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 17:45 Martin Blumenstingl [this message]
2016-06-23 17:45 ` [ath9k-devel] [RFC v2] ath9k: add devicetree support to ath9k Martin Blumenstingl
2016-06-23 17:45 ` [PATCH RFC v2 1/2] Documentation: dt: net: add ath9k wireless device binding Martin Blumenstingl
2016-06-23 17:45   ` [ath9k-devel] " Martin Blumenstingl
2016-06-23 17:58   ` Mark Rutland
2016-06-23 18:08     ` [ath9k-devel] " Mark Rutland
2016-06-23 18:14     ` Martin Blumenstingl
2016-06-23 18:14       ` [ath9k-devel] " Martin Blumenstingl
2016-06-27 12:57       ` Mark Rutland
2016-06-27 12:57         ` [ath9k-devel] " Mark Rutland
2016-06-27 13:07         ` Felix Fietkau
2016-06-27 13:07           ` [ath9k-devel] " Felix Fietkau
2016-06-27 14:58         ` Martin Blumenstingl
2016-06-27 14:58           ` [ath9k-devel] " Martin Blumenstingl
2016-06-23 19:25   ` Arend Van Spriel
2016-06-23 19:33     ` [ath9k-devel] " Arend Van Spriel
2016-06-23 21:46     ` Martin Blumenstingl
2016-06-23 21:46       ` [ath9k-devel] " Martin Blumenstingl
2016-06-23 17:45 ` [PATCH RFC v2 2/2] ath9k: parse the device configuration from an OF node Martin Blumenstingl
2016-06-23 17:45   ` [ath9k-devel] " 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=20160623174536.5967-1-martin.blumenstingl@googlemail.com \
    --to=martin.blumenstingl@googlemail.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=ath9k-devel@qca.qualcomm.com \
    --cc=chunkeey@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=nbd@nbd.name \
    --cc=robh+dt@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 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.