forked from luck/tmp_suning_uos_patched
c132419e56
The init_phy() function attaches to the PHY, then configures the SerDes<->TBI link (in SGMII mode). The TBI is on the MDIO bus with the PHY (sort of) and is accessed via the gianfar's MDIO registers, using the functions gfar_local_mdio_read/write(), which don't do any locking. The previously attached PHY will start a work-queue on a timer, and probably an irq handler as well, which will talk to the PHY and thus use the MDIO bus. This uses phy_read/write(), which have locking, but not against the gfar_local_mdio versions. The result is that PHY code will try to use the MDIO bus at the same time as the SerDes setup code, corrupting the transfers. Setting up the SerDes before attaching to the PHY will insure that there is no race between the SerDes code and *our* PHY, but doesn't fix everything. Typically the PHYs for all gianfar devices are on the same MDIO bus, which is associated with the first gianfar device. This means that the first gianfar's SerDes code could corrupt the MDIO transfers for a different gianfar's PHY. The lock used by phy_read/write() is contained in the mii_bus structure, which is pointed to by the PHY. This is difficult to access from the gianfar drivers, as there is no link between a gianfar device and the mii_bus which shares the same MDIO registers. As far as the device layer and drivers are concerned they are two unrelated devices (which happen to share registers). Generally all gianfar devices' PHYs will be on the bus associated with the first gianfar. But this might not be the case, so simply locking the gianfar's PHY's mii bus might not lock the mii bus that the SerDes setup code is going to use. We solve this by having the code that creates the gianfar platform device look in the device tree for an mdio device that shares the gianfar's registers. If one is found the ID of its platform device is saved in the gianfar's platform data. A new function in the gianfar mii code, gfar_get_miibus(), can use the bus ID to search through the platform devices for a gianfar_mdio device with the right ID. The platform device's driver data is the mii_bus structure, which the SerDes setup code can use to lock the current bus. Signed-off-by: Trent Piepho <tpiepho@freescale.com> CC: Andy Fleming <afleming@freescale.com> Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
137 lines
3.8 KiB
C
137 lines
3.8 KiB
C
/*
|
|
* include/linux/fsl_devices.h
|
|
*
|
|
* Definitions for any platform device related flags or structures for
|
|
* Freescale processor devices
|
|
*
|
|
* Maintainer: Kumar Gala <galak@kernel.crashing.org>
|
|
*
|
|
* Copyright 2004 Freescale Semiconductor, 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 _FSL_DEVICE_H_
|
|
#define _FSL_DEVICE_H_
|
|
|
|
#include <linux/types.h>
|
|
#include <linux/phy.h>
|
|
|
|
/*
|
|
* Some conventions on how we handle peripherals on Freescale chips
|
|
*
|
|
* unique device: a platform_device entry in fsl_plat_devs[] plus
|
|
* associated device information in its platform_data structure.
|
|
*
|
|
* A chip is described by a set of unique devices.
|
|
*
|
|
* Each sub-arch has its own master list of unique devices and
|
|
* enumerates them by enum fsl_devices in a sub-arch specific header
|
|
*
|
|
* The platform data structure is broken into two parts. The
|
|
* first is device specific information that help identify any
|
|
* unique features of a peripheral. The second is any
|
|
* information that may be defined by the board or how the device
|
|
* is connected externally of the chip.
|
|
*
|
|
* naming conventions:
|
|
* - platform data structures: <driver>_platform_data
|
|
* - platform data device flags: FSL_<driver>_DEV_<FLAG>
|
|
* - platform data board flags: FSL_<driver>_BRD_<FLAG>
|
|
*
|
|
*/
|
|
|
|
struct gianfar_platform_data {
|
|
/* device specific information */
|
|
u32 device_flags;
|
|
/* board specific information */
|
|
u32 board_flags;
|
|
int mdio_bus; /* Bus controlled by us */
|
|
char bus_id[MII_BUS_ID_SIZE]; /* Bus PHY is on */
|
|
u32 phy_id;
|
|
u8 mac_addr[6];
|
|
phy_interface_t interface;
|
|
};
|
|
|
|
struct gianfar_mdio_data {
|
|
/* board specific information */
|
|
int irq[32];
|
|
};
|
|
|
|
/* Flags related to gianfar device features */
|
|
#define FSL_GIANFAR_DEV_HAS_GIGABIT 0x00000001
|
|
#define FSL_GIANFAR_DEV_HAS_COALESCE 0x00000002
|
|
#define FSL_GIANFAR_DEV_HAS_RMON 0x00000004
|
|
#define FSL_GIANFAR_DEV_HAS_MULTI_INTR 0x00000008
|
|
#define FSL_GIANFAR_DEV_HAS_CSUM 0x00000010
|
|
#define FSL_GIANFAR_DEV_HAS_VLAN 0x00000020
|
|
#define FSL_GIANFAR_DEV_HAS_EXTENDED_HASH 0x00000040
|
|
#define FSL_GIANFAR_DEV_HAS_PADDING 0x00000080
|
|
#define FSL_GIANFAR_DEV_HAS_MAGIC_PACKET 0x00000100
|
|
|
|
/* Flags in gianfar_platform_data */
|
|
#define FSL_GIANFAR_BRD_HAS_PHY_INTR 0x00000001 /* set or use a timer */
|
|
#define FSL_GIANFAR_BRD_IS_REDUCED 0x00000002 /* Set if RGMII, RMII */
|
|
|
|
struct fsl_i2c_platform_data {
|
|
/* device specific information */
|
|
u32 device_flags;
|
|
};
|
|
|
|
/* Flags related to I2C device features */
|
|
#define FSL_I2C_DEV_SEPARATE_DFSRR 0x00000001
|
|
#define FSL_I2C_DEV_CLOCK_5200 0x00000002
|
|
|
|
enum fsl_usb2_operating_modes {
|
|
FSL_USB2_MPH_HOST,
|
|
FSL_USB2_DR_HOST,
|
|
FSL_USB2_DR_DEVICE,
|
|
FSL_USB2_DR_OTG,
|
|
};
|
|
|
|
enum fsl_usb2_phy_modes {
|
|
FSL_USB2_PHY_NONE,
|
|
FSL_USB2_PHY_ULPI,
|
|
FSL_USB2_PHY_UTMI,
|
|
FSL_USB2_PHY_UTMI_WIDE,
|
|
FSL_USB2_PHY_SERIAL,
|
|
};
|
|
|
|
struct fsl_usb2_platform_data {
|
|
/* board specific information */
|
|
enum fsl_usb2_operating_modes operating_mode;
|
|
enum fsl_usb2_phy_modes phy_mode;
|
|
unsigned int port_enables;
|
|
};
|
|
|
|
/* Flags in fsl_usb2_mph_platform_data */
|
|
#define FSL_USB2_PORT0_ENABLED 0x00000001
|
|
#define FSL_USB2_PORT1_ENABLED 0x00000002
|
|
|
|
struct fsl_spi_platform_data {
|
|
u32 initial_spmode; /* initial SPMODE value */
|
|
u16 bus_num;
|
|
bool qe_mode;
|
|
/* board specific information */
|
|
u16 max_chipselect;
|
|
void (*activate_cs)(u8 cs, u8 polarity);
|
|
void (*deactivate_cs)(u8 cs, u8 polarity);
|
|
u32 sysclk;
|
|
};
|
|
|
|
struct mpc8xx_pcmcia_ops {
|
|
void(*hw_ctrl)(int slot, int enable);
|
|
int(*voltage_set)(int slot, int vcc, int vpp);
|
|
};
|
|
|
|
/* Returns non-zero if the current suspend operation would
|
|
* lead to a deep sleep (i.e. power removed from the core,
|
|
* instead of just the clock).
|
|
*/
|
|
int fsl_deep_sleep(void);
|
|
|
|
#endif /* _FSL_DEVICE_H_ */
|