All of lore.kernel.org
 help / color / mirror / Atom feed
From: matti kaasinen <matti.kaasinen@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] am335x board i2c_probe fails from nand boot
Date: Tue, 3 Jan 2017 13:10:18 +0200	[thread overview]
Message-ID: <CADnUhn180Ft-ETF03tX21cw2OLb7O6W-CwYd8sNgsrYz4L=GkQ@mail.gmail.com> (raw)
In-Reply-To: <CAGm1_ks_A5q-eNTxsHV+K9hag5Vw=c6fmrSjF6YmJvhg56geiA@mail.gmail.com>

I could try that, but how does it work properly when I run it from mmc.
Does reading spl from mmc touch I2C somehow (interrupt, speed or anything)
or does reading spl from nand do that.

2017-01-03 13:05 GMT+02:00 Yegor Yefremov <yegorslists@googlemail.com>:

> On Tue, Jan 3, 2017 at 12:02 PM, matti kaasinen
> <matti.kaasinen@gmail.com> wrote:
> >
> > 2017-01-03 12:56 GMT+02:00 Yegor Yefremov <yegorslists@googlemail.com>:
> >>
> >> What PMIC are you using?
> >
> > It is TPS65217, so probe command is:
> >  i2c_probe(TPS65217_CHIP_PM)
>
> I had some problems with tps65910. Anyway try to reduce I2C speed up
> to 1000. The kernel can still run the full speed. It's only for
> bootloader stage.
>
> Yegor
>

  reply	other threads:[~2017-01-03 11:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03  9:26 [U-Boot] am335x board i2c_probe fails from nand boot matti kaasinen
2017-01-03 10:56 ` Yegor Yefremov
2017-01-03 11:02   ` matti kaasinen
2017-01-03 11:05     ` Yegor Yefremov
2017-01-03 11:10       ` matti kaasinen [this message]
2017-01-03 11:16 ` Lokesh Vutla
2017-01-03 12:33   ` matti kaasinen
2017-01-03 13:34     ` matti kaasinen
2017-01-03 14:37       ` matti kaasinen
2017-01-04  4:46         ` Lokesh Vutla
2017-01-04  7:33           ` matti kaasinen
2017-01-05 10:09             ` matti kaasinen
2017-01-05 13:01               ` matti kaasinen
2017-01-04 10:23           ` matti kaasinen

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='CADnUhn180Ft-ETF03tX21cw2OLb7O6W-CwYd8sNgsrYz4L=GkQ@mail.gmail.com' \
    --to=matti.kaasinen@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.