6ce880241b
Backporting the following commits: 2b0cc0f0ca23 mmc: It is not an error for the card to be removed while suspended 67903c1f4c77 mmc: sdhci: 64-bit DMA actually has 4-byte alignment 4e434f483381 mmc: sdhci: Do not BUG on invalid vdd 05be442eb234 mmc: mmc: Fix incorrect use of driver strength switching HS200 and HS400 97a5f396dca6 mmc: core: Make runtime resume default behavior for MMC/SD b6ee1ac07f14 mmc: mmc: Improve reliability of mmc_select_hs400() 45de48ce0b3c mmc: mmc: Move mmc_switch_status() 9d6aaaa0f6b7 mmc: mmc: Fix HS setting in mmc_select_hs400() d7795de930c5 mmc: mmc: Improve reliability of mmc_select_hs200() ac98e33a088d mmc: sdhci-acpi: Add more ACPI HIDs for Intel controllers 87f52cce8123 mmc: sdhci-pci: Add more PCI IDs for Intel controllers cf3a4d2d4c7d mmc: sdhci-pci: Add another PCI ID for an Intel eMMC host controller b3ef45585504 mmc: sdhci-pci: Build o2micro support in the same module b32a4e71f49d mmc: sdhci: enable tuning for DDR50 f8e213bee1e1 mmc: sdhci: call sdhci_init() before request irq ece0925eb94e mmc: sdhci-pci: Enable HS400 for some Intel host controllers 1c01bcdceaf6 mmc: sdhci-pci: Add support for drive strength selection for SPT c1d6e92915a9 mmc: sdhci: Add a callback to select drive strength 40deb3ac3331 mmc: mmc: Add driver strength selection e7d602f5992f mmc: mmc: Read card's valid driver strength mask bc193a886571 mmc: core: Record card drive strength a548d3993cc8 mmc: core: Factor out common code in drive strength selection 6713f5cf3164 mmc: core: Add 'card' to drive strength selection callback 852e6bd69b77 mmc: core: Simplify card drive strength mask 0bb40266bbb9 mmc: core: Allow card drive strength to be different to host 940d30f1a212 mmc: core: Reset driver type to default efbc6ba8cd27 mmc: cast u8 to unsigned long long to avoid unexpected error bafe0e5beba9 mmc: core: Don't print reset warning if reset is not supported 5b2789151852 mmc: block: Retry errored data requests when re-tuning is needed d14211a4b2fe mmc: block: Check re-tuning in the recovery path 1ff15c648159 mmc: core: Flag re-tuning is needed on CRC errors 12544ee1cdbb mmc: sdhci: Change to new way of doing re-tuning 995073b182f7 mmc: core: Add support for HS400 re-tuning 53a0d731e824 mmc: core: Separate out the mmc_switch status check so it can be re-used d3f59f108bf7 mmc: mmc: Hold re-tuning in mmc_sleep() 465db9504a27 mmc: core: Hold re-tuning while bkops ongoing 60cacf85ee10 mmc: core: Hold re-tuning during erase commands 5bd43535f4c1 mmc: core: Hold re-tuning during switch commands 4baa45ff8d15 mmc: core: Add support for re-tuning before each request cd2ca27f9282 mmc: core: Enable / disable re-tuning 65723236b746 mmc: host: Add facility to support re-tuning (From OE-Core rev: 934fd9d7310ffc72e206f48590a0f10ba0a78e1b) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a complete prepackaged build system and development environment. It features support for building customised embedded device style images. There are reference demo images featuring a X11/Matchbox/GTK themed UI called Sato. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK with IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of layers which extend the systems capabilities in a modular way.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information e.g. for the hardware support. Poky is in turn a component of the Yocto Project.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at: http://yoctoproject.org/documentation
OpenEmbedded-Core is a layer containing the core metadata for current versions of OpenEmbedded. It is distro-less (can build a functional image with DISTRO = "nodistro") and contains only emulated machine support.
For information about OpenEmbedded, see the OpenEmbedded website: http://www.openembedded.org/
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
bitbake: Git repository: http://git.openembedded.org/bitbake/ Mailing list: bitbake-devel@lists.openembedded.org
documentation: Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/ Mailing list: yocto@yoctoproject.org
meta-poky, meta-yocto-bsp: Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto(-bsp) Mailing list: poky@yoctoproject.org
Everything else should be sent to the OpenEmbedded Core mailing list. If in doubt, check the oe-core git repository for the content you intend to modify. Before sending, be sure the patches apply cleanly to the current oe-core git repository.
Git repository: http://git.openembedded.org/openembedded-core/
Mailing list: openembedded-core@lists.openembedded.org
Note: The scripts directory should be treated with extra care as it is a mix of oe-core and poky-specific files.