[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150612194439.GA15327@breakpoint.cc>
Date: Fri, 12 Jun 2015 21:44:39 +0200
From: Sebastian Andrzej Siewior <sebastian@...akpoint.cc>
To: Stefan Agner <stefan@...er.ch>
Cc: Sebastian Andrzej Siewior <sebastian@...akpoint.cc>,
dwmw2@...radead.org, computersforpeace@...il.com,
mark.rutland@....com, boris.brezillon@...e-electrons.com,
aaron@...tycactus.com, marb@...at.de, pawel.moll@....com,
ijc+devicetree@...lion.org.uk, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, robh+dt@...nel.org,
linux-mtd@...ts.infradead.org, kernel@...gutronix.de,
galak@...eaurora.org, shawn.guo@...aro.org,
linux-arm-kernel@...ts.infradead.org, bpringlemeir@...ps.com
Subject: Re: [PATCH v4 1/6] mtd: nand: vf610_nfc: Freescale NFC for VF610,
MPC5125 and others
On 2015-06-09 22:31:07 [+0200], Stefan Agner wrote:
> > have the endian swap. So an abstraction like you provided earlier
> > would be nice :)
>
> What do you mean by that?
Something like you did for the reader where you have:
|static inline u32 vf610_nfc_read(struct vf610_nfc *nfc, uint reg)
|{
| return readl(nfc->regs + reg);
|}
instead using readl() directly. So you could also have
|static inline u32 vf610_nfc_read_relaxed(struct vf610_nfc *nfc, uint reg)
|{
| return readl_relaxed(nfc->regs + reg);
|}
Instead of using readl_relaxed(). Unless I'm mistaken, that function was
used more than once. If someone plugs in PPC support he does not need to
add this function anymore but but simply add an ifdef in vf610_nfc_read()
and vf610_nfc_read_relaxed() and replace it whatever works for him.
Sebastian
--
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