From: ameliafu1990 <ameliafu1990@gmail.com>
To: linux-mm@kvack.org
Subject: Questions about PASR patch
Date: Wed, 26 Aug 2015 13:06:37 +0000 (UTC) [thread overview]
Message-ID: <loom.20150826T150345-632@post.gmane.org> (raw)
Recently I've been reading the PASR patch, and I am really interested in
that. Cause I am a total freshman to linux kernel, there are a few
questions about the framework. I would very appreciate it if anyone
could take a look at them and give me some suggestions.
Now I am trying to put several memory banks into no_refresh state on a
real device, Nexus 9. Nexus 9 is based on Nvidia Tegra K1, with LPDDR3
as the RAM. Its kernel version is tegra-flounder-3.10. From this kernel
version, tegra 12 seems to support PASR. But tegra K1(tegra 132) does
not have a supporting function like that.
static void tegra12_pasr_apply_mask(u16 *mem_reg, void *cookie)
{
u32 val = 0;
int device = (int)cookie;
val = TEGRA_EMC_MODE_REG_17 | *mem_reg;
val |= device << TEGRA_EMC_MRW_DEV_SHIFT;
emc_writel(val, EMC_MRW);
pr_debug("%s: cookie = %d mem_reg = 0x%04x val = 0x%08x\n",
__func__,
(int)cookie, *mem_reg, val);
}
1. Does tegra 12 really supports PASR?
2. Why doesn't tegra 132 have a PASR driver? Is it because of some
hardware differences? Is it possible if I rewrite a similar driver on
tegra 132, just like tegra 12?
Thanks very much!
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
reply other threads:[~2015-08-26 13:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=loom.20150826T150345-632@post.gmane.org \
--to=ameliafu1990@gmail.com \
--cc=linux-mm@kvack.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