public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: board: cm-fx6: fix mmc for old revisions of utilite
Date: Thu, 16 Jun 2016 12:05:20 +0300	[thread overview]
Message-ID: <57626BD0.2000600@compulab.co.il> (raw)
In-Reply-To: <ee73ccdf3c9e4a46bfe99381a0b84b9d@rwthex-s1-b.rwth-ad.de>

Hi Christopher,

On 06/15/2016 06:38 PM, Christopher Spinrath wrote:
> Hi Nikita,
> 
> On 06/15/2016 05:15 PM, Nikita Kiryanov wrote:
>> Hi CHristopher,
>>
>> On Wed, Jun 08, 2016 at 09:02:36PM +0200, Christopher Spinrath wrote:
>>> Old revisions of Utilite (based on cmfx6) do not have a dedicated
>>> card detect pin. But the card is removable by the user and card
>>> detection can be realized with polling (e.g. supported by Linux).
>>>
>>> Add the broken-cd property to the mmc device tree instead of the
>>> non-removable property to make card detection possible if polling
>>> is supported.
>>
>> Acked-by: Nikita Kiryanov <nikita@compulab.co.il>
> 
> How is this patch (and, in general, patches for Utilite/cm-fx6) supposed
> to be merged?

Well, you've done this almost correctly. You just need to add
Stefano Babic <sbabic@denx.de>
(who is the maintainer of imx) to "cc" or "to" list.
Added now.

> Due to get_maintainers your are (the only) maintainer
> related to the cm-fx6 board.

That is a separate discussion (e.g. how boards of a specific vendor, but
different architectures/platforms should be listed in the MAINTAINERS files).

> Do you want me to resend the patch (without
> the Fixes: tag)?
> 
>> One nit-pick below:
>>
>>>
>>> Fixes: 41855186afd3 ("arm: mx6: cm-fx6: modify device tree for old revisions of utilite")
>>
>> This isn't technically a fix; you're enabling new functionality. The
>> original behavior wasn't buggy, it just lacked the card detect feature.
>>
> Well, the card is clearly removable. So IMHO adding the non-removable
> property is wrong and this patch corrects/fixes it. But I'm fine either way.

Just a little explanation...
Mechanically the card _is_ removable, but for revisions < 1.3, it will
result in errors on the bus as no removal event will be sent to the
subsystem. Moreover, if I'm not mistaken, you have the PRO model, right?
In PRO model, you have internal storage (e.g. SSD) which makes the SD card
an additional and sensibly removable device...
There are additional Utilite models which have the SD card as the only
storage device and those models have the rootfs on the SD card.
In such case, IMO, it is much more appropriate to state that it should be
non-removable.

-- 
Regards,
Igor.

  reply	other threads:[~2016-06-16  9:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 19:02 [U-Boot] [PATCH] ARM: board: cm-fx6: fix mmc for old revisions of utilite Christopher Spinrath
2016-06-15 15:15 ` Nikita Kiryanov
     [not found] ` <d14689fedcc6431eb290feab11572a81@rwthex-w2-b.rwth-ad.de>
2016-06-15 15:38   ` Christopher Spinrath
2016-06-16  9:05     ` Igor Grinberg [this message]
2016-06-16 10:40     ` Nikita Kiryanov
     [not found]     ` <8541bdd129d345eda74f0bdb0444d2fc@rwthex-w2-a.rwth-ad.de>
2016-06-16 11:21       ` Christopher Spinrath
2016-06-16 12:46         ` Igor Grinberg
     [not found]     ` <f56e4e04d9ab4fb9bc974570a103a0d0@rwthex-w2-b.rwth-ad.de>
2016-06-16 11:22       ` Christopher Spinrath

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=57626BD0.2000600@compulab.co.il \
    --to=grinberg@compulab.co.il \
    --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