From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: linuxppc-dev list <Linuxppc-dev@ozlabs.org>,
Linux I2C <i2c@lm-sensors.org>
Subject: Re: [PATCH] Convert i2c-mpc from a platform driver to an of_platform one
Date: Sat, 28 Jun 2008 22:57:09 -0600 [thread overview]
Message-ID: <fa686aa40806282157y65835a73y6391e22cdf55b571@mail.gmail.com> (raw)
In-Reply-To: <9e4733910806101940o7f2f9863jb5e556ee2fc39a7e@mail.gmail.com>
On Tue, Jun 10, 2008 at 8:40 PM, Jon Smirl <jonsmirl@gmail.com> wrote:
> Convert i2c-mpc from a platform driver into an of_platform driver.
> This patch is much smaller since Jochen already added
> of_find_i2c_driver(). Versions of this have been posted before.
>
> Signed-ff-by: Jon Smirl <jonsmirl@gmail.com>
>
> --
> + if (of_device_is_compatible(op->node, "mpc5200-i2c"))
> + i2c->flags |= FSL_I2C_DEV_CLOCK_5200;
This needs to also test for "fsl,mpc5200-i2c". "mpc5200-i2c" isn't
used on current device trees, but there may be some deployed boards
which still have this string.
> +static const struct of_device_id mpc_i2c_of_match[] = {
> + {
> + .compatible = "fsl-i2c",
> + },
You can probably shorten this by 2 lines if you change it to:
+ { .compatible = "fsl-i2c", },
Doing so makes it more readable when you need to add additional
compatible values.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2008-06-29 4:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 2:40 [PATCH] Convert i2c-mpc from a platform driver to an of_platform one Jon Smirl
2008-06-11 16:00 ` [i2c] " Wolfram Sang
2008-06-11 16:14 ` Jon Smirl
2008-06-25 13:25 ` Jean Delvare
2008-06-25 13:58 ` Jean Delvare
2008-06-29 2:05 ` Jon Smirl
2008-06-29 4:49 ` Grant Likely
2008-06-29 6:31 ` Jean Delvare
2008-06-29 6:58 ` Grant Likely
2008-06-29 7:17 ` Jean Delvare
2008-06-29 16:24 ` Sean MacLennan
2008-06-29 16:35 ` Jean Delvare
2008-06-30 2:51 ` David Brownell
2008-06-29 4:57 ` Grant Likely [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=fa686aa40806282157y65835a73y6391e22cdf55b571@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=Linuxppc-dev@ozlabs.org \
--cc=i2c@lm-sensors.org \
--cc=jonsmirl@gmail.com \
/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).