public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/4] exynos: Fix passing of errors in exynos_mmc_init()
Date: Wed, 23 Sep 2015 18:54:28 +0900	[thread overview]
Message-ID: <560276D4.5070202@samsung.com> (raw)
In-Reply-To: <20150923113955.1aba87bd@amdc2363>

Hi.

On 09/23/2015 06:39 PM, Lukasz Majewski wrote:
> Hi Tobias,
> 
>> exynos_mmc_init() always returns zero, so for the caller
>> it looks like it never fails.
>>
>> Correct this by returning the error code of process_nodes().
>> For process_nodes() do something similar and return early
>> when do_sdhci_init() fails.
>>
>> Signed-off-by: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
>> ---
>>  drivers/mmc/s5p_sdhci.c | 10 ++++++----
>>  1 file changed, 6 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/mmc/s5p_sdhci.c b/drivers/mmc/s5p_sdhci.c
>> index e9c43a9..bc2102a 100644
>> --- a/drivers/mmc/s5p_sdhci.c
>> +++ b/drivers/mmc/s5p_sdhci.c
>> @@ -187,7 +187,11 @@ static int process_nodes(const void *blob, int
>> node_list[], int count) printf("%s: failed to decode dev
>> %d\n",	__func__, i); return -1;
>>  		}
>> -		do_sdhci_init(host);
>> +
>> +		if (do_sdhci_init(host)) {
>> +			printf("%s: failed to initialize dev %d\n",
>> __func__, i);
>> +			return -2;
> 
> IMHO, it would be better to write this code as follows:
> 
> ret = do_sdhci_init(host);
> if (ret) {
> 
> 	printf();
> 	return ret;
> }

I think it should be replaced to "continue;", not "return ret;"
If returned the fail, then next host can't initialize.(if there is next host..)
So maybe, it didn't use "return ret".

Best Regards,
Jaehoon Chung

> 	
> In the above code you read the exact return code from do_sdhci_init()
> and then you pass it to upper layer.
> 
> Returning only -2 is far less informational.
> 
>> +		}
>>  	}
>>  	return 0;
>>  }
>> @@ -201,8 +205,6 @@ int exynos_mmc_init(const void *blob)
>>  			COMPAT_SAMSUNG_EXYNOS_MMC, node_list,
>>  			SDHCI_MAX_HOSTS);
>>  
>> -	process_nodes(blob, node_list, count);
>> -
>> -	return 0;
>> +	return process_nodes(blob, node_list, count);
>>  }
>>  #endif
> 
> 
> 

  reply	other threads:[~2015-09-23  9:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-20 23:18 [U-Boot] [PATCH 0/4] Fix operation on Odroid devices Tobias Jakobi
2015-09-20 23:18 ` [U-Boot] [PATCH 1/4] exynos: Properly initialize host_caps in s5p_sdhci_core_init() Tobias Jakobi
2015-09-23  9:35   ` Lukasz Majewski
2015-09-20 23:18 ` [U-Boot] [PATCH 2/4] exynos: Fix passing of errors in exynos_mmc_init() Tobias Jakobi
2015-09-23  9:39   ` Lukasz Majewski
2015-09-23  9:54     ` Jaehoon Chung [this message]
2015-09-23 10:13       ` Minkyu Kang
2015-09-21  8:49 ` [U-Boot] [PATCH 0/4] Fix operation on Odroid devices Jaehoon Chung
2015-09-21  9:34   ` Tobias Jakobi
2015-09-21 10:04     ` Jaehoon Chung
2015-09-21 10:54       ` Tobias Jakobi
2015-09-21 11:00       ` Tobias Jakobi
2015-09-21 11:05         ` Jaehoon Chung
2015-09-24 15:04 ` Przemyslaw Marczak

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=560276D4.5070202@samsung.com \
    --to=jh80.chung@samsung.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