summaryrefslogtreecommitdiffstats
path: root/crypto/tcrypt.h
diff options
context:
space:
mode:
authorNishanth Menon <nm@ti.com>2013-03-16 11:46:44 +0530
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-03-25 13:18:12 -0700
commitf91a595d0b813c3a2f3b848c165e865ca4c5b8cc (patch)
treec14fc79d76636ef6118e0252c2408907c634d9a9 /crypto/tcrypt.h
parent25aaacd2834233bbfa2b7ec697bfce42707e35b7 (diff)
downloadlinux-f91a595d0b813c3a2f3b848c165e865ca4c5b8cc.tar.gz
linux-f91a595d0b813c3a2f3b848c165e865ca4c5b8cc.tar.bz2
linux-f91a595d0b813c3a2f3b848c165e865ca4c5b8cc.zip
memory: emif: Handle devices which are not rated for >85C
As per JESD209-2E specification for LPDDR2, http://www.jedec.org/standards-documents/results/jesd209-2E Table 73, LPDDR2 memories come in two flavors - Standard and Extended. The Standard types can operate from -25C to +85C However, beyond that and upto +105C can only be supported by Extended types. Unfortunately, it seems there is no info in MR0(device info) or MR[1,2](device feature) for run time detection of this capability as far as seen on the spec. Hence, we provide a custom_config flag to be populated by platforms which have these "extended" type memories. For the "Standard" memories, we need to consider MR4 notifications of temperature triggers >85C as equivalent to thermal shutdown events (equivalent to Spec specified thermal shutdown events for "extended" parts). Reported-by: Richard Woodruff <r-woodruff2@ti.com> Signed-off-by: Nishanth Menon <nm@ti.com> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'crypto/tcrypt.h')
0 files changed, 0 insertions, 0 deletions