2017-01-11 01:53:54 +00:00
|
|
|
/*-
|
|
|
|
|
* Copyright (c) 2017 Oleksandr Tymoshenko <gonzo@FreeBSD.org>
|
|
|
|
|
* All rights reserved.
|
|
|
|
|
*
|
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
|
* are met:
|
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
|
|
|
|
*
|
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
|
|
|
|
|
* IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
|
|
|
|
|
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
|
|
|
|
|
* IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
|
|
|
|
|
* INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
|
|
|
|
|
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
|
|
|
|
* DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
|
|
|
|
* THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
|
|
|
|
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
|
|
|
|
|
* THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#include <sys/cdefs.h>
|
|
|
|
|
__FBSDID("$FreeBSD$");
|
|
|
|
|
|
|
|
|
|
#include <sys/param.h>
|
|
|
|
|
#include <sys/systm.h>
|
|
|
|
|
#include <sys/bus.h>
|
|
|
|
|
#include <sys/kernel.h>
|
|
|
|
|
#include <sys/lock.h>
|
|
|
|
|
#include <sys/module.h>
|
|
|
|
|
#include <sys/mutex.h>
|
|
|
|
|
#include <sys/resource.h>
|
|
|
|
|
#include <sys/rman.h>
|
|
|
|
|
#include <sys/sysctl.h>
|
|
|
|
|
#include <sys/taskqueue.h>
|
|
|
|
|
|
|
|
|
|
#include <machine/bus.h>
|
|
|
|
|
#include <machine/resource.h>
|
|
|
|
|
|
|
|
|
|
#include <contrib/dev/acpica/include/acpi.h>
|
|
|
|
|
#include <dev/acpica/acpivar.h>
|
|
|
|
|
|
|
|
|
|
#include <dev/mmc/bridge.h>
|
|
|
|
|
|
2017-03-06 23:47:59 +00:00
|
|
|
#include <dev/sdhci/sdhci.h>
|
|
|
|
|
|
2017-01-11 01:53:54 +00:00
|
|
|
#include "mmcbr_if.h"
|
|
|
|
|
#include "sdhci_if.h"
|
|
|
|
|
|
|
|
|
|
static const struct sdhci_acpi_device {
|
|
|
|
|
const char* hid;
|
|
|
|
|
int uid;
|
|
|
|
|
const char *desc;
|
|
|
|
|
u_int quirks;
|
|
|
|
|
} sdhci_acpi_devices[] = {
|
- Unlike as in the PCI case, when attached to ACPI, Intel Bay Trail
and Braswell eMMC and SDXC controllers share the same IDs. Like in
the PCI case, Braswell eMMC needs the SDHCI_QUIRK_DATA_TIMEOUT_1MHZ
quirk (see r311794 for the corresponding change to the sdhci(4) PCI
PCI front-end), though. However, due to the shared ACPI IDs, this
is trickier to do.
- Intel Apollo Lake eMMC and SDXC controllers are affected by the
APL18 ("Using 32-bit Addressing Mode With SD/eMMC Controller May
Lead to Unpredictable System Behavior") silicon bug [1]. When this
erratum hits, typically both SDHCI and XHCI controllers wedge.
According to Intel, using ADMA2 with 64-bit addressing and 96-bit
descriptors serves as a workaround. Until such times when sdhci(4)
has ADMA2 support, flag DMA as broken for affected interfaces.
This turns out to work around the problem, too, at the cost of
performance.
- In the sdhci(4) ACPI front-end, probe the Intel Apollo Lake eMMC
and SDXC controllers, too.
1: http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/pentium-celeron-n-series-j-series-datasheet-spec-update.pdf
2017-05-14 21:33:01 +00:00
|
|
|
{ "80860F14", 1, "Intel Bay Trail/Braswell eMMC 4.5/4.5.1 Controller",
|
2017-01-11 01:53:54 +00:00
|
|
|
SDHCI_QUIRK_ALL_SLOTS_NON_REMOVABLE |
|
- Add support for eMMC "partitions". Besides the user data area, i. e.
the default partition, eMMC v4.41 and later devices can additionally
provide up to:
1 enhanced user data area partition
2 boot partitions
1 RPMB (Replay Protected Memory Block) partition
4 general purpose partitions (optionally with a enhanced or extended
attribute)
Of these "partitions", only the enhanced user data area one actually
slices the user data area partition and, thus, gets handled with the
help of geom_flashmap(4). The other types of partitions have address
space independent from the default partition and need to be switched
to via CMD6 (SWITCH), i. e. constitute a set of additional "disks".
The second kind of these "partitions" doesn't fit that well into the
design of mmc(4) and mmcsd(4). I've decided to let mmcsd(4) hook all
of these "partitions" up as disk(9)'s (except for the RPMB partition
as it didn't seem to make much sense to be able to put a file-system
there and may require authentication; therefore, RPMB partitions are
solely accessible via the newly added IOCTL interface currently; see
also below). This approach for one resulted in cleaner code. Second,
it retains the notion of mmcsd(4) children corresponding to a single
physical device each. With the addition of some layering violations,
it also would have been possible for mmc(4) to add separate mmcsd(4)
instances with one disk each for all of these "partitions", however.
Still, both mmc(4) and mmcsd(4) share some common code now e. g. for
issuing CMD6, which has been factored out into mmc_subr.c.
Besides simply subdividing eMMC devices, some Intel NUCs having UEFI
code in the boot partitions etc., another use case for the partition
support is the activation of pseudo-SLC mode, which manufacturers of
eMMC chips typically associate with the enhanced user data area and/
or the enhanced attribute of general purpose partitions.
CAVEAT EMPTOR: Partitioning eMMC devices is a one-time operation.
- Now that properly issuing CMD6 is crucial (so data isn't written to
the wrong partition for example), make a step into the direction of
correctly handling the timeout for these commands in the MMC layer.
Also, do a SEND_STATUS when CMD6 is invoked with an R1B response as
recommended by relevant specifications. However, quite some work is
left to be done in this regard; all other R1B-type commands done by
the MMC layer also should be followed by a SEND_STATUS (CMD13), the
erase timeout calculations/handling as documented in specifications
are entirely ignored so far, the MMC layer doesn't provide timeouts
applicable up to the bridge drivers and at least sdhci(4) currently
is hardcoding 1 s as timeout for all command types unconditionally.
Let alone already available return codes often not being checked in
the MMC layer ...
- Add an IOCTL interface to mmcsd(4); this is sufficiently compatible
with Linux so that the GNU mmc-utils can be ported to and used with
FreeBSD (note that due to the remaining deficiencies outlined above
SANITIZE operations issued by/with `mmc` currently most likely will
fail). These latter will be added to ports as sysutils/mmc-utils in
a bit. Among others, the `mmc` tool of the GNU mmc-utils allows for
partitioning eMMC devices (tested working).
- For devices following the eMMC specification v4.41 or later, year 0
is 2013 rather than 1997; so correct this for assembling the device
ID string properly.
- Let mmcsd.ko depend on mmc.ko. Additionally, bump MMC_VERSION as at
least for some of the above a matching pair is required.
- In the ACPI front-end of sdhci(4) describe the Intel eMMC and SDXC
controllers as such in order to match the PCI one.
Additionally, in the entry for the 80860F14 SDXC controller remove
the eMMC-only SDHCI_QUIRK_INTEL_POWER_UP_RESET.
OKed by: imp
Submitted by: ian (mmc_switch_status() implementation)
2017-03-16 22:23:04 +00:00
|
|
|
SDHCI_QUIRK_INTEL_POWER_UP_RESET |
|
o Add support for eMMC DDR bus speed mode at 52 MHz to sdhci(4) and
mmc(4). For the most part, this consists of support for:
- Switching the signal voltage (VCCQ) to 1.8 V or (if supported
by the host controller) to 1.2 V,
- setting the UHS mode as appropriate in the SDHCI_HOST_CONTROL2
register,
- setting the power class in the eMMC device according to the
core supply voltage (VCC),
- using different bits for enabling a bus width of 4 and 8 bits
in the the eMMC device at DDR or higher timings respectively,
- arbitrating timings faster than high speed if there actually
are additional devices on the same MMC bus.
Given that support for DDR52 is not denoted by SDHCI capability
registers, availability of that timing is indicated by a new
quirk SDHCI_QUIRK_MMC_DDR52 and only enabled for Intel SDHCI
controllers so far. Generally, what it takes for a sdhci(4)
front-end to enable support for DDR52 is to hook up the bridge
method mmcbr_switch_vccq (which especially for 1.2 V signaling
support is chip/board specific) and the sdhci_set_uhs_timing
sdhci(4) method.
As a side-effect, this change also fixes communication with
some eMMC devices at SDR high speed mode with 52 MHz due to
the signaling voltage and UHS bits in the SDHCI controller no
longer being left in an inappropriate state.
Compared to 52 MHz at SDR high speed which typically yields
~45 MB/s with the eMMC chips tested, throughput goes up to
~80 MB/s at DDR52.
Additionally, this change already adds infrastructure and quite
some code for modes up to HS400ES and SDR104 respectively (I did
not want to add to much stuff at a time, though). Essentially,
what is still missing in order to be able to activate support
for these latter is is support for and handling of (re-)tuning.
o In sdhci(4), add two tunables hw.sdhci.quirk_clear as well as
hw.sdhci.quirk_set, which (when hooked up in the front-end)
allow to set/clear sdhci(4) quirks for debugging and testing
purposes. However, especially for SDHCI controllers on the
PCI bus which have no specific support code so far and, thus,
are picked up as generic SDHCI controllers, hw.sdhci.quirk_set
allows for setting the necessary quirks (if required).
o In mmc(4), check and handle the return values of some more
function calls instead of assuming that everything went right.
In case failures actually are not problematic, indicate that
by casting the return value to void.
Reviewed by: jmcneill
2017-03-19 23:27:17 +00:00
|
|
|
SDHCI_QUIRK_WAIT_WHILE_BUSY |
|
|
|
|
|
SDHCI_QUIRK_MMC_DDR52 |
|
|
|
|
|
SDHCI_QUIRK_CAPS_BIT63_FOR_MMC_HS400 |
|
|
|
|
|
SDHCI_QUIRK_PRESET_VALUE_BROKEN },
|
- Unlike as in the PCI case, when attached to ACPI, Intel Bay Trail
and Braswell eMMC and SDXC controllers share the same IDs. Like in
the PCI case, Braswell eMMC needs the SDHCI_QUIRK_DATA_TIMEOUT_1MHZ
quirk (see r311794 for the corresponding change to the sdhci(4) PCI
PCI front-end), though. However, due to the shared ACPI IDs, this
is trickier to do.
- Intel Apollo Lake eMMC and SDXC controllers are affected by the
APL18 ("Using 32-bit Addressing Mode With SD/eMMC Controller May
Lead to Unpredictable System Behavior") silicon bug [1]. When this
erratum hits, typically both SDHCI and XHCI controllers wedge.
According to Intel, using ADMA2 with 64-bit addressing and 96-bit
descriptors serves as a workaround. Until such times when sdhci(4)
has ADMA2 support, flag DMA as broken for affected interfaces.
This turns out to work around the problem, too, at the cost of
performance.
- In the sdhci(4) ACPI front-end, probe the Intel Apollo Lake eMMC
and SDXC controllers, too.
1: http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/pentium-celeron-n-series-j-series-datasheet-spec-update.pdf
2017-05-14 21:33:01 +00:00
|
|
|
{ "80860F14", 3, "Intel Bay Trail/Braswell SDXC Controller",
|
o Add support for eMMC DDR bus speed mode at 52 MHz to sdhci(4) and
mmc(4). For the most part, this consists of support for:
- Switching the signal voltage (VCCQ) to 1.8 V or (if supported
by the host controller) to 1.2 V,
- setting the UHS mode as appropriate in the SDHCI_HOST_CONTROL2
register,
- setting the power class in the eMMC device according to the
core supply voltage (VCC),
- using different bits for enabling a bus width of 4 and 8 bits
in the the eMMC device at DDR or higher timings respectively,
- arbitrating timings faster than high speed if there actually
are additional devices on the same MMC bus.
Given that support for DDR52 is not denoted by SDHCI capability
registers, availability of that timing is indicated by a new
quirk SDHCI_QUIRK_MMC_DDR52 and only enabled for Intel SDHCI
controllers so far. Generally, what it takes for a sdhci(4)
front-end to enable support for DDR52 is to hook up the bridge
method mmcbr_switch_vccq (which especially for 1.2 V signaling
support is chip/board specific) and the sdhci_set_uhs_timing
sdhci(4) method.
As a side-effect, this change also fixes communication with
some eMMC devices at SDR high speed mode with 52 MHz due to
the signaling voltage and UHS bits in the SDHCI controller no
longer being left in an inappropriate state.
Compared to 52 MHz at SDR high speed which typically yields
~45 MB/s with the eMMC chips tested, throughput goes up to
~80 MB/s at DDR52.
Additionally, this change already adds infrastructure and quite
some code for modes up to HS400ES and SDR104 respectively (I did
not want to add to much stuff at a time, though). Essentially,
what is still missing in order to be able to activate support
for these latter is is support for and handling of (re-)tuning.
o In sdhci(4), add two tunables hw.sdhci.quirk_clear as well as
hw.sdhci.quirk_set, which (when hooked up in the front-end)
allow to set/clear sdhci(4) quirks for debugging and testing
purposes. However, especially for SDHCI controllers on the
PCI bus which have no specific support code so far and, thus,
are picked up as generic SDHCI controllers, hw.sdhci.quirk_set
allows for setting the necessary quirks (if required).
o In mmc(4), check and handle the return values of some more
function calls instead of assuming that everything went right.
In case failures actually are not problematic, indicate that
by casting the return value to void.
Reviewed by: jmcneill
2017-03-19 23:27:17 +00:00
|
|
|
SDHCI_QUIRK_WAIT_WHILE_BUSY |
|
|
|
|
|
SDHCI_QUIRK_PRESET_VALUE_BROKEN },
|
- Unlike as in the PCI case, when attached to ACPI, Intel Bay Trail
and Braswell eMMC and SDXC controllers share the same IDs. Like in
the PCI case, Braswell eMMC needs the SDHCI_QUIRK_DATA_TIMEOUT_1MHZ
quirk (see r311794 for the corresponding change to the sdhci(4) PCI
PCI front-end), though. However, due to the shared ACPI IDs, this
is trickier to do.
- Intel Apollo Lake eMMC and SDXC controllers are affected by the
APL18 ("Using 32-bit Addressing Mode With SD/eMMC Controller May
Lead to Unpredictable System Behavior") silicon bug [1]. When this
erratum hits, typically both SDHCI and XHCI controllers wedge.
According to Intel, using ADMA2 with 64-bit addressing and 96-bit
descriptors serves as a workaround. Until such times when sdhci(4)
has ADMA2 support, flag DMA as broken for affected interfaces.
This turns out to work around the problem, too, at the cost of
performance.
- In the sdhci(4) ACPI front-end, probe the Intel Apollo Lake eMMC
and SDXC controllers, too.
1: http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/pentium-celeron-n-series-j-series-datasheet-spec-update.pdf
2017-05-14 21:33:01 +00:00
|
|
|
{ "80860F16", 0, "Intel Bay Trail/Braswell SDXC Controller",
|
o Add support for eMMC DDR bus speed mode at 52 MHz to sdhci(4) and
mmc(4). For the most part, this consists of support for:
- Switching the signal voltage (VCCQ) to 1.8 V or (if supported
by the host controller) to 1.2 V,
- setting the UHS mode as appropriate in the SDHCI_HOST_CONTROL2
register,
- setting the power class in the eMMC device according to the
core supply voltage (VCC),
- using different bits for enabling a bus width of 4 and 8 bits
in the the eMMC device at DDR or higher timings respectively,
- arbitrating timings faster than high speed if there actually
are additional devices on the same MMC bus.
Given that support for DDR52 is not denoted by SDHCI capability
registers, availability of that timing is indicated by a new
quirk SDHCI_QUIRK_MMC_DDR52 and only enabled for Intel SDHCI
controllers so far. Generally, what it takes for a sdhci(4)
front-end to enable support for DDR52 is to hook up the bridge
method mmcbr_switch_vccq (which especially for 1.2 V signaling
support is chip/board specific) and the sdhci_set_uhs_timing
sdhci(4) method.
As a side-effect, this change also fixes communication with
some eMMC devices at SDR high speed mode with 52 MHz due to
the signaling voltage and UHS bits in the SDHCI controller no
longer being left in an inappropriate state.
Compared to 52 MHz at SDR high speed which typically yields
~45 MB/s with the eMMC chips tested, throughput goes up to
~80 MB/s at DDR52.
Additionally, this change already adds infrastructure and quite
some code for modes up to HS400ES and SDR104 respectively (I did
not want to add to much stuff at a time, though). Essentially,
what is still missing in order to be able to activate support
for these latter is is support for and handling of (re-)tuning.
o In sdhci(4), add two tunables hw.sdhci.quirk_clear as well as
hw.sdhci.quirk_set, which (when hooked up in the front-end)
allow to set/clear sdhci(4) quirks for debugging and testing
purposes. However, especially for SDHCI controllers on the
PCI bus which have no specific support code so far and, thus,
are picked up as generic SDHCI controllers, hw.sdhci.quirk_set
allows for setting the necessary quirks (if required).
o In mmc(4), check and handle the return values of some more
function calls instead of assuming that everything went right.
In case failures actually are not problematic, indicate that
by casting the return value to void.
Reviewed by: jmcneill
2017-03-19 23:27:17 +00:00
|
|
|
SDHCI_QUIRK_WAIT_WHILE_BUSY |
|
|
|
|
|
SDHCI_QUIRK_PRESET_VALUE_BROKEN },
|
- Unlike as in the PCI case, when attached to ACPI, Intel Bay Trail
and Braswell eMMC and SDXC controllers share the same IDs. Like in
the PCI case, Braswell eMMC needs the SDHCI_QUIRK_DATA_TIMEOUT_1MHZ
quirk (see r311794 for the corresponding change to the sdhci(4) PCI
PCI front-end), though. However, due to the shared ACPI IDs, this
is trickier to do.
- Intel Apollo Lake eMMC and SDXC controllers are affected by the
APL18 ("Using 32-bit Addressing Mode With SD/eMMC Controller May
Lead to Unpredictable System Behavior") silicon bug [1]. When this
erratum hits, typically both SDHCI and XHCI controllers wedge.
According to Intel, using ADMA2 with 64-bit addressing and 96-bit
descriptors serves as a workaround. Until such times when sdhci(4)
has ADMA2 support, flag DMA as broken for affected interfaces.
This turns out to work around the problem, too, at the cost of
performance.
- In the sdhci(4) ACPI front-end, probe the Intel Apollo Lake eMMC
and SDXC controllers, too.
1: http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/pentium-celeron-n-series-j-series-datasheet-spec-update.pdf
2017-05-14 21:33:01 +00:00
|
|
|
{ "80865ACA", 0, "Intel Apollo Lake SDXC Controller",
|
|
|
|
|
SDHCI_QUIRK_BROKEN_DMA | /* APL18 erratum */
|
|
|
|
|
SDHCI_QUIRK_WAIT_WHILE_BUSY |
|
|
|
|
|
SDHCI_QUIRK_PRESET_VALUE_BROKEN },
|
|
|
|
|
{ "80865ACC", 0, "Intel Apollo Lake eMMC 5.0 Controller",
|
|
|
|
|
SDHCI_QUIRK_BROKEN_DMA | /* APL18 erratum */
|
|
|
|
|
SDHCI_QUIRK_ALL_SLOTS_NON_REMOVABLE |
|
|
|
|
|
SDHCI_QUIRK_INTEL_POWER_UP_RESET |
|
|
|
|
|
SDHCI_QUIRK_WAIT_WHILE_BUSY |
|
|
|
|
|
SDHCI_QUIRK_MMC_DDR52 |
|
|
|
|
|
SDHCI_QUIRK_CAPS_BIT63_FOR_MMC_HS400 |
|
|
|
|
|
SDHCI_QUIRK_PRESET_VALUE_BROKEN },
|
2017-01-11 01:53:54 +00:00
|
|
|
{ NULL, 0, NULL, 0}
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static char *sdhci_ids[] = {
|
|
|
|
|
"80860F14",
|
|
|
|
|
"80860F16",
|
- Unlike as in the PCI case, when attached to ACPI, Intel Bay Trail
and Braswell eMMC and SDXC controllers share the same IDs. Like in
the PCI case, Braswell eMMC needs the SDHCI_QUIRK_DATA_TIMEOUT_1MHZ
quirk (see r311794 for the corresponding change to the sdhci(4) PCI
PCI front-end), though. However, due to the shared ACPI IDs, this
is trickier to do.
- Intel Apollo Lake eMMC and SDXC controllers are affected by the
APL18 ("Using 32-bit Addressing Mode With SD/eMMC Controller May
Lead to Unpredictable System Behavior") silicon bug [1]. When this
erratum hits, typically both SDHCI and XHCI controllers wedge.
According to Intel, using ADMA2 with 64-bit addressing and 96-bit
descriptors serves as a workaround. Until such times when sdhci(4)
has ADMA2 support, flag DMA as broken for affected interfaces.
This turns out to work around the problem, too, at the cost of
performance.
- In the sdhci(4) ACPI front-end, probe the Intel Apollo Lake eMMC
and SDXC controllers, too.
1: http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/pentium-celeron-n-series-j-series-datasheet-spec-update.pdf
2017-05-14 21:33:01 +00:00
|
|
|
"80865ACA",
|
|
|
|
|
"80865ACC",
|
2017-01-11 01:53:54 +00:00
|
|
|
NULL
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct sdhci_acpi_softc {
|
|
|
|
|
u_int quirks; /* Chip specific quirks */
|
|
|
|
|
struct resource *irq_res; /* IRQ resource */
|
2017-01-29 00:05:49 +00:00
|
|
|
void *intrhand; /* Interrupt handle */
|
2017-01-11 01:53:54 +00:00
|
|
|
|
|
|
|
|
struct sdhci_slot slot;
|
|
|
|
|
struct resource *mem_res; /* Memory resource */
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static void sdhci_acpi_intr(void *arg);
|
|
|
|
|
static int sdhci_acpi_detach(device_t dev);
|
|
|
|
|
|
|
|
|
|
static uint8_t
|
2017-03-17 22:57:37 +00:00
|
|
|
sdhci_acpi_read_1(device_t dev, struct sdhci_slot *slot __unused,
|
|
|
|
|
bus_size_t off)
|
2017-01-11 01:53:54 +00:00
|
|
|
{
|
|
|
|
|
struct sdhci_acpi_softc *sc = device_get_softc(dev);
|
|
|
|
|
|
|
|
|
|
bus_barrier(sc->mem_res, 0, 0xFF,
|
|
|
|
|
BUS_SPACE_BARRIER_READ | BUS_SPACE_BARRIER_WRITE);
|
|
|
|
|
return bus_read_1(sc->mem_res, off);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
2017-03-17 22:57:37 +00:00
|
|
|
sdhci_acpi_write_1(device_t dev, struct sdhci_slot *slot __unused,
|
|
|
|
|
bus_size_t off, uint8_t val)
|
2017-01-11 01:53:54 +00:00
|
|
|
{
|
|
|
|
|
struct sdhci_acpi_softc *sc = device_get_softc(dev);
|
|
|
|
|
|
|
|
|
|
bus_barrier(sc->mem_res, 0, 0xFF,
|
|
|
|
|
BUS_SPACE_BARRIER_READ | BUS_SPACE_BARRIER_WRITE);
|
|
|
|
|
bus_write_1(sc->mem_res, off, val);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static uint16_t
|
2017-03-17 22:57:37 +00:00
|
|
|
sdhci_acpi_read_2(device_t dev, struct sdhci_slot *slot __unused,
|
|
|
|
|
bus_size_t off)
|
2017-01-11 01:53:54 +00:00
|
|
|
{
|
|
|
|
|
struct sdhci_acpi_softc *sc = device_get_softc(dev);
|
|
|
|
|
|
|
|
|
|
bus_barrier(sc->mem_res, 0, 0xFF,
|
|
|
|
|
BUS_SPACE_BARRIER_READ | BUS_SPACE_BARRIER_WRITE);
|
|
|
|
|
return bus_read_2(sc->mem_res, off);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
2017-03-17 22:57:37 +00:00
|
|
|
sdhci_acpi_write_2(device_t dev, struct sdhci_slot *slot __unused,
|
|
|
|
|
bus_size_t off, uint16_t val)
|
2017-01-11 01:53:54 +00:00
|
|
|
{
|
|
|
|
|
struct sdhci_acpi_softc *sc = device_get_softc(dev);
|
|
|
|
|
|
|
|
|
|
bus_barrier(sc->mem_res, 0, 0xFF,
|
|
|
|
|
BUS_SPACE_BARRIER_READ | BUS_SPACE_BARRIER_WRITE);
|
|
|
|
|
bus_write_2(sc->mem_res, off, val);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static uint32_t
|
2017-03-17 22:57:37 +00:00
|
|
|
sdhci_acpi_read_4(device_t dev, struct sdhci_slot *slot __unused,
|
|
|
|
|
bus_size_t off)
|
2017-01-11 01:53:54 +00:00
|
|
|
{
|
|
|
|
|
struct sdhci_acpi_softc *sc = device_get_softc(dev);
|
|
|
|
|
|
|
|
|
|
bus_barrier(sc->mem_res, 0, 0xFF,
|
|
|
|
|
BUS_SPACE_BARRIER_READ | BUS_SPACE_BARRIER_WRITE);
|
|
|
|
|
return bus_read_4(sc->mem_res, off);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
2017-03-17 22:57:37 +00:00
|
|
|
sdhci_acpi_write_4(device_t dev, struct sdhci_slot *slot __unused,
|
|
|
|
|
bus_size_t off, uint32_t val)
|
2017-01-11 01:53:54 +00:00
|
|
|
{
|
|
|
|
|
struct sdhci_acpi_softc *sc = device_get_softc(dev);
|
|
|
|
|
|
|
|
|
|
bus_barrier(sc->mem_res, 0, 0xFF,
|
|
|
|
|
BUS_SPACE_BARRIER_READ | BUS_SPACE_BARRIER_WRITE);
|
|
|
|
|
bus_write_4(sc->mem_res, off, val);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
2017-03-17 22:57:37 +00:00
|
|
|
sdhci_acpi_read_multi_4(device_t dev, struct sdhci_slot *slot __unused,
|
2017-01-11 01:53:54 +00:00
|
|
|
bus_size_t off, uint32_t *data, bus_size_t count)
|
|
|
|
|
{
|
|
|
|
|
struct sdhci_acpi_softc *sc = device_get_softc(dev);
|
|
|
|
|
|
|
|
|
|
bus_read_multi_stream_4(sc->mem_res, off, data, count);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
2017-03-17 22:57:37 +00:00
|
|
|
sdhci_acpi_write_multi_4(device_t dev, struct sdhci_slot *slot __unused,
|
2017-01-11 01:53:54 +00:00
|
|
|
bus_size_t off, uint32_t *data, bus_size_t count)
|
|
|
|
|
{
|
|
|
|
|
struct sdhci_acpi_softc *sc = device_get_softc(dev);
|
|
|
|
|
|
|
|
|
|
bus_write_multi_stream_4(sc->mem_res, off, data, count);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static const struct sdhci_acpi_device *
|
|
|
|
|
sdhci_acpi_find_device(device_t dev)
|
|
|
|
|
{
|
|
|
|
|
const char *hid;
|
|
|
|
|
int i, uid;
|
|
|
|
|
ACPI_HANDLE handle;
|
|
|
|
|
ACPI_STATUS status;
|
|
|
|
|
|
|
|
|
|
hid = ACPI_ID_PROBE(device_get_parent(dev), dev, sdhci_ids);
|
|
|
|
|
if (hid == NULL)
|
|
|
|
|
return (NULL);
|
|
|
|
|
|
|
|
|
|
handle = acpi_get_handle(dev);
|
|
|
|
|
status = acpi_GetInteger(handle, "_UID", &uid);
|
|
|
|
|
if (ACPI_FAILURE(status))
|
|
|
|
|
uid = 0;
|
|
|
|
|
|
|
|
|
|
for (i = 0; sdhci_acpi_devices[i].hid != NULL; i++) {
|
|
|
|
|
if (strcmp(sdhci_acpi_devices[i].hid, hid) != 0)
|
|
|
|
|
continue;
|
|
|
|
|
if ((sdhci_acpi_devices[i].uid != 0) &&
|
|
|
|
|
(sdhci_acpi_devices[i].uid != uid))
|
|
|
|
|
continue;
|
2017-03-06 23:47:59 +00:00
|
|
|
return (&sdhci_acpi_devices[i]);
|
2017-01-11 01:53:54 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return (NULL);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static int
|
|
|
|
|
sdhci_acpi_probe(device_t dev)
|
|
|
|
|
{
|
|
|
|
|
const struct sdhci_acpi_device *acpi_dev;
|
|
|
|
|
|
|
|
|
|
acpi_dev = sdhci_acpi_find_device(dev);
|
|
|
|
|
if (acpi_dev == NULL)
|
|
|
|
|
return (ENXIO);
|
|
|
|
|
|
|
|
|
|
device_set_desc(dev, acpi_dev->desc);
|
|
|
|
|
|
|
|
|
|
return (BUS_PROBE_DEFAULT);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static int
|
|
|
|
|
sdhci_acpi_attach(device_t dev)
|
|
|
|
|
{
|
|
|
|
|
struct sdhci_acpi_softc *sc = device_get_softc(dev);
|
|
|
|
|
int rid, err;
|
|
|
|
|
const struct sdhci_acpi_device *acpi_dev;
|
|
|
|
|
|
|
|
|
|
acpi_dev = sdhci_acpi_find_device(dev);
|
|
|
|
|
if (acpi_dev == NULL)
|
|
|
|
|
return (ENXIO);
|
|
|
|
|
|
|
|
|
|
sc->quirks = acpi_dev->quirks;
|
|
|
|
|
|
|
|
|
|
/* Allocate IRQ. */
|
|
|
|
|
rid = 0;
|
|
|
|
|
sc->irq_res = bus_alloc_resource_any(dev, SYS_RES_IRQ, &rid,
|
|
|
|
|
RF_ACTIVE);
|
|
|
|
|
if (sc->irq_res == NULL) {
|
|
|
|
|
device_printf(dev, "can't allocate IRQ\n");
|
|
|
|
|
return (ENOMEM);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
rid = 0;
|
|
|
|
|
sc->mem_res = bus_alloc_resource_any(dev, SYS_RES_MEMORY,
|
|
|
|
|
&rid, RF_ACTIVE);
|
|
|
|
|
if (sc->mem_res == NULL) {
|
|
|
|
|
device_printf(dev, "can't allocate memory resource for slot\n");
|
|
|
|
|
sdhci_acpi_detach(dev);
|
|
|
|
|
return (ENOMEM);
|
|
|
|
|
}
|
2017-01-29 00:05:49 +00:00
|
|
|
|
- Unlike as in the PCI case, when attached to ACPI, Intel Bay Trail
and Braswell eMMC and SDXC controllers share the same IDs. Like in
the PCI case, Braswell eMMC needs the SDHCI_QUIRK_DATA_TIMEOUT_1MHZ
quirk (see r311794 for the corresponding change to the sdhci(4) PCI
PCI front-end), though. However, due to the shared ACPI IDs, this
is trickier to do.
- Intel Apollo Lake eMMC and SDXC controllers are affected by the
APL18 ("Using 32-bit Addressing Mode With SD/eMMC Controller May
Lead to Unpredictable System Behavior") silicon bug [1]. When this
erratum hits, typically both SDHCI and XHCI controllers wedge.
According to Intel, using ADMA2 with 64-bit addressing and 96-bit
descriptors serves as a workaround. Until such times when sdhci(4)
has ADMA2 support, flag DMA as broken for affected interfaces.
This turns out to work around the problem, too, at the cost of
performance.
- In the sdhci(4) ACPI front-end, probe the Intel Apollo Lake eMMC
and SDXC controllers, too.
1: http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/pentium-celeron-n-series-j-series-datasheet-spec-update.pdf
2017-05-14 21:33:01 +00:00
|
|
|
/* Intel Braswell eMMC 4.5.1 controller quirk */
|
|
|
|
|
if (strcmp(acpi_dev->hid, "80860F14") == 0 && acpi_dev->uid == 1 &&
|
|
|
|
|
SDHCI_READ_4(dev, &sc->slot, SDHCI_CAPABILITIES) == 0x446cc8b2 &&
|
|
|
|
|
SDHCI_READ_4(dev, &sc->slot, SDHCI_CAPABILITIES2) == 0x00000807)
|
|
|
|
|
sc->quirks |= SDHCI_QUIRK_DATA_TIMEOUT_1MHZ;
|
o Add support for eMMC DDR bus speed mode at 52 MHz to sdhci(4) and
mmc(4). For the most part, this consists of support for:
- Switching the signal voltage (VCCQ) to 1.8 V or (if supported
by the host controller) to 1.2 V,
- setting the UHS mode as appropriate in the SDHCI_HOST_CONTROL2
register,
- setting the power class in the eMMC device according to the
core supply voltage (VCC),
- using different bits for enabling a bus width of 4 and 8 bits
in the the eMMC device at DDR or higher timings respectively,
- arbitrating timings faster than high speed if there actually
are additional devices on the same MMC bus.
Given that support for DDR52 is not denoted by SDHCI capability
registers, availability of that timing is indicated by a new
quirk SDHCI_QUIRK_MMC_DDR52 and only enabled for Intel SDHCI
controllers so far. Generally, what it takes for a sdhci(4)
front-end to enable support for DDR52 is to hook up the bridge
method mmcbr_switch_vccq (which especially for 1.2 V signaling
support is chip/board specific) and the sdhci_set_uhs_timing
sdhci(4) method.
As a side-effect, this change also fixes communication with
some eMMC devices at SDR high speed mode with 52 MHz due to
the signaling voltage and UHS bits in the SDHCI controller no
longer being left in an inappropriate state.
Compared to 52 MHz at SDR high speed which typically yields
~45 MB/s with the eMMC chips tested, throughput goes up to
~80 MB/s at DDR52.
Additionally, this change already adds infrastructure and quite
some code for modes up to HS400ES and SDR104 respectively (I did
not want to add to much stuff at a time, though). Essentially,
what is still missing in order to be able to activate support
for these latter is is support for and handling of (re-)tuning.
o In sdhci(4), add two tunables hw.sdhci.quirk_clear as well as
hw.sdhci.quirk_set, which (when hooked up in the front-end)
allow to set/clear sdhci(4) quirks for debugging and testing
purposes. However, especially for SDHCI controllers on the
PCI bus which have no specific support code so far and, thus,
are picked up as generic SDHCI controllers, hw.sdhci.quirk_set
allows for setting the necessary quirks (if required).
o In mmc(4), check and handle the return values of some more
function calls instead of assuming that everything went right.
In case failures actually are not problematic, indicate that
by casting the return value to void.
Reviewed by: jmcneill
2017-03-19 23:27:17 +00:00
|
|
|
sc->quirks &= ~sdhci_quirk_clear;
|
|
|
|
|
sc->quirks |= sdhci_quirk_set;
|
2017-01-11 01:53:54 +00:00
|
|
|
sc->slot.quirks = sc->quirks;
|
|
|
|
|
|
|
|
|
|
err = sdhci_init_slot(dev, &sc->slot, 0);
|
|
|
|
|
if (err) {
|
|
|
|
|
device_printf(dev, "failed to init slot\n");
|
|
|
|
|
sdhci_acpi_detach(dev);
|
|
|
|
|
return (err);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Activate the interrupt */
|
|
|
|
|
err = bus_setup_intr(dev, sc->irq_res, INTR_TYPE_MISC | INTR_MPSAFE,
|
|
|
|
|
NULL, sdhci_acpi_intr, sc, &sc->intrhand);
|
|
|
|
|
if (err) {
|
|
|
|
|
device_printf(dev, "can't setup IRQ\n");
|
|
|
|
|
sdhci_acpi_detach(dev);
|
|
|
|
|
return (err);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Process cards detection. */
|
|
|
|
|
sdhci_start_slot(&sc->slot);
|
|
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static int
|
|
|
|
|
sdhci_acpi_detach(device_t dev)
|
|
|
|
|
{
|
|
|
|
|
struct sdhci_acpi_softc *sc = device_get_softc(dev);
|
|
|
|
|
|
|
|
|
|
if (sc->intrhand)
|
|
|
|
|
bus_teardown_intr(dev, sc->irq_res, sc->intrhand);
|
|
|
|
|
if (sc->irq_res)
|
|
|
|
|
bus_release_resource(dev, SYS_RES_IRQ,
|
|
|
|
|
rman_get_rid(sc->irq_res), sc->irq_res);
|
|
|
|
|
|
|
|
|
|
if (sc->mem_res) {
|
|
|
|
|
sdhci_cleanup_slot(&sc->slot);
|
|
|
|
|
bus_release_resource(dev, SYS_RES_MEMORY,
|
|
|
|
|
rman_get_rid(sc->mem_res), sc->mem_res);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static int
|
|
|
|
|
sdhci_acpi_shutdown(device_t dev)
|
|
|
|
|
{
|
|
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static int
|
|
|
|
|
sdhci_acpi_suspend(device_t dev)
|
|
|
|
|
{
|
|
|
|
|
struct sdhci_acpi_softc *sc = device_get_softc(dev);
|
|
|
|
|
int err;
|
|
|
|
|
|
|
|
|
|
err = bus_generic_suspend(dev);
|
|
|
|
|
if (err)
|
|
|
|
|
return (err);
|
|
|
|
|
sdhci_generic_suspend(&sc->slot);
|
|
|
|
|
return (0);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static int
|
|
|
|
|
sdhci_acpi_resume(device_t dev)
|
|
|
|
|
{
|
|
|
|
|
struct sdhci_acpi_softc *sc = device_get_softc(dev);
|
|
|
|
|
int err;
|
|
|
|
|
|
|
|
|
|
sdhci_generic_resume(&sc->slot);
|
|
|
|
|
err = bus_generic_resume(dev);
|
|
|
|
|
if (err)
|
|
|
|
|
return (err);
|
|
|
|
|
return (0);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
sdhci_acpi_intr(void *arg)
|
|
|
|
|
{
|
|
|
|
|
struct sdhci_acpi_softc *sc = (struct sdhci_acpi_softc *)arg;
|
|
|
|
|
|
|
|
|
|
sdhci_generic_intr(&sc->slot);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static device_method_t sdhci_methods[] = {
|
|
|
|
|
/* device_if */
|
|
|
|
|
DEVMETHOD(device_probe, sdhci_acpi_probe),
|
|
|
|
|
DEVMETHOD(device_attach, sdhci_acpi_attach),
|
|
|
|
|
DEVMETHOD(device_detach, sdhci_acpi_detach),
|
|
|
|
|
DEVMETHOD(device_shutdown, sdhci_acpi_shutdown),
|
|
|
|
|
DEVMETHOD(device_suspend, sdhci_acpi_suspend),
|
|
|
|
|
DEVMETHOD(device_resume, sdhci_acpi_resume),
|
|
|
|
|
|
|
|
|
|
/* Bus interface */
|
|
|
|
|
DEVMETHOD(bus_read_ivar, sdhci_generic_read_ivar),
|
|
|
|
|
DEVMETHOD(bus_write_ivar, sdhci_generic_write_ivar),
|
|
|
|
|
|
|
|
|
|
/* mmcbr_if */
|
2017-01-29 00:05:49 +00:00
|
|
|
DEVMETHOD(mmcbr_update_ios, sdhci_generic_update_ios),
|
o Add support for eMMC DDR bus speed mode at 52 MHz to sdhci(4) and
mmc(4). For the most part, this consists of support for:
- Switching the signal voltage (VCCQ) to 1.8 V or (if supported
by the host controller) to 1.2 V,
- setting the UHS mode as appropriate in the SDHCI_HOST_CONTROL2
register,
- setting the power class in the eMMC device according to the
core supply voltage (VCC),
- using different bits for enabling a bus width of 4 and 8 bits
in the the eMMC device at DDR or higher timings respectively,
- arbitrating timings faster than high speed if there actually
are additional devices on the same MMC bus.
Given that support for DDR52 is not denoted by SDHCI capability
registers, availability of that timing is indicated by a new
quirk SDHCI_QUIRK_MMC_DDR52 and only enabled for Intel SDHCI
controllers so far. Generally, what it takes for a sdhci(4)
front-end to enable support for DDR52 is to hook up the bridge
method mmcbr_switch_vccq (which especially for 1.2 V signaling
support is chip/board specific) and the sdhci_set_uhs_timing
sdhci(4) method.
As a side-effect, this change also fixes communication with
some eMMC devices at SDR high speed mode with 52 MHz due to
the signaling voltage and UHS bits in the SDHCI controller no
longer being left in an inappropriate state.
Compared to 52 MHz at SDR high speed which typically yields
~45 MB/s with the eMMC chips tested, throughput goes up to
~80 MB/s at DDR52.
Additionally, this change already adds infrastructure and quite
some code for modes up to HS400ES and SDR104 respectively (I did
not want to add to much stuff at a time, though). Essentially,
what is still missing in order to be able to activate support
for these latter is is support for and handling of (re-)tuning.
o In sdhci(4), add two tunables hw.sdhci.quirk_clear as well as
hw.sdhci.quirk_set, which (when hooked up in the front-end)
allow to set/clear sdhci(4) quirks for debugging and testing
purposes. However, especially for SDHCI controllers on the
PCI bus which have no specific support code so far and, thus,
are picked up as generic SDHCI controllers, hw.sdhci.quirk_set
allows for setting the necessary quirks (if required).
o In mmc(4), check and handle the return values of some more
function calls instead of assuming that everything went right.
In case failures actually are not problematic, indicate that
by casting the return value to void.
Reviewed by: jmcneill
2017-03-19 23:27:17 +00:00
|
|
|
DEVMETHOD(mmcbr_switch_vccq, sdhci_generic_switch_vccq),
|
2017-01-29 00:05:49 +00:00
|
|
|
DEVMETHOD(mmcbr_request, sdhci_generic_request),
|
|
|
|
|
DEVMETHOD(mmcbr_get_ro, sdhci_generic_get_ro),
|
2017-01-11 01:53:54 +00:00
|
|
|
DEVMETHOD(mmcbr_acquire_host, sdhci_generic_acquire_host),
|
|
|
|
|
DEVMETHOD(mmcbr_release_host, sdhci_generic_release_host),
|
|
|
|
|
|
o Add support for eMMC DDR bus speed mode at 52 MHz to sdhci(4) and
mmc(4). For the most part, this consists of support for:
- Switching the signal voltage (VCCQ) to 1.8 V or (if supported
by the host controller) to 1.2 V,
- setting the UHS mode as appropriate in the SDHCI_HOST_CONTROL2
register,
- setting the power class in the eMMC device according to the
core supply voltage (VCC),
- using different bits for enabling a bus width of 4 and 8 bits
in the the eMMC device at DDR or higher timings respectively,
- arbitrating timings faster than high speed if there actually
are additional devices on the same MMC bus.
Given that support for DDR52 is not denoted by SDHCI capability
registers, availability of that timing is indicated by a new
quirk SDHCI_QUIRK_MMC_DDR52 and only enabled for Intel SDHCI
controllers so far. Generally, what it takes for a sdhci(4)
front-end to enable support for DDR52 is to hook up the bridge
method mmcbr_switch_vccq (which especially for 1.2 V signaling
support is chip/board specific) and the sdhci_set_uhs_timing
sdhci(4) method.
As a side-effect, this change also fixes communication with
some eMMC devices at SDR high speed mode with 52 MHz due to
the signaling voltage and UHS bits in the SDHCI controller no
longer being left in an inappropriate state.
Compared to 52 MHz at SDR high speed which typically yields
~45 MB/s with the eMMC chips tested, throughput goes up to
~80 MB/s at DDR52.
Additionally, this change already adds infrastructure and quite
some code for modes up to HS400ES and SDR104 respectively (I did
not want to add to much stuff at a time, though). Essentially,
what is still missing in order to be able to activate support
for these latter is is support for and handling of (re-)tuning.
o In sdhci(4), add two tunables hw.sdhci.quirk_clear as well as
hw.sdhci.quirk_set, which (when hooked up in the front-end)
allow to set/clear sdhci(4) quirks for debugging and testing
purposes. However, especially for SDHCI controllers on the
PCI bus which have no specific support code so far and, thus,
are picked up as generic SDHCI controllers, hw.sdhci.quirk_set
allows for setting the necessary quirks (if required).
o In mmc(4), check and handle the return values of some more
function calls instead of assuming that everything went right.
In case failures actually are not problematic, indicate that
by casting the return value to void.
Reviewed by: jmcneill
2017-03-19 23:27:17 +00:00
|
|
|
/* SDHCI accessors */
|
2017-01-11 01:53:54 +00:00
|
|
|
DEVMETHOD(sdhci_read_1, sdhci_acpi_read_1),
|
|
|
|
|
DEVMETHOD(sdhci_read_2, sdhci_acpi_read_2),
|
|
|
|
|
DEVMETHOD(sdhci_read_4, sdhci_acpi_read_4),
|
|
|
|
|
DEVMETHOD(sdhci_read_multi_4, sdhci_acpi_read_multi_4),
|
|
|
|
|
DEVMETHOD(sdhci_write_1, sdhci_acpi_write_1),
|
|
|
|
|
DEVMETHOD(sdhci_write_2, sdhci_acpi_write_2),
|
|
|
|
|
DEVMETHOD(sdhci_write_4, sdhci_acpi_write_4),
|
|
|
|
|
DEVMETHOD(sdhci_write_multi_4, sdhci_acpi_write_multi_4),
|
o Add support for eMMC DDR bus speed mode at 52 MHz to sdhci(4) and
mmc(4). For the most part, this consists of support for:
- Switching the signal voltage (VCCQ) to 1.8 V or (if supported
by the host controller) to 1.2 V,
- setting the UHS mode as appropriate in the SDHCI_HOST_CONTROL2
register,
- setting the power class in the eMMC device according to the
core supply voltage (VCC),
- using different bits for enabling a bus width of 4 and 8 bits
in the the eMMC device at DDR or higher timings respectively,
- arbitrating timings faster than high speed if there actually
are additional devices on the same MMC bus.
Given that support for DDR52 is not denoted by SDHCI capability
registers, availability of that timing is indicated by a new
quirk SDHCI_QUIRK_MMC_DDR52 and only enabled for Intel SDHCI
controllers so far. Generally, what it takes for a sdhci(4)
front-end to enable support for DDR52 is to hook up the bridge
method mmcbr_switch_vccq (which especially for 1.2 V signaling
support is chip/board specific) and the sdhci_set_uhs_timing
sdhci(4) method.
As a side-effect, this change also fixes communication with
some eMMC devices at SDR high speed mode with 52 MHz due to
the signaling voltage and UHS bits in the SDHCI controller no
longer being left in an inappropriate state.
Compared to 52 MHz at SDR high speed which typically yields
~45 MB/s with the eMMC chips tested, throughput goes up to
~80 MB/s at DDR52.
Additionally, this change already adds infrastructure and quite
some code for modes up to HS400ES and SDR104 respectively (I did
not want to add to much stuff at a time, though). Essentially,
what is still missing in order to be able to activate support
for these latter is is support for and handling of (re-)tuning.
o In sdhci(4), add two tunables hw.sdhci.quirk_clear as well as
hw.sdhci.quirk_set, which (when hooked up in the front-end)
allow to set/clear sdhci(4) quirks for debugging and testing
purposes. However, especially for SDHCI controllers on the
PCI bus which have no specific support code so far and, thus,
are picked up as generic SDHCI controllers, hw.sdhci.quirk_set
allows for setting the necessary quirks (if required).
o In mmc(4), check and handle the return values of some more
function calls instead of assuming that everything went right.
In case failures actually are not problematic, indicate that
by casting the return value to void.
Reviewed by: jmcneill
2017-03-19 23:27:17 +00:00
|
|
|
DEVMETHOD(sdhci_set_uhs_timing, sdhci_generic_set_uhs_timing),
|
2017-01-11 01:53:54 +00:00
|
|
|
|
|
|
|
|
DEVMETHOD_END
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static driver_t sdhci_acpi_driver = {
|
|
|
|
|
"sdhci_acpi",
|
|
|
|
|
sdhci_methods,
|
|
|
|
|
sizeof(struct sdhci_acpi_softc),
|
|
|
|
|
};
|
|
|
|
|
static devclass_t sdhci_acpi_devclass;
|
|
|
|
|
|
|
|
|
|
DRIVER_MODULE(sdhci_acpi, acpi, sdhci_acpi_driver, sdhci_acpi_devclass, NULL,
|
|
|
|
|
NULL);
|
|
|
|
|
MODULE_DEPEND(sdhci_acpi, sdhci, 1, 1, 1);
|
2017-03-07 22:42:44 +00:00
|
|
|
MMC_DECLARE_BRIDGE(sdhci_acpi);
|
