mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: cbou@mail.ru, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add I2C driver for Summit Microelectronics SMB347 Battery Charger.
Date: Mon, 6 Feb 2012 16:01:27 +0000	[thread overview]
Message-ID: <20120206160127.GF10173@sirena.org.uk> (raw)
In-Reply-To: <20120206155729.9947.22792.stgit@bob.linux.org.uk>

On Mon, Feb 06, 2012 at 03:59:01PM +0000, Alan Cox wrote:

> Driver support for the Summit I??C battery charger. This is used in some
> Intel devices.

There's quite a lot of read/modify/write cycles and...

> +static int smb347_debugfs_show(struct seq_file *s, void *data)
> +{
> +	struct smb347_charger *smb = s->private;
> +	int ret;
> +	u8 reg;
> +
> +	seq_printf(s, "Control registers:\n");
> +	seq_printf(s, "==================\n");

...this which make me wonder if this might not benefit from using
regmap.  The read/modify/write cycles are handled by regmap_update_bits()
and there's a standard debugfs file for dumping registers.  Should save
a bit of code I think but I'd not worry too much either way.

> +static int __init smb347_init(void)
> +{
> +	return i2c_add_driver(&smb347_driver);
> +}
> +module_init(smb347_init);
> +
> +static void __exit smb347_exit(void)
> +{
> +	i2c_del_driver(&smb347_driver);
> +}
> +module_exit(smb347_exit);

There's module_i2c_driver() (and similarly for SPI and platform) though
that's definitely a nitpick.

  reply	other threads:[~2012-02-06 16:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 15:59 Alan Cox
2012-02-06 16:01 ` Mark Brown [this message]
2012-02-06 16:24   ` Alan Cox
2012-02-06 16:35     ` Mark Brown
2012-02-06 17:05       ` Alan Cox
2012-02-06 17:21         ` Mark Brown
2012-03-13 23:46   ` Anton Vorontsov

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=20120206160127.GF10173@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cbou@mail.ru \
    --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