Backporting the following changes from the mainline kernel to enhance/add support for tpm2, pinctrl, powercap and watchdog: 634eecdb20b watchdog: omap_wdt: fix null pointer dereference 79dcc6dabe63 Watchdog: Fix parent of watchdog_devices 94a2e8f1d47e watchdog: st_wdt: Update IP layout information to include Clocksource 3a74938a9610 watchdog: st_wdt: Add new driver for ST's LPC Watchdog fb6b94faa82c watchdog: digicolor: driver for Conexant Digicolor CX92755 SoC 22fb7b1353dd watchdog: omap_wdt: early_enable module parameter aa70c2480483 watchdog: omap_wdt: implement get_timeleft 47b7a1a5f70f watchdog: docs: omap_wdt also understands nowayout 9d833b82f706 watchdog: omap: put struct watchdog_device into driver data 87ded7189286 watchdog: omap: use watchdog_init_timeout instead of open coding it abccc104fcad watchdog: da9062: DA9062 watchdog driver 95f8b1024989 pinctrl: intel: fix offset calculation issue of register PAD_OWN 8e6606474fa0 pinctrl: intel: fix bug of register offset calculation 2423468cb317 MAINTAINERS: add new maintainer for TPM DEVICE DRIVER cf94113f05a6 sysfs: added __compat_only_sysfs_link_entry_to_kobj() cdb63d5cd801 tpm: fix missing migratable flag in sealing functionality for TPM2 95f738feaafe keys, trusted: seal/unseal with TPM 2.0 chips 92eb9052fd50 tpm: seal/unseal for TPM 2.0 d9c7bb89ec85 keys, trusted: move struct trusted_key_options to trusted-type.h a3b394e91b31 tpm: introduce tpm_buf bd68d3a21139 tpm: move the PPI attributes to character device directory. 54fb01659b83 tpm, tpm_crb: fix unaligned read of the command buffer address 0ab522f5ef11 powercap / RAPL: disable the 2nd power limit properly 9ba8c36e9ea7 thermal/powerclamp: remove cpu whitelist 2971561c8fc9 thermal/powerclamp: add cpu id for Skylake u/y cec457da34d0 thermal/powerclamp: add cpu id for denlow platform fc30ea2abdc5 thermal/powerclamp: add cpu id for skylake h/s 3eea18356747 intel powerclamp: support Knights Landing (From OE-Core rev: ecb1fa6ed2366a031ba374d16d4ccbbd8b7fc7e6) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.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.