public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Johannes Krottmayer <krjdev@gmail.com>
To: u-boot@lists.denx.de, trini@konsulko.com
Cc: Johannes Krottmayer <krjdev@gmail.com>
Subject: [PATCH 0/2] CONFIG_EARLY_TIMER: Fix EAGAIN issue and use DM too
Date: Thu, 10 Mar 2022 19:45:47 +0100	[thread overview]
Message-ID: <20220310184549.1883-1-krjdev@gmail.com> (raw)

Hi,

I'm currently working on support for a STMicroelectronics board. I have
written a DM driver which implements the timer_early_* functions. But
noticed an issue when the configuration switch is set.

common/board_f.c
Here this leads in an EAGAIN issue, becaues the DM sub-system isn't
running at this point.

lib/time.c
I modified the routines here, because it's also could fail. An addintionl
feature is, that if CONFIG_EARLY_TIMER first it probes if, the DM timer
is present, if not it uses the timer_early_* functions.

Have compiled it in both configurations, and it works as accepted.

Kind regards,

Johannes


Signed-off-by: Johannes Krottmayer <krjdev@gmail.com>
Cc: Tom Rini <trini@konsulko.com>

---

Johannes Krottmayer (2):
  common: board_f.c: Fix EAGAIN issue when CONFIG_TIMER_EARLY is
    selected
  lib: time.c: Try also DM timer, when CONFIG_TIMER_EARLY is selected

 common/board_f.c |  6 ------
 lib/time.c       | 46 ++++++++++++++++++++++++++++++++--------------
 2 files changed, 32 insertions(+), 20 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-03-10 18:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 18:45 Johannes Krottmayer [this message]
2022-03-10 18:45 ` [PATCH 1/2] common: board_f.c: Fix EAGAIN issue when CONFIG_TIMER_EARLY is selected Johannes Krottmayer
2022-03-11 16:35   ` Johannes (krjdev) Krottmayer
2022-03-10 18:45 ` [PATCH 2/2] lib: time.c: Try also DM timer, " Johannes Krottmayer
2022-03-11 16:34   ` Johannes (krjdev) Krottmayer
2022-03-11 16:35 ` [PATCH 0/2] CONFIG_EARLY_TIMER: Fix EAGAIN issue and use DM too Johannes (krjdev) Krottmayer

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=20220310184549.1883-1-krjdev@gmail.com \
    --to=krjdev@gmail.com \
    --cc=krjdev@gnail.com \
    --cc=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox