summaryrefslogtreecommitdiff
path: root/drivers/net/fsl_mdio.c
diff options
context:
space:
mode:
authorClaudiu Manoil <claudiu.manoil@freescale.com>2013-09-30 12:44:42 +0300
committerJoe Hershberger <joe.hershberger@ni.com>2013-11-22 17:03:15 -0600
commitaec84bf6719f9efcc754acfb08b8ca866c8a5e95 (patch)
tree8abc6da1f65037bb93761fdd7b3e74df377eebe1 /drivers/net/fsl_mdio.c
parentb200204e8e2a2eee081d576ed578d87b75813b46 (diff)
downloadu-boot-aec84bf6719f9efcc754acfb08b8ca866c8a5e95.tar.gz
u-boot-aec84bf6719f9efcc754acfb08b8ca866c8a5e95.tar.bz2
u-boot-aec84bf6719f9efcc754acfb08b8ca866c8a5e95.zip
net: tsec: Cleanup tsec regs init and fix __iomem warns
Remove tsec_t typedef. Define macros as getters of tsec and mdio register memory regions, for consistent initialization of various 'regs' fields and also to manage overly long initialization lines. Use the __iomem address space marker to address sparse warnings in tsec.c where IO accessors are used, like: tsec.c:394:19: warning: incorrect type in argument 1 (different address spaces) tsec.c:394:19: expected unsigned int volatile [noderef] <asn:2>*addr tsec.c:394:19: got unsigned int *<noident> [...] Add the __iomem address space marker for the tsec pointers to struct tsec_mii_mng memory mapped register regions. This solves the sparse warnings for mixig normal pointers with __iomem pointers for tsec. Signed-off-by: Claudiu Manoil <claudiu.manoil@freescale.com>
Diffstat (limited to 'drivers/net/fsl_mdio.c')
0 files changed, 0 insertions, 0 deletions