From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 2/3] i2c: mux: demux-pinctrl: add driver
Date: Wed, 1 Jul 2015 12:07:08 +0200 [thread overview]
Message-ID: <20150701100707.GA1926@katana> (raw)
In-Reply-To: <CAMuHMdW+rd+U0VQjitbyJ3AiZakhLztdYe27n1rkK9tFWT=z4w@mail.gmail.com>
> > +Changing I2C controllers:
> > +
> > +The created mux-device will have a file "cur_master" in its sysfs-entry. Write
> > +0 there for the first master listed in the "i2c-parent" property, 1 for the
> > +second etc. Reading the file will give you a list with the active master
> > +marked.
>
> This paragraph doesn't belong in the DT binding doc, but somewhere
> under Documentation/i2c/
Yes.
> > +struct i2c_demux_pinctrl_priv {
> > + int cur_chan;
> > + int num_chan;
>
> unsigned int
When comparing variables, I prefer to have them the same signedness.
> > +static struct property status_okay = { .name = "status", .length = 3, .value = "ok" };
>
> "okay" or "ok"?
Both are valid, I took the shorter one.
> > + struct i2c_demux_pinctrl_priv *priv = dev_get_drvdata(dev);
> > + int count = 0, i;
>
> unsigned int i
Same as above.
>
> > +
> > + for (i = 0; i < priv->num_chan; i++)
> > + count += sprintf(buf + count, "%c %d - %s\n",
> > + i == priv->cur_chan ? '*' : ' ', i,
> > + priv->chan[i].parent_np->full_name);
> > + //FIXME: Check count > PAGE_SIZE
>
> Can you use seq_printf() for device attributes?
I can't find a reference to that.
> > +static ssize_t cur_master_store(struct device *dev, struct device_attribute *attr,
> > + const char *buf, size_t count)
> > +{
> > + struct i2c_demux_pinctrl_priv *priv = dev_get_drvdata(dev);
> > + unsigned long val;
>
> unsigned int
>
> > + int ret;
> > +
> > + ret = kstrtoul(buf, 0, &val);
>
> kstrtouint()
Yes, I agree to the last two.
Thanks for the review,
Wolfram
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150701/fa07ecde/attachment.sig>
next prev parent reply other threads:[~2015-07-01 10:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 21:44 [RFC 0/3] switch I2C IP cores at runtime Wolfram Sang
2015-06-30 21:44 ` [RFC 1/3] of: make of_mutex public Wolfram Sang
2015-07-03 4:43 ` Rob Herring
2015-07-03 6:54 ` Pantelis Antoniou
2015-07-03 7:24 ` Wolfram Sang
2015-06-30 21:44 ` [RFC 2/3] i2c: mux: demux-pinctrl: add driver Wolfram Sang
2015-07-01 7:08 ` Geert Uytterhoeven
2015-07-01 10:07 ` Wolfram Sang [this message]
2015-06-30 21:44 ` [RFC 3/3] ARM: shmobile: r8a7790: rework dts to use i2c demuxer Wolfram Sang
2015-07-01 7:10 ` Geert Uytterhoeven
2015-07-01 10:08 ` Wolfram Sang
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=20150701100707.GA1926@katana \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).