All of lore.kernel.org
 help / color / mirror / Atom feed
From: anarsoul@gmail.com (Vasily Khoruzhick)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c-s3c2410: Enable i2c clock only on xfer
Date: Tue, 20 Apr 2010 14:35:26 +0300	[thread overview]
Message-ID: <201004201435.32697.anarsoul@gmail.com> (raw)
In-Reply-To: <20100420093936.GE6684@trinity.fluff.org>

? ????????? ?? 20 ?????? 2010 12:39:36 ????? Ben Dooks ???????:
> On Sat, Apr 17, 2010 at 11:42:32PM +0300, Vasily Khoruzhick wrote:
> > I don't see any reason to keep i2c clock enabled all the time when i2c
> > bus driver is loaded, and even more: it prevents me to disable uda1380
> > codec power - uda1380 doesn't respond on i2c xfers if its power was
> > disabled during i2c clock is enabled.
> 
> Weird. The SCL line should only be clocked when the block is generating
> transfers.

Yeah, it should be so, but there's a fact - codec doesn't respond on i2c after 
its power off/power on sequence without this patch, and it responds with 
patch.
I suppose I can monitor SDA/SCL state via reading GPE15/GPE14 pin status, I'll 
investigate on it a bit more...

> It is probably worth moving the clk_enable() outside the loop to avoid
> calling it each time we try an transfer.

Ok.

> I'm not sure, but I think the clock should also be enabled when reading
> or writing registers. I'd be happier to see a patch where the setup
> functions also ensure that the clock is enabled.

Ok

Regards,
Vasily
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100420/b0067cbd/attachment.sig>

      reply	other threads:[~2010-04-20 11:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17 20:42 [PATCH] i2c-s3c2410: Enable i2c clock only on xfer Vasily Khoruzhick
2010-04-20  9:39 ` Ben Dooks
2010-04-20 11:35   ` Vasily Khoruzhick [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=201004201435.32697.anarsoul@gmail.com \
    --to=anarsoul@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.