mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-01 07:46:46 +07:00
0c2bec9694
In certain cases it is required to perform board specific actions before activating libertas G-SPI interface. These actions may include power up of the chip, GPIOs setup, proper pin-strapping and SPI controller config. This patch adds ability to call board specific setup/teardown methods Signed-off-by: Mike Rapoport <mike@compulab.co.il> Acked-by: Andrey Yurovsky <andrey@cozybit.com> Acked-by: Dan Williams <dcbw@redhat.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
33 lines
963 B
C
33 lines
963 B
C
/*
|
|
* board-specific data for the libertas_spi driver.
|
|
*
|
|
* Copyright 2008 Analog Devices Inc.
|
|
*
|
|
* This program is free software; you can redistribute it and/or modify
|
|
* it under the terms of the GNU General Public License as published by
|
|
* the Free Software Foundation; either version 2 of the License, or (at
|
|
* your option) any later version.
|
|
*/
|
|
#ifndef _LIBERTAS_SPI_H_
|
|
#define _LIBERTAS_SPI_H_
|
|
|
|
struct spi_device;
|
|
|
|
struct libertas_spi_platform_data {
|
|
/* There are two ways to read data from the WLAN module's SPI
|
|
* interface. Setting 0 or 1 here controls which one is used.
|
|
*
|
|
* Usually you want to set use_dummy_writes = 1.
|
|
* However, if that doesn't work or if you are using a slow SPI clock
|
|
* speed, you may want to use 0 here. */
|
|
u16 use_dummy_writes;
|
|
|
|
/* GPIO number to use as chip select */
|
|
u16 gpio_cs;
|
|
|
|
/* Board specific setup/teardown */
|
|
int (*setup)(struct spi_device *spi);
|
|
int (*teardown)(struct spi_device *spi);
|
|
};
|
|
#endif
|