All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Michal Kazior <michal.kazior@tieto.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: Fix DMA burst size
Date: Mon, 12 Jan 2015 13:51:48 +0200	[thread overview]
Message-ID: <87ppakdxnv.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <21677.2491.857663.473071@gargle.gargle.HOWL> (Sujith Manoharan's message of "Wed, 7 Jan 2015 15:56:03 +0530")

Sujith Manoharan <sujith@msujith.org> writes:

> Michal Kazior wrote:
>> Since it's for cards/chips why do you enable it for 10.2 only? There's
>> 10.1, main and tlv as well which could possibly benefit from this.
>
> I've not tested it with any of the FW versions other than 10.2 and
> am not sure if older FW support this properly. We could try it
> with 10.1, I guess - but even that is in 'maintenance mode'
> internally.

Yeah, I don't see much point of trying to improve our 10.1 support as
all the new development happens on 10.2 branch. Most important is that
we don't break 10.1 support ("no regressions" rule), but it in no way
does 10.1 need to be in feature parity with 10.2.

-- 
Kalle Valo

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

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: Michal Kazior <michal.kazior@tieto.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: Fix DMA burst size
Date: Mon, 12 Jan 2015 13:51:48 +0200	[thread overview]
Message-ID: <87ppakdxnv.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <21677.2491.857663.473071@gargle.gargle.HOWL> (Sujith Manoharan's message of "Wed, 7 Jan 2015 15:56:03 +0530")

Sujith Manoharan <sujith@msujith.org> writes:

> Michal Kazior wrote:
>> Since it's for cards/chips why do you enable it for 10.2 only? There's
>> 10.1, main and tlv as well which could possibly benefit from this.
>
> I've not tested it with any of the FW versions other than 10.2 and
> am not sure if older FW support this properly. We could try it
> with 10.1, I guess - but even that is in 'maintenance mode'
> internally.

Yeah, I don't see much point of trying to improve our 10.1 support as
all the new development happens on 10.2 branch. Most important is that
we don't break 10.1 support ("no regressions" rule), but it in no way
does 10.1 need to be in feature parity with 10.2.

-- 
Kalle Valo

  reply	other threads:[~2015-01-12 11:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29  6:21 [PATCH] ath10k: Fix DMA burst size Sujith Manoharan
2014-12-29  6:21 ` Sujith Manoharan
2015-01-02  7:41 ` Kalle Valo
2015-01-02  7:41   ` Kalle Valo
2015-01-07 10:04 ` Michal Kazior
2015-01-07 10:04   ` Michal Kazior
2015-01-07 10:26   ` Sujith Manoharan
2015-01-07 10:26     ` Sujith Manoharan
2015-01-12 11:51     ` Kalle Valo [this message]
2015-01-12 11:51       ` Kalle Valo
2015-01-12 11:53 ` Kalle Valo
2015-01-12 11:53   ` 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=87ppakdxnv.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 \
    --cc=sujith@msujith.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.