mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Anthony Olech <anthony.olech.opensource@diasemi.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [NEW DRIVER V1 4/7] DA9058 RTC driver
Date: Thu, 2 Aug 2012 17:13:55 +0100	[thread overview]
Message-ID: <20120802161355.GD4537@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201208020849.q728nhll007819@latitude.olech.com>

On Thu, Aug 02, 2012 at 09:48:56AM +0100, Anthony Olech wrote:

> -comment "I2C RTC drivers"
> -	depends on I2C
> -
> -if I2C
> -
>  config RTC_DRV_88PM860X
>  	tristate "Marvell 88PM860x"
>  	depends on RTC_CLASS && I2C && MFD_88PM860X
> @@ -135,6 +130,21 @@ config RTC_DRV_88PM860X
>  	  This driver can also be built as a module. If so, the module
>  	  will be called rtc-88pm860x.
>  
> +comment "I2C RTC drivers"
> +	depends on I2C
> +
> +if I2C
> +

Hrm?

> +	dev_info(dev, "Read RTC: %02x %02x %02x %02x %02x %02x\n",
> +		rtc_time[0], rtc_time[1], rtc_time[2],
> +		rtc_time[3], rtc_time[4], rtc_time[5]);

This is way too noisy to be doing every time you read the RTC.

> +	dev_info(dev, "Setting RTC: %02x %02x %02x %02x %02x %02x\n",
> +		rtc_time[0], rtc_time[1], rtc_time[2], rtc_time[3],
> +		rtc_time[4], rtc_time[5]);

Similarly here...

> +	ret = da9058_bulk_write(da9058, DA9058_COUNTS_REG, rtc_time, 6);
> +	if (ret) {
> +		dev_dbg(dev, "failed %d to write to RTC\n", ret);

...especially given that things like actual error messages are at debug
level!

> +static int da9058_rtc_proc(struct device *dev, struct seq_file *seq)
> +{
> +	seq_printf(seq, "Tony Olech was here\n");
> +
> +	return 0;
> +}

Perhaps the driver needs some cleanup...

      reply	other threads:[~2012-08-02 16:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02  8:48 Anthony Olech
2012-08-02 16:13 ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120802161355.GD4537@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=anthony.olech.opensource@diasemi.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome