[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1158817598.11110.7.camel@localhost.localdomain>
Date: 21 Sep 2006 13:46:39 +0800
From: Zang Roy-r61911 <tie-fei.zang@...escale.com>
To: Jeff Garzik <jgarzik@...ox.com>
Cc: Roland Dreier <rdreier@...co.com>, Andrew Morton <akpm@...l.org>,
netdev <netdev@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [patch 3/3] Add tsi108 On Chip Ethernet device driver support
On Thu, 2006-09-21 at 12:26, Jeff Garzik wrote:
> Zang Roy-r61911 wrote:
> > +#define TSI108_ETH_WRITE_REG(offset, val) \
> > + writel(le32_to_cpu(val),data->regs + (offset))
> > +
> > +#define TSI108_ETH_READ_REG(offset) \
> > + le32_to_cpu(readl(data->regs + (offset)))
> > +
> > +#define TSI108_ETH_WRITE_PHYREG(offset, val) \
> > + writel(le32_to_cpu(val), data->phyregs + (offset))
> > +
> > +#define TSI108_ETH_READ_PHYREG(offset) \
> > + le32_to_cpu(readl(data->phyregs + (offset)))
>
>
> NAK:
>
> 1) writel() and readl() are defined to be little endian.
>
> If your platform is different, then your platform should have its own
> foobus_writel() and foobus_readl().
Tsi108 bridge is designed for powerpc platform. Originally, I use
out_be32() and in_be32(). While there is no obvious reason to object
using this bridge in a little endian system. Maybe some extra hardware
logic needed for the bus interface. le32_to_cpu() can be aware the
endian difference.
Any comment?
>
> 2) TSI108_ETH_WRITE_REG() is just way too long. TSI_READ(),
> TSI_WRITE(), TSI_READ_PHY() and TSI_WRITE_PHY() would be far more
> readable.
>
> More in next email.
>
I will modify the name.
Roy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists