public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Johannes (krjdev) Krottmayer" <krjdev@gmail.com>
To: krjdev@gnail.com, u-boot@lists.denx.de, trini@konsulko.com
Subject: Re: [PATCH 1/2] common: board_f.c: Fix EAGAIN issue when CONFIG_TIMER_EARLY is selected
Date: Fri, 11 Mar 2022 17:35:12 +0100	[thread overview]
Message-ID: <b4bee750-022e-7634-dd8b-9c1615e37e4d@gmail.com> (raw)
In-Reply-To: <20220310184549.1883-2-krjdev@gmail.com>

Hi,

Ignore these patches. Have send them to the wrong maintainers...
There are also somm issues.

Thanks!

On 10.03.22 19:45, Johannes Krottmayer wrote:
> Description:
> 
> When CONFIG_TIMER_EARLY is selected and the timer driver implements
> timer_early_get_count() and timer_early_get_rate() this leads to
> an EAGAIN error in initf_dm() one some configurations.
> 
> Signed-off-by: Johannes Krottmayer <krjdev@gmail.com>
> Cc: Tom Rini <trini@konsulko.com>
> ---
>  common/board_f.c | 6 ------
>  1 file changed, 6 deletions(-)
> 
> diff --git a/common/board_f.c b/common/board_f.c
> index a68760092a..fc883c1742 100644
> --- a/common/board_f.c
> +++ b/common/board_f.c
> @@ -785,12 +785,6 @@ static int initf_dm(void)
>  	bootstage_accum(BOOTSTAGE_ID_ACCUM_DM_F);
>  	if (ret)
>  		return ret;
> -
> -	if (IS_ENABLED(CONFIG_TIMER_EARLY)) {
> -		ret = dm_timer_init();
> -		if (ret)
> -			return ret;
> -	}
>  #endif
>  
>  	return 0;

  reply	other threads:[~2022-03-11 16:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 18:45 [PATCH 0/2] CONFIG_EARLY_TIMER: Fix EAGAIN issue and use DM too Johannes Krottmayer
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 [this message]
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=b4bee750-022e-7634-dd8b-9c1615e37e4d@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