Importing a series of mainline backports to support USB on a couple of Intel platforms: b5f6aa9957dd usb: otg: add usb_otg_caps structure for otg capabilities bbce8fe2cc42 usb: dwc3: pci: add support for Intel Broxton SOC e734e1d9f827 usb: dwc3: pci: Set enblslpm quirk for Synopsys platforms 1c6bb6694d50 usb: dwc3: Add dis_enblslpm_quirk 1c6be99e56b8 usb: dwc3: pci: trivial: Formatting 2f2b89764b97 usb: dwc3: pci: passing forward the ACPI companion ea4b3c72d976 usb: dwc3: core: convert to unified device property interface dc670b52c69a usb: common: of_usb_get_dr_mode to usb_get_dr_mode 586fc5174649 usb: dwc3: st: prepare the driver for generic usb_get_dr_mode function 0624bd9af7ef usb: common: of_usb_get_maximum_speed to usb_get_maximum_speed e65bc5467e07 usb: dwc3: Add frame length adjustment quirk a90954c5d267 usb: musb: dsps: control musb speed based on dts setting b48ff160a993 usb: renesas_usbhs: Allow an OTG PHY driver to provide VBUS d1c59752195e usb: chipidea: set usb otg capabilities 733eada2cdec usb: common: add API to update usb otg capabilities by device tree 7ab2108dd82b usb: dwc3: core: avoid NULL pointer dereference 1aedb48b7dc9 usb: dwc3: add ULPI interface support 07e42a29fb7e usb: dwc3: pci: add quirk for Baytrails 065917252622 usb: dwc3: add hsphy_interface property b2bb32a363a3 usb: dwc3: setup phys earlier bf6bb0a6ebb5 usb: dwc3: soft reset to it's own function d481da949476 usb: dwc3: cache hwparams earlier 9ac66262a201 usb: dwc3: store driver data earlier 5f940588938c usb: dwc3: ULPI or UTMI+ select 04fdce097f83 usb: dwc3: USB2 PHY register access bits b7209213cc05 usb: add bus type for USB ULPI (From OE-Core rev: 46d173949675dde10b714f30b6f9c37c2e26a43a) 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.