[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110119104823.GD2833@S2101-09.ap.freescale.net>
Date: Wed, 19 Jan 2011 18:48:24 +0800
From: Shawn Guo <shawn.guo@...escale.com>
To: Sascha Hauer <s.hauer@...gutronix.de>
CC: <gerg@...pgear.com>, <B32542@...escale.com>,
<netdev@...r.kernel.org>, <bryan.wu@...onical.com>,
<jamie@...reable.org>, <baruch@...s.co.il>,
<w.sang@...gutronix.de>, <r64343@...escale.com>, <eric@...rea.com>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>, <jamie@...ieiles.com>,
<davem@...emloft.net>, <linux-arm-kernel@...ts.infradead.org>,
<lw@...o-electronics.de>
Subject: Re: [PATCH v4 08/10] ARM: mxs: add ocotp read function
Hi Sascha,
On Fri, Jan 14, 2011 at 09:16:56PM +0800, Shawn Guo wrote:
> On Fri, Jan 14, 2011 at 09:33:20AM +0100, Sascha Hauer wrote:
> > On Thu, Jan 13, 2011 at 04:19:39PM +0100, Uwe Kleine-König wrote:
> > > On Thu, Jan 06, 2011 at 03:13:16PM +0800, Shawn Guo wrote:
> > > > Signed-off-by: Shawn Guo <shawn.guo@...escale.com>
> > > > ---
> > > > Changes for v4:
> > > > - Call cpu_relax() during polling
> > > >
> > > > Changes for v2:
> > > > - Add mutex locking for mxs_read_ocotp()
> > > > - Use type size_t for count and i
> > > > - Add comment for clk_enable/disable skipping
> > > > - Add ERROR bit clearing and polling step
> > > >
> > > > arch/arm/mach-mxs/Makefile | 2 +-
> > > > arch/arm/mach-mxs/include/mach/common.h | 1 +
> > > > arch/arm/mach-mxs/ocotp.c | 79 +++++++++++++++++++++++++++++++
> > > > 3 files changed, 81 insertions(+), 1 deletions(-)
> > > > create mode 100644 arch/arm/mach-mxs/ocotp.c
> > > >
> > > > diff --git a/arch/arm/mach-mxs/Makefile b/arch/arm/mach-mxs/Makefile
> > > > index 39d3f9c..f23ebbd 100644
> > > > --- a/arch/arm/mach-mxs/Makefile
> > > > +++ b/arch/arm/mach-mxs/Makefile
> > > > @@ -1,5 +1,5 @@
> > > > # Common support
> > > > -obj-y := clock.o devices.o gpio.o icoll.o iomux.o system.o timer.o
> > > > +obj-y := clock.o devices.o gpio.o icoll.o iomux.o ocotp.o system.o timer.o
> > > is it worth to make ocotp optional? (and let evk select
> > > CONFIG_MXS_OCOTP)
> >
> > I think not.
> >
> I thought it depends on how we think about it. If we think that
> ocotp is a block of soc and should be on every system based on
> the soc, we should build it unconditional. However, if we think
> ocotp is a function that could either be used on a machine or not,
> it should be built conditional, so that the machine does not use
> ocotp function could save the ocotp build and the memory of
> u32 ocotp_words[0x20].
>
You've not merged patch #8, #9, #10, so you still think
CONFIG_MXS_OCOTP should not be added?
--
Regards,
Shawn
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists