1. 27 Jun, 2019 6 commits
    • Lorenzo Bianconi's avatar
      mt76: mt7615: add support for mtd eeprom parsing · f9461a68
      Lorenzo Bianconi authored
      Calibration data are often available on a specific mtd partition on
      embedded devices. Take into account eeprom calibration data if
      available.
      Signed-off-by: default avatarLorenzo Bianconi <lorenzo@kernel.org>
      Signed-off-by: default avatarFelix Fietkau <nbd@nbd.name>
      f9461a68
    • Lorenzo Bianconi's avatar
      mt76: move mt76_insert_ccmp_hdr in mt76-module · eadfd98f
      Lorenzo Bianconi authored
      Move mt7615_insert_ccmp_hdr in mac80211.c and rename it in
      mt76_insert_ccmp_hdr since it is shared between mt7603 and mt7615
      drivers
      Signed-off-by: default avatarLorenzo Bianconi <lorenzo@kernel.org>
      Signed-off-by: default avatarFelix Fietkau <nbd@nbd.name>
      eadfd98f
    • Felix Fietkau's avatar
      mt76: mt76x02: fix tx reordering on rate control probing without a-mpdu · 5c280ae7
      Felix Fietkau authored
      To avoid aggregating rate control probing packets with other traffic, and to
      ensure that the probing rate gets used, probing packets get assigned a different
      internal queueing priority.
      This causes packets to be transmitted in a different order, which is compensated
      by the receiver side reordering.
      However, if A-MPDU is disabled, this reordering can become visible to upper
      layers on the receiver side. Disable the priority change if A-MPDU is disabled.
      Signed-off-by: default avatarFelix Fietkau <nbd@nbd.name>
      5c280ae7
    • Felix Fietkau's avatar
      mt76: mt76x02: fix tx status reporting issues · 8548c6eb
      Felix Fietkau authored
      When the hardware falls back to lower rates for a transmit attempt, only the
      first status report will show the number of retries correctly. The frames
      that follow will report the correct final rate, but number of retries set to 0.
      This can cause the rate control module to vastly underestimate the number of
      retransmissions per rate.
      
      To fix this, we need to keep track of the initial requested tx rate per packet
      and pass it to the status information.
      For frames with tx status requested, this is simple: use the rate configured
      in info->control.rates[0] as reference.
      For no-skb tx status information, we have to encode the requested tx rate in
      the packet id (and make it possible to distinguish it from real packet ids).
      
      To do that, reduce the packet id field size by one bit, and use that bit to
      indicate packet id vs rate.
      
      This change also improves reporting by filling the status rate array with
      rates from first rate to final rate, taking the same steps as the hardware
      fallback table. This matters in corner cases like MCS8 on HT, where the
      fallback target is MCS0, not MCS7.
      Signed-off-by: default avatarFelix Fietkau <nbd@nbd.name>
      8548c6eb
    • Felix Fietkau's avatar
      mt76: fix setting chan->max_power · 09952572
      Felix Fietkau authored
      When setting chan->max_power after registering the wiphy, chan->max_reg_power
      needs to be used as a limit
      Signed-off-by: default avatarFelix Fietkau <nbd@nbd.name>
      09952572
    • Felix Fietkau's avatar
      mt76: mt7603: fix reading target tx power from eeprom · b0297b67
      Felix Fietkau authored
      For the external PA (TSSI OFF) case, the target power needs to be read
      from a different location in EEPROM
      Signed-off-by: default avatarFelix Fietkau <nbd@nbd.name>
      b0297b67
  2. 25 Jun, 2019 34 commits