FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F10.1.0 2014-08-11T01:22:10Z 2014-08-11T01:22:10Z Ian Lepore ian@FreeBSD.org 2014-08-11T01:22:10Z urn:sha1:cdc42107a7b59619e364a3d0f863b10ee1f7c1f3 2014-05-15T22:35:04Z Ian Lepore ian@FreeBSD.org 2014-05-15T22:35:04Z urn:sha1:68602f513a7eefc7bbb559936a5d47ae64cbc25f r261955, r261958, Add a driver to provide access to imx6 on-chip one-time-programmble data. Make it possible to access the ocotp registers before the ocotp device is attached, by establishing a temporary mapping of the registers when necessary. It turns out Freescale cleverly made the ocotp device compatible across several different families of SoCs, so move it to the freescale directory and prefix everything with fsl rather than imx6. Convert the imx6 sdhci "R1B fix" from a busy-loop in the interrupt handler to a callout. Increase the wait time for acquiring the SD bus from 10 to 250ms. If no compatible cards were found after probing the SD bus, say so. Add timeout logic to sdhci, separate from the timeouts done by the hardware. After a timeout, reset the controller using SDHCI_RESET_CMD|SDHCI_RESET_DATA rather than SDHCI_RESET_ALL; the latter turns off clocks and power, removing any possibility of recovering from the error. Add a helper routine to depth-search the device tree for a node with a matching 'compatible' property. 2014-05-15T17:30:16Z Ian Lepore ian@FreeBSD.org 2014-05-15T17:30:16Z urn:sha1:aac49345d30f4a7d3a1f7d0a2736340168cc31d3 r261596, r261606 Add the imx sdhci controller. Move Open Firmware device root on PowerPC, ARM, and MIPS systems to a sub-node of nexus (ofwbus) rather than direct attach under nexus. This fixes FDT on x86 and will make coexistence with ACPI on ARM systems easier. SPARC is unchanged. Add the missing ')' at end of sentence. Reword it to use a more common idiom. Pass the kernel physical address to initarm through the boot param struct. Make functions only used in vfp.c static, and remove vfp_enable. Fix __syscall on armeb EABI. As it returns a 64-bit value it needs to place 32-bit data in r1, not r0. 64-bit data is already packed correctly. Use abp_physaddr for the physical address over KERNPHYSADDR. This helps us remove the need to load the kernel at a fixed address. Remove references to PHYSADDR where it's used only in debugging output. Dynamically generate the page table. This will allow us to detect the physical address we are loaded at to change the mapping. 2013-08-23T15:07:54Z Ian Lepore ian@FreeBSD.org 2013-08-23T15:07:54Z urn:sha1:a6e2415cc4b2f026f7c6dfa3cc55dd2c6a9180d8 mode. We don't know why it failed, so we can't know that a retry will also fail (the low-level driver might have reset the controller state machine or something similar that would allow a retry to work). 2013-08-20T12:33:35Z Ian Lepore ian@FreeBSD.org 2013-08-20T12:33:35Z urn:sha1:59769a581f13e040d88d5f5b2302887e7bc6c63f The MMCHS hardware is pretty much a standard SDHCI v2.0 controller with a couple quirks, which are now supported by sdhci(4) as of r254507. This should work for all TI SoCs that use the MMCHS hardware, but it has only been tested on AM335x right now, so this enables it on those platforms but leaves the existing ti_mmchs driver in place for other OMAP variants until they can be tested. This initial incarnation lacks DMA support (coming soon). Even without it this improves performance pretty noticibly over the ti_mmchs driver, primarily because it now does multiblock IO. 2013-08-17T00:19:27Z Ian Lepore ian@FreeBSD.org 2013-08-17T00:19:27Z urn:sha1:ed7142a72da78712e844f40399ea3844c0e7c70c before using them. 2013-08-16T23:05:34Z Ian Lepore ian@FreeBSD.org 2013-08-16T23:05:34Z urn:sha1:a8328210d05a13ccb5efb3e3ffe8424746c0228f ensure that all such commands have a non-zero retry count except for those that are expected to fail (for example, because they are used to probe for feature support). While it is possible to pass a retry count down to the hardware driver in the command request structure, no hardware driver currently implements any retry logic. The hardware doesn't know much about the context of a single request, so it makes more sense to handle retries at a layer that does. This adds retry loops to the mmc_wait_for_cmd() and mmc_wait_for_app_cmd() functions. These functions are the gateway from other code within mmc.c to the hardware. App commands are a sequence of two commands and a retry has to rerun both of them in order, so it needs its own retry loop. Retry looping is specifically NOT implemented in mmc_wait_for_request() because it is the gateway for children on the bus, and they have to implement their own retry logic depending on what makes sense for them. 2013-08-16T20:32:56Z Ian Lepore ian@FreeBSD.org 2013-08-16T20:32:56Z urn:sha1:df736d55a1bbf6f53e0d166e71920dbb80fcaef8 speed the bus claims to be capable of. The 400KHz speed is dictated by the SD and MMC standards. 2013-08-16T20:22:57Z Ian Lepore ian@FreeBSD.org 2013-08-16T20:22:57Z urn:sha1:65f63c73cb2b44bb378f46875acef64ba14bf865 other debugging output does (when it appears in command arguments, for example). 2013-07-09T03:00:06Z Rui Paulo rpaulo@FreeBSD.org 2013-07-09T03:00:06Z urn:sha1:88e07d922d89a6c36502eab5c2729ead700d6e9c This can be useful when we want to be able to identify which mmcsd is stuck.