0f34084f95
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
133 lines
4.4 KiB
Objective-C
133 lines
4.4 KiB
Objective-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 AND CONTRIBUTORS ``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 OR CONTRIBUTORS 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$
|
|
#
|
|
|
|
#include <sys/types.h>
|
|
#include <dev/mmc/bridge.h>
|
|
#include <dev/mmc/mmcreg.h>
|
|
|
|
#
|
|
# This is the interface that a mmc bridge chip gives to the mmc bus
|
|
# that attaches to the mmc bridge.
|
|
#
|
|
|
|
INTERFACE mmcbr;
|
|
|
|
#
|
|
# Default implementations of some methods.
|
|
#
|
|
CODE {
|
|
static int
|
|
null_switch_vccq(device_t brdev __unused, device_t reqdev __unused)
|
|
{
|
|
|
|
return (0);
|
|
}
|
|
};
|
|
|
|
#
|
|
# Called by the mmcbus to set up the IO pins correctly, the common/core
|
|
# supply voltage (VDD/VCC) to use for the device, the clock frequency, the
|
|
# type of SPI chip select, power mode and bus width.
|
|
#
|
|
METHOD int update_ios {
|
|
device_t brdev;
|
|
device_t reqdev;
|
|
};
|
|
|
|
#
|
|
# Called by the mmcbus to switch the signaling voltage (VCCQ).
|
|
#
|
|
METHOD int switch_vccq {
|
|
device_t brdev;
|
|
device_t reqdev;
|
|
} DEFAULT null_switch_vccq;
|
|
|
|
#
|
|
# Called by the mmcbus or its children to schedule a mmc request. These
|
|
# requests are queued. Time passes. The bridge then gets notification
|
|
# of the status of the request, who then notifies the requesting device
|
|
# by calling the completion function supplied as part of the request.
|
|
#
|
|
METHOD int request {
|
|
device_t brdev;
|
|
device_t reqdev;
|
|
struct mmc_request *req;
|
|
};
|
|
|
|
#
|
|
# Called by mmcbus to get the read only status bits.
|
|
#
|
|
METHOD int get_ro {
|
|
device_t brdev;
|
|
device_t reqdev;
|
|
};
|
|
|
|
#
|
|
# Claim the current bridge, blocking the current thread until the host
|
|
# is no longer busy.
|
|
#
|
|
METHOD int acquire_host {
|
|
device_t brdev;
|
|
device_t reqdev;
|
|
}
|
|
|
|
#
|
|
# Release the current bridge.
|
|
#
|
|
METHOD int release_host {
|
|
device_t brdev;
|
|
device_t reqdev;
|
|
}
|