From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Jules Maselbas <jmaselbas@kalray.eu>, Sascha Hauer <sha@pengutronix.de>
Cc: John Watts <contact@jookia.org>, barebox@lists.infradead.org
Subject: Re: [PATCH] I2C: i.MX: early: Use internal udelay
Date: Thu, 2 Feb 2023 15:27:26 +0100 [thread overview]
Message-ID: <f083c41a-3606-f43a-cfb4-1bfc7ccedbcf@pengutronix.de> (raw)
In-Reply-To: <20230202142103.GL4155@tellis.lin.mbt.kalray.eu>
Hello Jules,
On 02.02.23 15:21, Jules Maselbas wrote:
> On Mon, Jan 30, 2023 at 11:27:27AM +0100, Sascha Hauer wrote:
>> The time spent for a register read depends on the bus clock which
>> doesn't change that much between the different SoCs.
>>
>
> Some arm devices have an architecture timer, isn't it possible to use
> the udelay defined in arch/arm/lib64/pbl.c on i.MX ? I am not very
> experienced on ARM cpus, is this only possible on armv7/armv8, and not
> on every i.MX SoCs ?
Cortex-A7 and later i.MX has an ARMv7 architected timer, but "normal"
i.MX6Q/DL with Cortex-A9 doesn't.
Cheers,
Ahmad
>
> Cheers,
> -- Jules
>
>
>
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2023-02-02 14:28 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
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 [this message]
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=f083c41a-3606-f43a-cfb4-1bfc7ccedbcf@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=contact@jookia.org \
--cc=jmaselbas@kalray.eu \
--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