72dec0792a
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)
153 lines
5.9 KiB
C
153 lines
5.9 KiB
C
/*-
|
|
* Copyright (c) 2006 M. Warner Losh. 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.
|
|
*
|
|
* Portions of this software may have been developed with reference to
|
|
* the SD Simplified Specification. The following disclaimer may apply:
|
|
*
|
|
* The following conditions apply to the release of the simplified
|
|
* specification ("Simplified Specification") by the SD Card Association and
|
|
* the SD Group. The Simplified Specification is a subset of the complete SD
|
|
* Specification which is owned by the SD Card Association and the SD
|
|
* Group. This Simplified Specification is provided on a non-confidential
|
|
* basis subject to the disclaimers below. Any implementation of the
|
|
* Simplified Specification may require a license from the SD Card
|
|
* Association, SD Group, SD-3C LLC or other third parties.
|
|
*
|
|
* Disclaimers:
|
|
*
|
|
* The information contained in the Simplified Specification is presented only
|
|
* as a standard specification for SD Cards and SD Host/Ancillary products and
|
|
* is provided "AS-IS" without any representations or warranties of any
|
|
* kind. No responsibility is assumed by the SD Group, SD-3C LLC or the SD
|
|
* Card Association for any damages, any infringements of patents or other
|
|
* right of the SD Group, SD-3C LLC, the SD Card Association or any third
|
|
* parties, which may result from its use. No license is granted by
|
|
* implication, estoppel or otherwise under any patent or other rights of the
|
|
* SD Group, SD-3C LLC, the SD Card Association or any third party. Nothing
|
|
* herein shall be construed as an obligation by the SD Group, the SD-3C LLC
|
|
* or the SD Card Association to disclose or distribute any technical
|
|
* information, know-how or other confidential information to any third party.
|
|
*
|
|
* $FreeBSD$
|
|
*/
|
|
|
|
#ifndef DEV_MMC_BRIDGE_H
|
|
#define DEV_MMC_BRIDGE_H
|
|
|
|
#include <sys/bus.h>
|
|
|
|
/*
|
|
* This file defines interfaces for the mmc bridge. The names chosen
|
|
* are similar to or the same as the names used in Linux to allow for
|
|
* easy porting of what Linux calls mmc host drivers. I use the
|
|
* FreeBSD terminology of bridge and bus for consistency with other
|
|
* drivers in the system. This file corresponds roughly to the Linux
|
|
* linux/mmc/host.h file.
|
|
*
|
|
* A mmc bridge is a chipset that can have one or more mmc and/or sd
|
|
* cards attached to it. mmc cards are attached on a bus topology,
|
|
* while sd and sdio cards are attached using a star topology (meaning
|
|
* in practice each sd card has its own, independent slot). Each
|
|
* mmcbr is assumed to be derived from the mmcbr. This is done to
|
|
* allow for easier addition of bridges (as each bridge does not need
|
|
* to be added to the mmcbus file).
|
|
*
|
|
* Attached to the mmc bridge is an mmcbus. The mmcbus is described
|
|
* in dev/mmc/mmcbus_if.m.
|
|
*/
|
|
|
|
/*
|
|
* mmc_ios is a structure that is used to store the state of the mmc/sd
|
|
* bus configuration. This include the bus' clock speed, its voltage,
|
|
* the bus mode for command output, the SPI chip select, some power
|
|
* states and the bus width.
|
|
*/
|
|
enum mmc_vdd {
|
|
vdd_150 = 0, vdd_155, vdd_160, vdd_165, vdd_170, vdd_180,
|
|
vdd_190, vdd_200, vdd_210, vdd_220, vdd_230, vdd_240, vdd_250,
|
|
vdd_260, vdd_270, vdd_280, vdd_290, vdd_300, vdd_310, vdd_320,
|
|
vdd_330, vdd_340, vdd_350, vdd_360
|
|
};
|
|
|
|
enum mmc_power_mode {
|
|
power_off = 0, power_up, power_on
|
|
};
|
|
|
|
enum mmc_bus_mode {
|
|
opendrain = 1, pushpull
|
|
};
|
|
|
|
enum mmc_chip_select {
|
|
cs_dontcare = 0, cs_high, cs_low
|
|
};
|
|
|
|
enum mmc_bus_width {
|
|
bus_width_1 = 0, bus_width_4 = 2, bus_width_8 = 3
|
|
};
|
|
|
|
enum mmc_bus_timing {
|
|
bus_timing_normal = 0, bus_timing_hs
|
|
};
|
|
|
|
struct mmc_ios {
|
|
uint32_t clock; /* Speed of the clock in Hz to move data */
|
|
enum mmc_vdd vdd; /* Voltage to apply to the power pins/ */
|
|
enum mmc_bus_mode bus_mode;
|
|
enum mmc_chip_select chip_select;
|
|
enum mmc_bus_width bus_width;
|
|
enum mmc_power_mode power_mode;
|
|
enum mmc_bus_timing timing;
|
|
};
|
|
|
|
enum mmc_card_mode {
|
|
mode_mmc, mode_sd
|
|
};
|
|
|
|
struct mmc_host {
|
|
int f_min;
|
|
int f_max;
|
|
uint32_t host_ocr;
|
|
uint32_t ocr;
|
|
uint32_t caps;
|
|
#define MMC_CAP_4_BIT_DATA (1 << 0) /* Can do 4-bit data transfers */
|
|
#define MMC_CAP_8_BIT_DATA (1 << 1) /* Can do 8-bit data transfers */
|
|
#define MMC_CAP_HSPEED (1 << 2) /* Can do High Speed transfers */
|
|
#define MMC_CAP_BOOT_NOACC (1 << 4) /* Cannot access boot partitions */
|
|
#define MMC_CAP_WAIT_WHILE_BUSY (1 << 5) /* Host waits for busy responses */
|
|
enum mmc_card_mode mode;
|
|
struct mmc_ios ios; /* Current state of the host */
|
|
};
|
|
|
|
extern driver_t mmc_driver;
|
|
extern devclass_t mmc_devclass;
|
|
|
|
#define MMC_VERSION 2
|
|
|
|
#define MMC_DECLARE_BRIDGE(name) \
|
|
DRIVER_MODULE(mmc, name, mmc_driver, mmc_devclass, NULL, NULL); \
|
|
MODULE_DEPEND(name, mmc, MMC_VERSION, MMC_VERSION, MMC_VERSION);
|
|
#define MMC_DEPEND(name) \
|
|
MODULE_DEPEND(name, mmc, MMC_VERSION, MMC_VERSION, MMC_VERSION);
|
|
|
|
#endif /* DEV_MMC_BRIDGE_H */
|