All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/3] ath10k: embed supported chip ids in hw_params
Date: Wed, 26 Nov 2014 09:21:16 +0200	[thread overview]
Message-ID: <87vbm2whoz.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1416838646-18801-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Mon, 24 Nov 2014 15:17:24 +0100")

Michal Kazior <michal.kazior@tieto.com> writes:

> This will make it easier to extend and maintain
> list of supported hardware.
>
> As a requirement this moves chip_id checking a
> little later because target_version isn't known
> until BMI can be queried.
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>

The reason why I originally added the chip_id check was that QCA988X hw
1.0 failed badly (ath10k might have even crashed, don't remember
anymore) and I added this chip_id as an ugly workaround to detect hw1.0
early. Most likely with this patch the problem comes back again.

I don't know what's a good solution, need to think more. Any ideas?

-- 
Kalle Valo

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 1/3] ath10k: embed supported chip ids in hw_params
Date: Wed, 26 Nov 2014 09:21:16 +0200	[thread overview]
Message-ID: <87vbm2whoz.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1416838646-18801-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Mon, 24 Nov 2014 15:17:24 +0100")

Michal Kazior <michal.kazior@tieto.com> writes:

> This will make it easier to extend and maintain
> list of supported hardware.
>
> As a requirement this moves chip_id checking a
> little later because target_version isn't known
> until BMI can be queried.
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>

The reason why I originally added the chip_id check was that QCA988X hw
1.0 failed badly (ath10k might have even crashed, don't remember
anymore) and I added this chip_id as an ugly workaround to detect hw1.0
early. Most likely with this patch the problem comes back again.

I don't know what's a good solution, need to think more. Any ideas?

-- 
Kalle Valo

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

  parent reply	other threads:[~2014-11-26  7:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 14:17 [PATCH 1/3] ath10k: embed supported chip ids in hw_params Michal Kazior
2014-11-24 14:17 ` Michal Kazior
2014-11-24 14:17 ` [PATCH 2/3] ath10k: put board size into hw_params Michal Kazior
2014-11-24 14:17   ` Michal Kazior
2014-11-24 14:17 ` [PATCH 3/3] ath10k: move uart pin config " Michal Kazior
2014-11-24 14:17   ` Michal Kazior
2014-11-26  7:21 ` Kalle Valo [this message]
2014-11-26  7:21   ` [PATCH 1/3] ath10k: embed supported chip ids in hw_params Kalle Valo
2014-11-26  7:54   ` Michal Kazior
2014-11-26  7:54     ` Michal Kazior
2014-11-27  7:30     ` Kalle Valo
2014-11-27  7:30       ` Kalle Valo
2014-11-27  7:45       ` Michal Kazior
2014-11-27  7:45         ` Michal Kazior
2014-11-28  7:02         ` Kalle Valo
2014-11-28  7:02           ` Kalle Valo
2014-11-28  7:10     ` Kalle Valo
2014-11-28  7:10       ` Kalle Valo
2014-11-28 11:25       ` Michal Kazior
2014-11-28 11:25         ` Michal Kazior
2014-12-01  7:17 ` [PATCH v2 1/3] ath10k: create a chip revision whielist Michal Kazior
2014-12-01  7:17   ` Michal Kazior
2014-12-01  7:17   ` [PATCH v2 2/3] ath10k: put board size into hw_params Michal Kazior
2014-12-01  7:17     ` Michal Kazior
2014-12-01  7:17   ` [PATCH v2 3/3] ath10k: move uart pin config " Michal Kazior
2014-12-01  7:17     ` Michal Kazior
2014-12-01  7:47   ` [PATCH v2 1/3] ath10k: create a chip revision whielist Kalle Valo
2014-12-01  7:47     ` Kalle Valo
2014-12-01  8:35     ` Michal Kazior
2014-12-01  8:35       ` Michal Kazior
2014-12-08 15:35   ` Kalle Valo
2014-12-08 15:35     ` 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=87vbm2whoz.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michal.kazior@tieto.com \
    /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.