Eric Lee / smarc-fsl-linux-kernel

08 Jul, 2016

1 commit

11 Mar, 2016

1 commit

28 Oct, 2014

2 commits

08 May, 2014

1 commit

  • 552a51570   ath9k: Allow platform override without EEPROM override ... Browse Code »

    Add a new platform data flag "use_eeprom" that indicates that the eeprom
    found on the card itself should be used instead of the one present in
    the platform data.

    This allows to override the MAC address of a PCI card while preserving
    the eeprom data from the card itself.

    The default behavior is preserved.

    Signed-off-by: Helmut Schaa
    Signed-off-by: John W. Linville

    Helmut Schaa
     

10 Dec, 2013

1 commit

  • 0f978bfaf   ath9k: Use a separate TX gain table for WZR-HP-G450H ... Browse Code »

    The Buffalo device WZR-HP-G450H uses the index 3 for TX gain,
    which is set to the high_power table currently. Later variants
    of the router use the same index, but instead refer to the
    low_ob_db gain table. This is not handled in the driver since
    there is no way to distinguish board revisions and the high_power
    table is used (incorrectly) for the newer variants.

    By default, devices based on AR9300 using the TX gain index 3 have
    to use the high_power table. To make sure that WZR-HP-G450H is not
    broken when the high_power table is updated, use a separate array
    based on information obtained from the platform data.

    The current situation where only the original variant of WZR-HP-G450H
    works properly stays unchanged.

    Signed-off-by: Sujith Manoharan
    Signed-off-by: John W. Linville

    Sujith Manoharan
     

11 Dec, 2012

1 commit

  • ab5c4f71d   ath9k: allow to load EEPROM content via firmware API ... Browse Code »

    The calibration data for devices w/o a separate
    EEPROM chip can be specified via the 'eeprom_data'
    field of 'ath9k_platform_data'. The 'eeprom_data'
    is usually filled from board specific setup
    functions. It is easy if the EEPROM data is mapped
    to the memory, but it can be complicated if it is
    stored elsewhere.

    The patch adds support for loading of the EEPROM
    data via the firmware API to avoid this limitation.

    Signed-off-by: Gabor Juhos
    Signed-off-by: John W. Linville

    Gabor Juhos
     

23 Jun, 2011

2 commits

  • 7d95847c9   ath9k: add external_reset callback to ath9k_platfom_data for AR9330 ... Browse Code »

    The patch adds a callback to ath9k_platform_data. If the
    callback is provided by the platform code, then it can be
    used to hard reset the WMAC device.

    The callback is required for doing a hard reset of the AR9330
    chips to get them working again after a hang.

    Signed-off-by: Gabor Juhos
    Signed-off-by: John W. Linville

    Gabor Juhos
     
  • 3762561aa   ath9k: add MAC revision detection for AR9330 ... Browse Code »

    The AR9330 1.0 and 1.1 are using the same revision,
    thus it is not possible to distinguish the two chips.
    The platform setup code can distinguish the chips based
    on the SoC revision.

    Add a callback function to ath9k_platform_data in order
    to allow getting the revision number from the platform code.

    Signed-off-by: Gabor Juhos
    Signed-off-by: John W. Linville

    Gabor Juhos
     

26 Apr, 2011

1 commit

31 Mar, 2011

2 commits

30 Jan, 2009

1 commit

  • 9dbeb91a8   ath9k: get EEPROM contents from platform data on AHB bus ... Browse Code »

    On the AR913x SOCs we have to provide EEPROM contents via platform_data,
    because accessing the flash via MMIO is not safe. Additionally different
    boards may store the radio calibration data at different locations.

    Changes-licensed-under: ISC

    Signed-off-by: Gabor Juhos
    Signed-off-by: Imre Kaloz
    Tested-by: Pavel Roskin
    Signed-off-by: John W. Linville

    Gabor Juhos