From: Mark Rutland <mark.rutland@arm.com>
To: "atull@opensource.altera.com" <atull@opensource.altera.com>
Cc: "wsa@the-dreams.de" <wsa@the-dreams.de>,
"baruch@tkos.co.il" <baruch@tkos.co.il>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"skuribay@pobox.com" <skuribay@pobox.com>,
"Romain.Baeriswyl@abilis.com" <Romain.Baeriswyl@abilis.com>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"alan@linux.intel.com" <alan@linux.intel.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"delicious.quinoa@gmail.com" <delicious.quinoa@gmail.com>,
"dinguyen@opensource.altera.com" <dinguyen@opensource.altera.com>,
"yvanderv@opensource.altera.com" <yvanderv@opensource.altera.com>
Subject: Re: [PATCH] i2c: designware: deduce speed mode from device tree setting
Date: Wed, 20 Aug 2014 10:22:57 +0100 [thread overview]
Message-ID: <20140820092257.GA21174@leverpostej> (raw)
In-Reply-To: <1408479529-24249-1-git-send-email-atull@opensource.altera.com>
On Tue, Aug 19, 2014 at 09:18:49PM +0100, atull@opensource.altera.com wrote:
> From: Alan Tull <atull@opensource.altera.com>
>
> Use the documented, but unimplemented "clock-frequency"
> Device Tree setting as a guide on whether to set the speed
> mode bits in DW_IC_CON to standard or fast i2c mode.
>
> Previously, the driver was hardwired to fast mode. Default
> to fast mode if the "clock-frequency" property is not present
> for backwards compatiblity.
>
> Signed-off-by: Alan Tull <atull@opensource.altera.com>
> ---
> drivers/i2c/busses/i2c-designware-platdrv.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-designware-platdrv.c b/drivers/i2c/busses/i2c-designware-platdrv.c
> index bc87733..18cd3d9 100644
> --- a/drivers/i2c/busses/i2c-designware-platdrv.c
> +++ b/drivers/i2c/busses/i2c-designware-platdrv.c
> @@ -122,7 +122,8 @@ static int dw_i2c_probe(struct platform_device *pdev)
> struct dw_i2c_dev *dev;
> struct i2c_adapter *adap;
> struct resource *mem;
> - int irq, r;
> + int irq, r, ret, speed = DW_IC_CON_SPEED_FAST;
> + u32 bus_rate;
>
> irq = platform_get_irq(pdev, 0);
> if (irq < 0) {
> @@ -167,6 +168,11 @@ static int dw_i2c_probe(struct platform_device *pdev)
> of_property_read_u32(pdev->dev.of_node,
> "i2c-scl-falling-time-ns",
> &dev->scl_falling_time);
> +
> + ret = of_property_read_u32(pdev->dev.of_node,
> + "clock-frequency", &bus_rate);
> + if (!ret && (bus_rate <= 100000))
> + speed = DW_IC_CON_SPEED_STD;
This looks a bit odd.
If the device only supports two particular speeds why do we accept any
other speed in the clock-frequency property? Surely we should at least
warn that something was off?
Thanks,
Mark
> }
>
> dev->functionality =
> @@ -177,7 +183,7 @@ static int dw_i2c_probe(struct platform_device *pdev)
> I2C_FUNC_SMBUS_WORD_DATA |
> I2C_FUNC_SMBUS_I2C_BLOCK;
> dev->master_cfg = DW_IC_CON_MASTER | DW_IC_CON_SLAVE_DISABLE |
> - DW_IC_CON_RESTART_EN | DW_IC_CON_SPEED_FAST;
> + DW_IC_CON_RESTART_EN | speed;
>
> /* Try first if we can configure the device from ACPI */
> r = dw_i2c_acpi_configure(pdev);
> --
> 1.7.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-08-20 9:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 20:18 [PATCH] i2c: designware: deduce speed mode from device tree setting atull
2014-08-20 7:52 ` Mika Westerberg
2014-08-20 9:22 ` Mark Rutland [this message]
2014-08-20 9:49 ` Romain Baeriswyl
2014-08-20 12:07 ` Romain Baeriswyl
2014-08-20 12:32 ` Wolfram Sang
2014-08-20 14:24 ` atull
2014-08-20 14:38 ` Romain Baeriswyl
2014-08-20 15:12 ` atull
2014-08-20 12:36 ` Wolfram Sang
2014-08-20 12:42 ` Mark Rutland
2014-08-20 14:29 ` [PATCH] i2c designware add support of I2C standard mode Romain Baeriswyl
2014-08-20 14:32 ` atull
2014-08-20 15:25 ` atull
2014-09-18 15:52 ` atull
2014-09-20 9:24 ` Wolfram Sang
2014-09-28 3:40 ` atull
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=20140820092257.GA21174@leverpostej \
--to=mark.rutland@arm.com \
--cc=Romain.Baeriswyl@abilis.com \
--cc=alan@linux.intel.com \
--cc=atull@opensource.altera.com \
--cc=baruch@tkos.co.il \
--cc=delicious.quinoa@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@opensource.altera.com \
--cc=grant.likely@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robh+dt@kernel.org \
--cc=skuribay@pobox.com \
--cc=wsa@the-dreams.de \
--cc=yvanderv@opensource.altera.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