linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: ath9k-devel@qca.qualcomm.com, linux-wireless@vger.kernel.org,
	ath9k-devel@lists.ath9k.org, nbd@nbd.name
Subject: Re: [PATCH 1/2] ath9k: parse the device configuration from an OF node
Date: Thu, 23 Jun 2016 17:59:11 +0200	[thread overview]
Message-ID: <3936546.74vnbYymVv@debian64> (raw)
In-Reply-To: <20160623151328.24061-2-martin.blumenstingl@googlemail.com>

On Thursday, June 23, 2016 05:13:27 PM Martin Blumenstingl wrote:
> This makes it possible to configure ath9k based devices using
> devicetree. That makes some out-of-tree "convert devicetree to
> ath9k_platform_data glue"-code obsolete.
> 
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> ---
>  drivers/net/wireless/ath/ath9k/init.c | 70 +++++++++++++++++++++++++++++++++++
>  1 file changed, 70 insertions(+)
> 
> diff --git a/drivers/net/wireless/ath/ath9k/init.c b/drivers/net/wireless/ath/ath9k/init.c
> index a0f4a52..0f76137 100644
> --- a/drivers/net/wireless/ath/ath9k/init.c
> +++ b/drivers/net/wireless/ath/ath9k/init.c
> @@ -20,6 +20,8 @@
>  #include <linux/slab.h>
>  #include <linux/ath9k_platform.h>
>  #include <linux/module.h>
> +#include <linux/of.h>
> +#include <linux/of_net.h>
>  #include <linux/relay.h>
>  #include <net/ieee80211_radiotap.h>
>  
> @@ -555,6 +557,70 @@ static int ath9k_init_platform(struct ath_softc *sc)
>  	return 0;
>  }
>  
> +static int ath9k_of_init(struct ath_softc *sc)
> +{
> +	struct device_node *np = sc->dev->of_node;
> +	struct ath_hw *ah = sc->sc_ah;
> +	struct ath_common *common = ath9k_hw_common(ah);
> +	const char *mac, *eeprom_name;
> +	int led_pin, ret;
> +	u32 gpio_data;
> +
> +	if (!np)
> +		return 0;

Can you please add a of_device_is_available check here too? So
we can skip it with the status property?

> +
> +	ath_dbg(common, CONFIG, "parsing configuration from OF node\n");
> +
> +	if (!of_property_read_u32(np, "ath,led-pin", &led_pin))
> +		ah->led_pin = led_pin;
> +
> +	if (!of_property_read_u32(np, "ath,gpio-mask", &gpio_data))
> +		ah->gpio_mask = gpio_data;
> +
> +	if (!of_property_read_u32(np, "ath,gpio-val", &gpio_data))
> +		ah->gpio_val = gpio_data;
> +
> +	if (of_property_read_bool(np, "ath,clk-25mhz"))
> +		ah->is_clk_25mhz = true;
> +
> +	if (!of_property_read_u32(np, "ath,gpio-mask", &gpio_data))
> +		ah->gpio_mask = gpio_data;
^^
Duplicated? (see 11 lines above)

> +
> +	if (!of_property_read_u32(np, "ath,gpio-val", &gpio_data))
> +		ah->gpio_val = gpio_data;
^^
Duplicated?

> +
> +	if (of_property_read_bool(np, "ath,clk-25mhz"))
> +		ah->is_clk_25mhz = true;
^^
Duplicated?

> +
> +	if (of_property_read_bool(np, "ath,led-active-high"))
> +		ah->config.led_active_high = true;
> +
> +	if (of_property_read_bool(np, "ath,disable-2ghz"))
> +		ah->disable_2ghz = true;
> +
> +	if (of_property_read_bool(np, "ath,disable-5ghz"))
> +		ah->disable_5ghz = true;
> +
> +	if (of_property_read_bool(np, "ath,check-eeprom-endianness"))
> +		ah->ah_flags &= ~AH_NO_EEP_SWAP;
> +	else
> +		ah->ah_flags |= AH_NO_EEP_SWAP;
> +
> +	if (!of_property_read_string(np, "ath,eeprom-name", &eeprom_name)) {
> +		ret = ath9k_eeprom_request(sc, eeprom_name);
> +		if (ret)
> +			return ret;
> +	}
> +
> +	mac = of_get_mac_address(np);
> +	if (mac)
> +		ether_addr_copy(common->macaddr, mac);
> +
> +	ah->ah_flags &= ~AH_USE_EEPROM;
> +
> +	return 0;
> +}
> +
>  static int ath9k_init_softc(u16 devid, struct ath_softc *sc,
>  			    const struct ath_bus_ops *bus_ops)
>  {
> @@ -611,6 +677,10 @@ static int ath9k_init_softc(u16 devid, struct ath_softc *sc,
>  	if (ret)
>  		return ret;
>  
> +	ret = ath9k_of_init(sc);
> +	if (ret)
> +		return ret;
> +
>  	if (ath9k_led_active_high != -1)
>  		ah->config.led_active_high = ath9k_led_active_high == 1;



  reply	other threads:[~2016-06-23 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 15:13 [RFC] ath9k: add devicetree support to ath9k Martin Blumenstingl
2016-06-23 15:13 ` [PATCH 1/2] ath9k: parse the device configuration from an OF node Martin Blumenstingl
2016-06-23 15:59   ` Christian Lamparter [this message]
2016-06-23 15:13 ` [PATCH 2/2] Documentation: dt: net: add ath9k wireless device binding Martin Blumenstingl
2016-06-23 16:18   ` Christian Lamparter

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=3936546.74vnbYymVv@debian64 \
    --to=chunkeey@googlemail.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=ath9k-devel@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=nbd@nbd.name \
    /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).