4dc5ec21dc
Integrating the following mainline backports for better Broxton
support:
Adrian Hunter (3):
mmc: sdhci: Remove SDHCI_SDR104_NEEDS_TUNING
mmc: mmc: Attempt to flush cache before reset
mmc: mmc: Fix partition switch timeout for some eMMCs
Andy Shevchenko (12):
device property: always check for fwnode type
device property: rename helper functions
device property: refactor built-in properties support
device property: keep single value inplace
device property: improve readability of macros
device property: return -EINVAL when property isn't found in ACPI
device property: Fallback to secondary fwnode if primary misses the property
mfd: core: propagate device properties to sub devices drivers
mfd: intel-lpss: Pass HSUART configuration via properties
device property: avoid allocations of 0 length
lib/string: introduce match_string() helper
device property: convert to use match_string() helper
Bamvor Jian Zhang (1):
gpiolib: do not allow to insert an empty gpiochip
Christophe RICARD (2):
ACPI: Rename acpi_gsi_get_irq_type to acpi_dev_get_irq_type and export symbol
ACPI / gpio: Add irq_type when a GPIO is used as an interrupt
Dasaratharaman Chandramouli (1):
intel_idle: Support for Intel Xeon Phi Processor x200 Product Family
Gwendal Grignou (1):
mmc: core: Do regular power cycle when lacking eMMC HW reset support
Heikki Krogerus (4):
device property: helper macros for property entry creation
device property: the secondary fwnode needs to depend on the primary
device property: fwnode->secondary may contain ERR_PTR(-ENODEV)
device property: fix for a case of use-after-free
Len Brown (2):
intel_idle: Add SKX support
intel_idle: add BXT support
Linus Walleij (1):
Revert "gpio: revert get() to non-errorprogating behaviour"
Mika Westerberg (7):
pwm: lpss: Remove ->free() callback
pwm: lpss: Rework the sequence of programming PWM_SW_UPDATE
device property: Take a copy of the property set
driver core: platform: Add support for built-in device properties
mfd: intel-lpss: Add support for passing device properties
mfd: intel-lpss: Pass SDA hold time to I2C host controller driver
mfd: intel-lpss: Pass I2C configuration via properties on BXT
Qipeng Zha (1):
pinctrl: intel: make the high level interrupt working
Richard Cochran (10):
intel_idle: remove useless return from void function.
intel_idle: Fix a helper function's return value.
intel_idle: Remove redundant initialization calls.
intel_idle: Fix deallocation order on the driver exit path.
intel_idle: Fix dangling registration on error path.
intel_idle: Avoid a double free of the per-CPU data.
intel_idle: Setup the timer broadcast only on successful driver load.
intel_idle: Don't overreact to a cpuidle registration failure.
intel_idle: Propagate hot plug errors.
intel_idle: Clean up all registered devices on exit.
Wolfram Sang (1):
mmc: make MAN_BKOPS_EN message a debug
qipeng.zha (1):
pwm: lpss: Update PWM setting for Broxton
(From OE-Core rev: 232320c019240f90fd984a23e4d382cd7c3c018d)
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
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.