History log of /dragonfly/sys/dev/disk/sdhci/sdhci_acpi.c (Results 1 – 8 of 8)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc
# df21e16d 28-Jan-2018 Imre Vadász <imre@vdsz.com>

acpi - Use KOBJ_GPRI_ACPI driver priorities for ig4 and gpio_intel.

* Since we currently don't handle the ACPI _DEP methods appropriately,
use the "global priority hack" from
5025fc65cd2448de8a5

acpi - Use KOBJ_GPRI_ACPI driver priorities for ig4 and gpio_intel.

* Since we currently don't handle the ACPI _DEP methods appropriately,
use the "global priority hack" from
5025fc65cd2448de8a5b7295c9936b473a7b0194 to enforce that ig4 and
gpio_intel attach before various ACPI namespace devices.

* This uses the KOBJ_GPRI_ACPI+1 and KOBJ_GPRI_ACPI+2 driver global priority
levels for important ACPI drivers, which may have to attach before other
ACPI devices can be used.

* This also adds the KOBJ_GPRI_ACPI global priority level to the sdhci_acpi
driver declaration.

show more ...


Revision tags: v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1
# ffb8e567 05-Jun-2017 Imre Vadász <imre@vdsz.com>

sdhci - Add missing BROKEN_DMA quirk for Apollo Lake in sdhci_acpi(4).

* Because of the APL18 erratum, DMA should be disabled on the Apollo Lake
controllers for now, until we have 64bit ADMA2, whi

sdhci - Add missing BROKEN_DMA quirk for Apollo Lake in sdhci_acpi(4).

* Because of the APL18 erratum, DMA should be disabled on the Apollo Lake
controllers for now, until we have 64bit ADMA2, which should work
reliably on these models. I forgot to add this flag in sdhci_acpi(4) in
commit 7ba10b88109826f7f4b59e318458760d74f2452e.

show more ...


# 7ba10b88 21-May-2017 Imre Vadász <imre@vdsz.com>

Port initial UHS-1 support from FreeBSD (Only DDR52 for eMMC so far).

* Fix typo from FreeBSD commit:
SDHCI_CTRL2_DRIVER_TYPE_A/_C_D vs. SDHCI_CAN_DRIVE_TYPE_A/_C/_D.
And these Driver Type capab

Port initial UHS-1 support from FreeBSD (Only DDR52 for eMMC so far).

* Fix typo from FreeBSD commit:
SDHCI_CTRL2_DRIVER_TYPE_A/_C_D vs. SDHCI_CAN_DRIVE_TYPE_A/_C/_D.
And these Driver Type capability bits are in the CAPABILITIES2 register.

* Hide 1.8V VDD capability when the slot is detected as a removable card
slot, as the spec explicitly states that the 1.8V VDD is only meant to
be for embedded slots.

* This gives ca. 75 MiB/s read speed with the eMMC in my HP X2 210
detachable with the Intel Cherry Trail eMMC controller, in DDR52 mode.

Taken-From: FreeBSD (svn r315598)

show more ...


# 85ccd313 21-May-2017 Imre Vadász <imre@vdsz.com>

A step to correctly handling command timeouts in the MMC layer.

- Now that properly issuing CMD6 is crucial (so data isn't written to
the wrong partition for example), make a step into the

A step to correctly handling command timeouts in the MMC layer.

- 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 ...

- 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.

* This omits all the parts specific to eMMC "partitions" from the FreeBSD
change.

* Add the Intel sdhci controller ids to sdhci_pci.c to set the
SDHCI_QUIRK_WAIT_WHILE_BUSY quirk there.
This also disables DMA on apollo lake sdhci, while there and whitelists
ADMA2 on Bay Trail and Braswell sdhci controllers.

Taken-From: FreeBSD (svn r315430)

show more ...


# 4d3ae590 21-May-2017 Imre Vadász <imre@vdsz.com>

More style, comments, includes and unused params fixes for sdhci and mmc.

Taken-From: FreeBSD (svn r314811)


# 70a02aad 20-May-2017 Imre Vadász <imre@vdsz.com>

Style fixes for sdhci(4) and mmc(4) in comments, includes, unused params.

Taken-From: FreeBSD (svn r315466)


Revision tags: v4.8.0, v4.6.2, v4.9.0, v4.8.0rc
# 4f67f60c 06-Jan-2017 Imre Vadász <imre@vdsz.com>

sdhci - Add tunables for disabling SDMA and/or ADMA2, and for testing ADMA2.

* Also document hw.sdhci.debug tunable while there.

* Limit ADMA2 support to the already tested and working Intel sdhci

sdhci - Add tunables for disabling SDMA and/or ADMA2, and for testing ADMA2.

* Also document hw.sdhci.debug tunable while there.

* Limit ADMA2 support to the already tested and working Intel sdhci
controllers for now. Currently we only explicitly match against the Intel
models in sdhci_acpi(4).
XXX sdhci_pci(4) should explicitly match against the Intel sdhci
controllers as well to whitelist ADMA2 support, via the
SDHCI_QUIRK_WHITELIST_ADMA2 flag.

* For testing on not-yet whitelisted models, add the hw.sdhci.adma2_test
tunable to skip the whitelist check.

show more ...


Revision tags: v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3
# 21f9f90c 10-Mar-2016 Imre Vadász <imre@vdsz.com>

sys/dev/disk/sdhci: Add sdhci_acpi for attaching via acpi resources.

* Only attaches on Bay- and Cherry-Trail atom devices.

* Not fully functional yet. At least this still needs fixes in mmc(4)
(

sys/dev/disk/sdhci: Add sdhci_acpi for attaching via acpi resources.

* Only attaches on Bay- and Cherry-Trail atom devices.

* Not fully functional yet. At least this still needs fixes in mmc(4)
(to get eMMC working) and ACPI improvements (for actually getting
SD-card bus power enabled via the _PS0 acpi method).

show more ...