a256628ea0
To enable Apollo Lake/Broxton, we backport the following changes: da451824f75f i2c: designware: Convert to use unified device property API 58b1b5365f4a i2c: designware: Do not require clock when SSCN and FFCN are provided 8995091cfa0f i2c: designware: retry transfer on transient failure 1fc62907f84e i2c: designware: Move common probe code into i2c_dw_probe() 678110c0f2b8 i2c: designware: Rename platform driver probe and PM functions c51c2e104d40 i2c: designware: Make dw_readl() and dw_writel() static 98d2b6e244ad i2c: designware: Remove unused functions 3d04c6e99652 i2c: designware: Disable interrupts before requesting PCI device interrupt fb5b7be0fbe7 i2c: designware: Remove interrupt clearing from i2c_dw_pci_probe() d48fd08b11c8 i2c: designware: Make debug print in i2c_dw_isr() shorter 28f94bc07450 i2c: designware-pci: use IRQF_COND_SUSPEND flag 95f494846fc1 i2c: designware: Avoid unnecessary resuming during system suspend fb2ae3705a3a i2c: dw: Add APM X-Gene ACPI I2C device support 516a0fc91e00 i2c: designware: Add support for AMD Seattle I2C 874d63b3c95c i2c: designware: fix IO timeout issue for AMD controller 47543e80c6dd i2c: designware: reverts "i2c: designware: Add support for AMD I2C controller" 076fe383c4b5 i2c: designware: use to_pci_dev() (From OE-Core rev: 7b4b8a2481ce256e35fb86ebdeb944ee29ad5231) 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.