mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: John Watts <contact@jookia.org>
To: Sascha Hauer <sha@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] I2C: i.MX: early: Use internal udelay
Date: Mon, 30 Jan 2023 23:56:20 +1100	[thread overview]
Message-ID: <Y9e+dKTG59Y0Kxhl@novena-choice-citizen> (raw)
In-Reply-To: <20230130123142.GS13319@pengutronix.de>

On Mon, Jan 30, 2023 at 01:31:42PM +0100, Sascha Hauer wrote:
> As said, the code is also for other i.MX SoCs, so a fixed base address
> won't do it. You would first have to detect the SoC type, but we can
> only get this from the device tree.
> 
> I'm afraid there is no good solution for this problem, at least we
> haven't found any over the years.
> 
> Sascha

Oh right, because Barebox does multi-image builds. That is an unsatisfying
problem but it makes sense.

So for this patch I imagine I should just take the udelay you've written,
use the I2C registers as the base address and just poke around for a while?

I'm still unsure on how to test this- can I just disable the MMU and dcache
in board.c and do some prints with some type of timer?

John.



  reply	other threads:[~2023-01-30 17:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 18:56 John Watts
2023-01-30 10:27 ` Sascha Hauer
2023-01-30 10:42   ` John Watts
2023-01-30 12:17     ` Sascha Hauer
2023-01-30 12:24       ` John Watts
2023-01-30 12:31         ` Sascha Hauer
2023-01-30 12:56           ` John Watts [this message]
2023-01-30 16:36             ` Sascha Hauer
2023-01-30 18:42               ` John Watts
2023-01-31  6:14                 ` Sascha Hauer
2023-01-31  6:33                   ` John Watts
2023-02-02 14:21   ` Jules Maselbas
2023-02-02 14:27     ` Ahmad Fatoum
2023-02-01 17:50 ` Alexander Shiyan
2023-02-01 18:12   ` Jookia
2023-02-01 19:44   ` Ahmad Fatoum

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=Y9e+dKTG59Y0Kxhl@novena-choice-citizen \
    --to=contact@jookia.org \
    --cc=barebox@lists.infradead.org \
    --cc=sha@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox