61e077e998
Updating to include the following commits:
a4d0c407cced dmaengine: dw: don't handle interrupt when dmaengine is not used
e92b2ce791b2 dmaengine: dw: define DW_DMA_MAX_NR_MASTERS
931304a6567e dmaengine: dw: provide DMA capabilities
468bad4f7a6f dmaengine: dw: Split device_control
b4afd7710db7 i2c: i801: Use managed pcim_* PCI device initialization and reservation
d81a8a11ecba i2c: i801: Remove pci_enable_device() call from i801_resume()
40e18604e70c i2c: i801: Use managed devm_* memory and irq allocation
b54f65dbe57b i2c: i801: Remove i801_driver forward declaration
e95740d4d079 i2c: i801: Don't break user-visible strings
423e98721e04 ACPI: Introduce has_acpi_companion()
291f620dc052 i2c: designware: Suppress error message if platform_get_irq() < 0
cf5ff51a8e3f i2c: designware-pci: no need to provide clk_khz
4f583ce420d3 i2c: designware-pci: remove Moorestown support
e000c549c9d8 i2c: designware: Add Intel Baytrail PMIC I2C bus support
7ffbd9ca19a7 i2c: designware: fixup return handling of wait_for_completion_timeout
5758d5a1df32 i2c: designware: Do not calculate SCL timing parameters needlessly
2f58fcae92db i2c: designware: Add i2c bus locking support
84a73e51e900 i2c: designware: use {readl|writel}_relaxed instead of readl/writel
f672bb8424e6 serial: 8250_dw: Fix get_mctrl behaviour
91bd64585489 serial: 8250: add support for ACPI-probed serial port for X-Gene platform
1190cba71f09 serial:8250:8250_pci: delete unneeded quirk entries
6405a4b71451 serial:8250:8250_pci: fix redundant entry report for WCH_CH352_2S
0a1a31bbbc19 serial: 8250_pci: remove one useless explicit type conversion
4edc52a55f82 intel_idle: Add support for the Airmont Core in the Cherrytrail and Braswell SOCs
934f85e8bfdb x86/irq, ACPI: Implement ACPI driver to support IOAPIC hotplug
c6a3440252a8 ACPI / LPSS: check the result of ioremap()
6aacc0c931b7 pinctrl: update direction_output function of cherryview driver
cb4a43a2177d pinctrl: cherryview: Configure HiZ pins to be input when requested as GPIOs
0df22c007ce1 pinctrl: intel: drop owner assignment from platform_drivers
07b16f04700b pinctrl: cherryview: Save and restore pin configs over system sleep
e8e5cfffa231 pinctrl: baytrail: Save pin context over system sleep
04cb3cc0ff21 pinctrl: baytrail: Rework interrupt handling
4cac25d2574d pinctrl: baytrail: Clear interrupt triggering from pins that are in GPIO mode
eacab9ab234a pinctrl: baytrail: Relax GPIO request rules
(From OE-Core rev: d2dd36bafdef7b0424041f5369706b9152ea13da)
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-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.