[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120821132222.GF7995@opensource.wolfsonmicro.com>
Date: Tue, 21 Aug 2012 14:22:22 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Felipe Balbi <balbi@...com>
Cc: Sourav Poddar <sourav.poddar@...com>,
devicetree-discuss@...ts.ozlabs.org,
linux-arm-kernel@...ts.infradead.org, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: Re: [PATCH 1/4] mfd: smsc: Add support for smsc gpio io/keypad driver
On Tue, Aug 21, 2012 at 03:42:45PM +0300, Felipe Balbi wrote:
> On Tue, Aug 21, 2012 at 01:41:46PM +0100, Mark Brown wrote:
> > > + regmap_read(smsc->regmap, SMSC_DEV_ID, &ret);
> > > + dev_dbg(&i2c->dev, "SMSC Device ID: %d\n", ret);
> > I'd make these log messages dev_info() or something.
> dev_info() ? It'lll just make boot noisier for no good reason. Which
> user wants to see this during boot up ? That's a debugging feature for
> develop IMHO.
Most of the registers appeared to be chip revision information which is
most definitely useful to tell people about, though possibly with neater
formatting ("why is this batch of boards failing... oh, right"). If
they're fixed device IDs then the driver should instead be verifying
that the registers contain the expected values and bombing out if they
don't. Either way dev_dbg() isn't too helpful.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists