From: atull@opensource.altera.com (atull)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/2] ARM: socfpga: support suspend to ram
Date: Thu, 28 May 2015 15:21:43 -0500 [thread overview]
Message-ID: <alpine.DEB.2.02.1505281520410.31038@linuxheads99> (raw)
In-Reply-To: <20150526215617.GA3137@amd>
On Tue, 26 May 2015, Pavel Machek wrote:
> Hi!
>
> > Thanks for the feedback.
> >
> > Yes I agree.
> >
> > One possibility is that I could add a suspend function to EDAC that
> > always fails with a helpful message like "Suspend with EDAC not
> > supported." If someone wants to suspend, they'll have to take the
> > EDAC out of the device tree so its probe will bomb out. I'm not
> > sure how normal it is to have suspend functions in the kernel
> > that always fail, though.
>
> "Interesting" solution, but better than config exclusion, I'd say.
>
> > > > + /*
> > > > + * This code assumes that the bootloader has already
> > > > + * properly configured the sdram controller:
> > >
> > > Which bootloaders can do that?
> >
> > Whatever bootloader is configuring the sdram controller for the
> > board.
>
> Ok, so direct question: will mainline u-boot 2015.04 configure the
> controller correctly?
Should be in 2015.07
Alan Tull
next prev parent reply other threads:[~2015-05-28 20:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 18:02 [PATCH v4 0/2] socfpga: support suspend to ram Alan Tull
2015-05-22 18:02 ` [PATCH v4 1/2] ARM: " Alan Tull
2015-05-25 12:41 ` Pavel Machek
2015-05-26 21:40 ` atull
2015-05-26 21:56 ` Pavel Machek
2015-05-28 20:21 ` atull [this message]
2015-05-26 13:48 ` Dinh Nguyen
2015-05-27 20:25 ` atull
2015-05-28 15:07 ` Dinh Nguyen
2015-05-28 20:23 ` atull
2015-05-22 18:02 ` [PATCH v4 2/2] ARM: socfpga: dts: add sdram controller dt binding doc Alan Tull
2015-05-25 12:39 ` Pavel Machek
2015-05-26 21:37 ` atull
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=alpine.DEB.2.02.1505281520410.31038@linuxheads99 \
--to=atull@opensource.altera.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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