From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv7 17/21] ARM: OMAP4: TWL: enable high speed mode for PMIC communication
Date: Wed, 26 Sep 2012 15:06:28 +0300 [thread overview]
Message-ID: <1348661188.1956.1.camel@sokoban> (raw)
In-Reply-To: <5062E95C.6050903@ti.com>
On Wed, 2012-09-26 at 14:39 +0300, Peter Ujfalusi wrote:
> Hi Tero,
>
> On 09/25/2012 07:33 PM, Tero Kristo wrote:
> > With the new parameters, I2C can now be put to high speed mode for
> > better performance.
>
> We have twl6040 on the same bus. have you tried this with audio enabled?
> twl6040 is in standard mode (up to 100 kbps) after power up...
No, I don't have capability to try out audio. Can you give it a shot and
see what happens? Otherwise we probably just have to drop this patch out
for now.
-Tero
>
> >
> > Signed-off-by: Tero Kristo <t-kristo@ti.com>
> > ---
> > arch/arm/mach-omap2/omap_twl.c | 1 +
> > 1 files changed, 1 insertions(+), 0 deletions(-)
> >
> > diff --git a/arch/arm/mach-omap2/omap_twl.c b/arch/arm/mach-omap2/omap_twl.c
> > index 611cb63..7ff9667 100644
> > --- a/arch/arm/mach-omap2/omap_twl.c
> > +++ b/arch/arm/mach-omap2/omap_twl.c
> > @@ -218,6 +218,7 @@ static struct omap_voltdm_pmic omap4_core_pmic = {
> > .i2c_slave_addr = OMAP4_SRI2C_SLAVE_ADDR,
> > .volt_reg_addr = OMAP4_VDD_CORE_SR_VOLT_REG,
> > .cmd_reg_addr = OMAP4_VDD_CORE_SR_CMD_REG,
> > + .i2c_high_speed = true,
> > .i2c_pad_load = 3,
> > .vsel_to_uv = twl6030_vsel_to_uv,
> > .uv_to_vsel = twl6030_uv_to_vsel,
> >
>
>
next prev parent reply other threads:[~2012-09-26 12:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 16:33 [PATCHv7 00/21] ARM: OMAP3+: auto retention support Tero Kristo
2012-09-25 16:33 ` [PATCHv7 01/21] ARM: OMAP3+: PM: VP: use uV for max and min voltage limits Tero Kristo
2012-09-25 16:33 ` [PATCHv7 02/21] ARM: OMAP: voltage: renamed vp_vddmin and vp_vddmax fields Tero Kristo
2012-09-25 16:33 ` [PATCHv7 03/21] ARM: OMAP3+: voltage: introduce omap vc / vp params for voltagedomains Tero Kristo
2012-09-25 16:33 ` [PATCHv7 04/21] ARM: OMAP3: VC: calculate ramp times Tero Kristo
2012-09-25 16:33 ` [PATCHv7 05/21] ARM: OMAP4: voltage: add support for VOLTSETUP_x_OFF register Tero Kristo
2012-09-25 16:33 ` [PATCHv7 06/21] ARM: OMAP4: VC: calculate ramp times Tero Kristo
2012-09-25 16:33 ` [PATCHv7 07/21] ARM: OMAP: add support for oscillator setup Tero Kristo
2012-09-25 16:33 ` [PATCHv7 08/21] ARM: OMAP3+: vp: use new vp_params for calculating vddmin and vddmax Tero Kristo
2012-09-25 16:33 ` [PATCHv7 09/21] ARM: OMAP3+: voltage: use oscillator data to calculate setup times Tero Kristo
2012-09-25 16:33 ` [PATCHv7 10/21] ARM: OMAP: TWL: change the vddmin / vddmax voltages to spec Tero Kristo
2012-09-25 16:33 ` [PATCHv7 11/21] TEMP: ARM: OMAP3: beagle rev-c4: enable OPP6 Tero Kristo
2012-09-25 16:33 ` [PATCHv7 12/21] ARM: OMAP: beagle: set oscillator startup time to 10ms for rev c4 Tero Kristo
2012-09-25 16:33 ` [PATCHv7 13/21] ARM: OMAP3: vc: auto_ret / auto_off support Tero Kristo
2012-09-25 16:33 ` [PATCHv7 14/21] ARM: OMAP3+: voltage: remove unused volt_setup_time parameter Tero Kristo
2012-09-25 16:33 ` [PATCHv7 15/21] ARM: OMAP4: vc: fix channel configuration Tero Kristo
2012-09-25 16:33 ` [PATCHv7 16/21] ARM: OMAP4: VC: setup I2C parameters based on board data Tero Kristo
2012-09-25 16:33 ` [PATCHv7 17/21] ARM: OMAP4: TWL: enable high speed mode for PMIC communication Tero Kristo
2012-09-26 11:39 ` Peter Ujfalusi
2012-09-26 12:06 ` Tero Kristo [this message]
2012-09-26 12:23 ` Peter Ujfalusi
2012-09-25 16:33 ` [PATCHv7 18/21] ARM: OMAP4: OPP: add OMAP4460 definitions Tero Kristo
2012-09-25 16:33 ` [PATCHv7 19/21] ARM: OMAP3+: PM: introduce a central pmic control Tero Kristo
2012-09-25 16:33 ` [PATCHv7 20/21] ARM: OMAP2+ PM: Add support for TPS62361 Tero Kristo
2012-09-25 16:33 ` [PATCHv7 21/21] ARM: OMAP4: vc: auto retention support Tero Kristo
2012-11-06 1:02 ` [PATCHv7 00/21] ARM: OMAP3+: " Kevin Hilman
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=1348661188.1956.1.camel@sokoban \
--to=t-kristo@ti.com \
--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