All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Kalle Valo <kvalo@qca.qualcomm.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	Andy Lutomirski <luto@amacapital.net>
Subject: Re: ath10k: calibration data through Device Tree?
Date: Fri, 3 Oct 2014 17:25:13 +0100	[thread overview]
Message-ID: <20141003162513.GW26643@leverpostej> (raw)
In-Reply-To: <2386503.dNPayhXJTQ@wuerfel>

> From a system design point, it's still horrible that you have to use
> DT for a device that is on a discoverable bus like PCI, but as you describe,
> the reality is that products are shipping that use ath10k PCI devices
> without this data in them.

I'd see any DT property for this as a workaround, the use of which
should be discouraged.

A fun question that springs to mind is can the ath10k chip be removed,
and if so am I able to place it into a non-DT system (whereupon I have
no calibration data, so it won't work)?

Mark.

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>,
	Kalle Valo <kvalo-A+ZNKFmMK5xy9aJCnZT0Uw@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"ath10k-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<ath10k-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: ath10k: calibration data through Device Tree?
Date: Fri, 3 Oct 2014 17:25:13 +0100	[thread overview]
Message-ID: <20141003162513.GW26643@leverpostej> (raw)
In-Reply-To: <2386503.dNPayhXJTQ@wuerfel>

> From a system design point, it's still horrible that you have to use
> DT for a device that is on a discoverable bus like PCI, but as you describe,
> the reality is that products are shipping that use ath10k PCI devices
> without this data in them.

I'd see any DT property for this as a workaround, the use of which
should be discouraged.

A fun question that springs to mind is can the ath10k chip be removed,
and if so am I able to place it into a non-DT system (whereupon I have
no calibration data, so it won't work)?

Mark.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-10-03 16:25 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02 13:14 ath10k: calibration data through Device Tree? Kalle Valo
2014-10-02 13:14 ` Kalle Valo
2014-10-02 13:27 ` Arnd Bergmann
2014-10-02 13:27   ` Arnd Bergmann
2014-10-02 13:47   ` Kalle Valo
2014-10-02 13:47     ` Kalle Valo
2014-10-02 14:19     ` Arnd Bergmann
2014-10-02 14:19       ` Arnd Bergmann
2014-10-02 14:55       ` Kalle Valo
2014-10-02 14:55         ` Kalle Valo
2014-10-02 15:58         ` Arnd Bergmann
2014-10-02 15:58           ` Arnd Bergmann
2014-10-02 13:29 ` Mark Rutland
2014-10-02 13:29   ` Mark Rutland
2014-10-02 13:44   ` Kalle Valo
2014-10-02 13:44     ` Kalle Valo
2014-10-02 15:07     ` Mark Rutland
2014-10-02 15:07       ` Mark Rutland
2014-10-02 19:05     ` Andy Lutomirski
2014-10-02 19:05       ` Andy Lutomirski
2014-10-02 19:28       ` Adrian Chadd
2014-10-02 19:28         ` Adrian Chadd
2014-10-02 19:35         ` Andy Lutomirski
2014-10-02 19:35           ` Andy Lutomirski
2014-10-07 16:44           ` Kalle Valo
2014-10-07 16:44             ` Kalle Valo
2014-10-17 12:25             ` Kumar Gala
2014-10-17 12:25               ` Kumar Gala
2014-10-22 12:02               ` Kalle Valo
2014-10-22 12:02                 ` Kalle Valo
2014-10-03 15:29       ` Arnd Bergmann
2014-10-03 15:29         ` Arnd Bergmann
2014-10-03 16:24         ` Andy Lutomirski
2014-10-03 16:24           ` Andy Lutomirski
2014-10-03 16:25         ` Mark Rutland [this message]
2014-10-03 16:25           ` Mark Rutland
2014-10-03 16:42           ` Arnd Bergmann
2014-10-03 16:42             ` Arnd Bergmann
2014-10-03 16:54             ` Andy Lutomirski
2014-10-03 16:54               ` Andy Lutomirski
2014-10-03 17:21               ` Adrian Chadd
2014-10-03 17:21                 ` Adrian Chadd
  -- strict thread matches above, loose matches on Subject: below --
2014-10-02 13:05 Kalle Valo
2014-10-02 13:09 ` 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=20141003162513.GW26643@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=arnd@arndb.de \
    --cc=ath10k@lists.infradead.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kvalo@qca.qualcomm.com \
    --cc=luto@amacapital.net \
    /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.