linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Merlijn Wajer <merlijn@wizzup.org>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
	"Arthur D." <spinal.by@gmail.com>
Subject: Re: N900: Remove mmc1 "safety feature"? (was: Re: mmc0 on Nokia N900 on Linux 5.4.18)
Date: Sat, 8 Feb 2020 23:06:21 +0100	[thread overview]
Message-ID: <20200208220621.GA18161@amd> (raw)
In-Reply-To: <1eac0db3-17ce-8ebd-4997-8b1c282126e4@wizzup.org>

[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]

Hi!

> >>> When booting Linux 5.4.18 with omap2plus_defconfig, I no longer get a
> >>> /dev/mmcblk0 device - the one corresponding to my microSD card, where
> >>> u-boot also loads the kernel from.
> >>>
> >>> This also likely seems to be a regression, but I haven't tried to hunt
> >>> it down yet.
> >>>
> >>> Kernel log attached, below.
> >>
> >> Do you have back cover attached? That's common trap...
> > 
> > Right.
> > 
> > No, I did not, since I have the serial pins connected to my PC, and the
> > whole device is mounted on a piece of hardware for that. I thought that
> > we fixed the problem where we require the cover to be on...
> 
> Indeed, this was the problem.
> 
> Is there really a reason to have this in the DTS? I have a hard time
> imagining a use case for not showing SD card to users or developers
> simply because the casing is open. If anything, this sounds like it
> should be a userspace thing.

It is very bad for debugging, agreed.

It makes sense for regular usage: when user removes back cover, system
unmounts the u-SD card, so that it is ready for user to remove
it. Note that we do _not_ have "remove the card safely" button in the
UI; back cover serves that purpose.

That said... for Leste just keep the patch. And maybe apply that one
to shutdown system when battery is low :-).

Best regards,
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2020-02-08 22:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07 17:41 mmc0 on Nokia N900 on Linux 5.4.18 Merlijn Wajer
2020-02-08 19:04 ` Pavel Machek
2020-02-08 19:18   ` Merlijn Wajer
2020-02-08 21:44     ` N900: Remove mmc1 "safety feature"? (was: Re: mmc0 on Nokia N900 on Linux 5.4.18) Merlijn Wajer
2020-02-08 22:06       ` Pavel Machek [this message]
2020-02-08 22:19         ` Merlijn Wajer
2020-02-09  3:48           ` Arthur D.
2020-02-09  8:11             ` Merlijn Wajer
2020-02-10 19:45             ` Aaro Koskinen
2020-02-10 19:27           ` Aaro Koskinen
2020-02-12 13:02             ` Merlijn Wajer
2020-02-14  1:39               ` Sebastian Reichel
2020-02-14  5:51                 ` N900: Remove mmc1 "safety feature"? Ivaylo Dimitrov
2020-02-14 14:19                   ` Tony Lindgren
2020-02-14 10:31                 ` N900: Remove mmc1 "safety feature"? (was: Re: mmc0 on Nokia N900 on Linux 5.4.18) Merlijn Wajer

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=20200208220621.GA18161@amd \
    --to=pavel@ucw.cz \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=merlijn@wizzup.org \
    --cc=spinal.by@gmail.com \
    --cc=tony@atomide.com \
    /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;
as well as URLs for NNTP newsgroup(s).