From: Jaehoon Chung <jh80.chung@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] MMC: Do not write to mmc_uclass_priv if it was not allocated
Date: Mon, 04 Jul 2016 11:28:12 +0900 [thread overview]
Message-ID: <5779C9BC.7070607@samsung.com> (raw)
In-Reply-To: <CAPnjgZ36aZnBqgrXzCG10dTRjmRmkLj2EKBTfPqbBXv+Qoc+Kw@mail.gmail.com>
On 07/02/2016 03:17 AM, Simon Glass wrote:
> Hi,
>
> On 1 July 2016 at 04:37, Jaehoon Chung <jh80.chung@samsung.com> wrote:
>> On 07/01/2016 04:28 AM, Simon Glass wrote:
>>> Hi Meteusz,
>>>
>>> On 30 June 2016 at 12:18, Mateusz Kulikowski
>>> <mateusz.kulikowski@gmail.com> wrote:
>>>> On 29.06.2016 05:27, Simon Glass wrote:
>>>>> Hi Matt,
>>>>>
>>>>> On 25 June 2016 at 14:57, Matt Corallo <linux@bluematt.me> wrote:
>>>>>> Signed-off-by: Matt Corallo <git@bluematt.me>
>>>>>> ---
>>>>>> drivers/mmc/mmc.c | 3 ++-
>>>>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>>>>
>>>>>> diff --git a/drivers/mmc/mmc.c b/drivers/mmc/mmc.c
>>>>>> index aabfc71..eba20f0 100644
>>>>>> --- a/drivers/mmc/mmc.c
>>>>>> +++ b/drivers/mmc/mmc.c
>>>>>> @@ -1734,7 +1734,8 @@ int mmc_init(struct mmc *mmc)
>>>>>> #ifdef CONFIG_DM_MMC
>>>>>> struct mmc_uclass_priv *upriv = dev_get_uclass_priv(mmc->dev);
>>>>>>
>>>>>> - upriv->mmc = mmc;
>>>>>> + if (upriv)
>>>>>> + upriv->mmc = mmc;
>>>>>> #endif
>>>>>> if (mmc->has_init)
>>>>>> return 0;
>>>>>> --
>>>>>> 2.1.4
>>>>>
>>>>> Can you please add a commit message explaining why this is needed and
>>>>> what it fixes? How can mmc_init() be called before the MMC device is
>>>>> there? Is this related to this patch?
>>>>>
>>>>> http://patchwork.ozlabs.org/patch/640735/
>>>>
>>>> It's related in a way that it fixed crash of dragonboard before I submitted my patch :)
>>>>
>>>> Not sure if it meant to fix dragonboard or some other board.
>>>>
>>>> Although - imho - it's nice to make check like that.. or at least some kind of assert.
>>
>> I have just one question..Maybe it's not related with this patch..
>> But i saw other driver did that upriv->mmc is assigned to mmc in each drivers.
>>
>> What's difference with "upriv->mmc = mmc" in mmc.c?
>>
>> ./drivers/mmc/fsl_esdhc.c:972: upriv->mmc = priv->mmc;
>> ./drivers/mmc/mmc.c:1606: upriv->mmc = mmc;
>> ./drivers/mmc/mmc-uclass.c:91: return upriv->mmc;
>> ./drivers/mmc/msm_sdhci.c:147: upriv->mmc = host->mmc;
>> ./drivers/mmc/omap_hsmmc.c:830: upriv->mmc = mmc;
>> ./drivers/mmc/rockchip_dw_mmc.c:114: upriv->mmc = host->mmc;
>> ./drivers/mmc/socfpga_dw_mmc.c:110: upriv->mmc = host->mmc;
>> ./drivers/mmc/uniphier-sd.c:727: upriv->mmc = priv->mmc;
>> ./drivers/mmc/zynq_sdhci.c:52: upriv->mmc = host->mmc;
>>
>> Is it duplicated?
>> (I didn't see in more detail.)
>>
>> Best Regards,
>> Jaehoon Chung
>
> I am actually not happy with how this is at present. It should be
> handled by a function call. If you'd like to look at this please do,
> otherwise I will take a pass at it. It should be clear at this point
> what we need.
I will send the patch for cleaning.
Best Regards,
Jaehoon Chung
>
>>
>>>
>>> An assert() would be fine with me.
>>>
>>> Regards,
>>> Simon
>>> _______________________________________________
>>> U-Boot mailing list
>>> U-Boot at lists.denx.de
>>> http://lists.denx.de/mailman/listinfo/u-boot
>>>
>>>
>>>
>>
>
>
> Regards,
> Simon
>
>
>
prev parent reply other threads:[~2016-07-04 2:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-25 21:57 [U-Boot] [PATCH] MMC: Do not write to mmc_uclass_priv if it was not allocated Matt Corallo
2016-06-29 3:27 ` Simon Glass
2016-06-30 19:18 ` Mateusz Kulikowski
2016-06-30 19:28 ` Simon Glass
2016-06-30 22:35 ` Matt Corallo
2016-07-01 11:37 ` Jaehoon Chung
2016-07-01 18:17 ` Simon Glass
2016-07-04 2:28 ` Jaehoon Chung [this message]
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=5779C9BC.7070607@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