ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>,
	Benjamin Berg <benjamin@sipsolutions.net>,
	Mathias Kretschmer <mathias.kretschmer@fit.fraunhofer.de>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	Simon Wunderlich <sw@simonwunderlich.de>
Subject: Re: [PATCHv2 2/2] ath10k: Allow setting coverage class
Date: Thu, 4 Aug 2016 13:35:59 +0200	[thread overview]
Message-ID: <dcd027e0-33d1-c329-73c4-8d1afb7ea080@dd-wrt.com> (raw)
In-Reply-To: <CA+BoTQn30T9w1E63Ch51oYRJYuRBNLORy4=xAeEGzDo2yZqPbQ@mail.gmail.com>

Am 04.08.2016 um 07:28 schrieb Michal Kazior:
> On 3 August 2016 at 17:37, Sebastian Gottschall <s.gottschall@dd-wrt.com> wrote:
>>>> +       if (value < 0)
>>>> +               value = ar->fw_coverage.coverage_class;
>>>> +
>>>> +       /* Break out if the coverage class and registers have the
>>>> expected
>>>> +        * value.
>>>> +        */
>>>> +       if (value == ar->fw_coverage.coverage_class &&
>>>> +           slottime_reg == ar->fw_coverage.reg_slottime_conf &&
>>>> +           timeout_reg == ar->fw_coverage.reg_ack_cts_timeout_conf)
>>>> +               goto unlock;
>>> I would move this part to the caller and keep the hardware-specific
>>> function just compute and set registers, e.g. have
>>> ath10k_mac_set_coverage_class (as opposed to
>>> ath10k_mac_op_set_coverage_class). It should also reduce some code
>>> duplication.
>> doesnt make sense. i already enhanced this code to support beeliner (99xx)
>> and newers.
>> the code is that much different that this check need to be treaded in a
>> indivudual way
>> reg_slottime_conf is hardware defacto specific since the value is taken from
>> a hardware specific register.
>> you cannot handle this outside this function since other chips have
>> different registers.
> Ah, you're right, my bad :)
the current code i sended to benjamin makes several of these vars 
obsolete anyway.
just waiting for his new cleaned up version here on that list.

>
>
> Michał
>


-- 
Mit freundlichen Grüssen / Regards

Sebastian Gottschall / CTO

NewMedia-NET GmbH - DD-WRT
Firmensitz:  Berliner Ring 101, 64625 Bensheim
Registergericht: Amtsgericht Darmstadt, HRB 25473
Geschäftsführer: Peter Steinhäuser, Christian Scheele
http://www.dd-wrt.com
email: s.gottschall@dd-wrt.com
Tel.: +496251-582650 / Fax: +496251-5826565


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

      reply	other threads:[~2016-08-04 11:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01 10:21 [PATCHv2 0/2] ath10k: Allow setting coverage class Benjamin Berg
2016-08-01 10:21 ` [PATCHv2 1/2] ath10k: Rename hw_rx_desc_ops to hw_ops to use it for other purposes Benjamin Berg
2016-08-01 10:21 ` [PATCHv2 2/2] ath10k: Allow setting coverage class Benjamin Berg
2016-08-03  7:19   ` Michal Kazior
2016-08-03 15:37     ` Sebastian Gottschall
2016-08-04  5:28       ` Michal Kazior
2016-08-04 11:35         ` Sebastian Gottschall [this message]

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=dcd027e0-33d1-c329-73c4-8d1afb7ea080@dd-wrt.com \
    --to=s.gottschall@dd-wrt.com \
    --cc=ath10k@lists.infradead.org \
    --cc=benjamin@sipsolutions.net \
    --cc=mathias.kretschmer@fit.fraunhofer.de \
    --cc=michal.kazior@tieto.com \
    --cc=sw@simonwunderlich.de \
    --cc=vthiagar@qti.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox