Linux MultiMedia Card development
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Pintu Kumar <pintu.ping@gmail.com>
Cc: Mikko Perttunen <cyndis@kapsi.fi>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mmc@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [tegra186]: emmc resume failing after booting from snapshot image
Date: Wed, 22 Nov 2017 16:15:58 +0000	[thread overview]
Message-ID: <b0729c10-601f-d609-b807-a87b4bed4e59@nvidia.com> (raw)
In-Reply-To: <CAOuPNLgW84yuXxm8HLQ7KS-1=0nPo9s7OumWt4ipkm7D2pdmog@mail.gmail.com>


On 22/11/17 12:26, Pintu Kumar wrote:
> Hello Jon,
> Yes I raised my query there almost 1 week back here.
> https://devtalk.nvidia.com/default/topic/1026527/jetson-tx2/-jetson-tx2-mmc-resume-errors-after-booting-from-suspend/
> 
> But no response.
> So, I thought to discuss it here.
> May be some pointers may help to find the root cause.
> One point is that, I am able to resume the board with the sd-card, but
> resume from emmc is returning -110 (may be CMD5 timeout).
> Whether there is any difference between sd-card resume and emmc resume ?
> Do we need to check the card initialization sequence for emmc ?
OK great. There should be a team looking at these so please bare with
them. I noticed that you did not state which release you are using for
TX2 and there are two available (r27 and r28.1 [0]), unless I missed it.
So it is worth stating the release you are using.

What command are you using to suspend to disk?

Cheers
Jon

[0] https://developer.nvidia.com/embedded/linux-tegra-archive
-- 
nvpublic

  reply	other threads:[~2017-11-22 16:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22  6:41 [tegra186]: emmc resume failing after booting from snapshot image Pintu Kumar
2017-11-22  9:11 ` Mikko Perttunen
2017-11-22 10:40   ` Jon Hunter
     [not found]     ` <b607c51f-559e-0315-6843-c0d9d07cb81e-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-11-22 12:26       ` Pintu Kumar
2017-11-22 16:15         ` Jon Hunter [this message]
2017-11-22 16:39           ` Pintu Kumar

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=b0729c10-601f-d609-b807-a87b4bed4e59@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=cyndis@kapsi.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=pintu.ping@gmail.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