Hello, I pushed following updates:
commit 362c55a3a251e0ef8df2a0069a2396d208121288 Author: Lauren Post <[email protected]> Date: Tue Oct 1 11:36:52 2013 -0500 imx6solosabresd.conf: Add ldo device tree ENGR00277895: dts: ARM: imx6: add ldo-enable dts files Currently, we use different dts files to support ldo-bypass or ldo-enable, then we need add both dts files for the boards which can support ldo-bypass mode(all boards support ldo-enable at least). So for below boards we need add ldo-enable dts file so that we can use this to easily support ldo-enable mode: 1)mx6q-sabresd board: ldo-bypass dts->mx6q-sabresd.dtb, ldo-enable dts->mx6q-sabresd-ldo.dtb 2)mx6q-sabresd board: ldo-bypass dts->mx6dl-sabresd.dtb, ldo-enable dts->mx6dl-sabresd-ldo.dtb 3)mx6sl-evk board: ldo-bypass dts->mx6sl-evk.dtb, ldo-enable dts->mx6sl-evk-ldo.dtb Change-Id: I261c516495e3921fb1c2d8937d96fb6e3a23e87b Signed-off-by: Lauren Post <[email protected]> commit b9596cd34ef8edec93430a4454062e22609fcc9e Author: Lauren Post <[email protected]> Date: Tue Oct 1 11:35:29 2013 -0500 imx6slevk.conf: Add ldo device tree ENGR00277895: dts: ARM: imx6: add ldo-enable dts files Currently, we use different dts files to support ldo-bypass or ldo-enable, then we need add both dts files for the boards which can support ldo-bypass mode(all boards support ldo-enable at least). So for below boards we need add ldo-enable dts file so that we can use this to easily support ldo-enable mode: 1)mx6q-sabresd board: ldo-bypass dts->mx6q-sabresd.dtb, ldo-enable dts->mx6q-sabresd-ldo.dtb 2)mx6q-sabresd board: ldo-bypass dts->mx6dl-sabresd.dtb, ldo-enable dts->mx6dl-sabresd-ldo.dtb 3)mx6sl-evk board: ldo-bypass dts->mx6sl-evk.dtb, ldo-enable dts->mx6sl-evk-ldo.dtb Change-Id: I997bf896a3d3fde482fe9c120a92c16d49817adb Signed-off-by: Lauren Post <[email protected]> commit c4940e8b73dd4c3e9012e280a44ed6614ef2ec24 Author: Lauren Post <[email protected]> Date: Tue Oct 1 11:34:35 2013 -0500 imx6qsabresd.conf: Add ldo and hdcp DTS ENGR00274059-02 ARM: Add new dts for imx6q/imx6dl SabreSD hdcp hdcp ddc pins conflict with i2c2, add new dts file for imx6q and imx6dl SabreSD board, enable hdcp and disable i2c2 in these dts files. Remove hdmi pins property from mx6qdl-sabresd.dtsi. ENGR00279402-1 ARM: dts: imx6: add wdog reset source seclect in dts Some boards use another WDOG reset source to reboot system in ldo-bypass mode. We need add the property in board dts file so that we can easily know the WDOG reset source currently. For Sabresd, WDOG1 for ldo-enable mode(WDOG event), WDOG2 for ldo-bypass mode (reset external pmic to trigger POR event). For sl-evk board, there is no WDOG pin connected with external pmic as Sabresd , because mx6sl boot at 400Mhz. Then both ldo-enable and ldo-bypass mode use the common WDOG1 as reset source. ENGR00277895: dts: ARM: imx6: add ldo-enable dts files Currently, we use different dts files to support ldo-bypass or ldo-enable, then we need add both dts files for the boards which can support ldo-bypass mode(all boards support ldo-enable at least). So for below boards we need add ldo-enable dts file so that we can use this to easily support ldo-enable mode: 1)mx6q-sabresd board: ldo-bypass dts->mx6q-sabresd.dtb, ldo-enable dts->mx6q-sabresd-ldo.dtb 2)mx6q-sabresd board: ldo-bypass dts->mx6dl-sabresd.dtb, ldo-enable dts->mx6dl-sabresd-ldo.dtb 3)mx6sl-evk board: ldo-bypass dts->mx6sl-evk.dtb, ldo-enable dts->mx6sl-evk-ldo.dtb Change-Id: I38fb55249a002888c9da2c5e298acca089759876 Signed-off-by: Lauren Post <[email protected]> commit 6113055031f7708945aabaa0482f4631b1576218 Author: Lauren Post <[email protected]> Date: Tue Oct 1 11:31:52 2013 -0500 imx6qsabreauto.conf: Add gpmi-weim DTS ENGR00269945: ARM: imx6: add the secondary sabreauto dts for pin conflict The patch is to solve the pin conflicts between devices that are currently added in imx6qdl-sabreauto dts file. It has ecspi1, i2c3, and uart3 enabled while gpmi and weim disabled in the primary imx6qdl-sabreauto.dtsi, and creates the secondary imx6q/dl-sabreauto dts to have gpmi and weim enabled while others disabled. Since usbh1 and usbotg depend on GPIO from max7310 on i2c3, they have to be disabled as well in the secondary sabreauto dts files. Change-Id: I6338e60fa8c1622b2a73e99aa1e3def0a2555bc2 Signed-off-by: Lauren Post <[email protected]> commit e6286b977bf410b6527b950c4d34470c2c9e3e1b Author: Lauren Post <[email protected]> Date: Tue Oct 1 11:30:30 2013 -0500 imx6dlsabresd.conf: Add in ldo and hdcp DTS ENGR00274059-02 ARM: Add new dts for imx6q/imx6dl SabreSD hdcp hdcp ddc pins conflict with i2c2, add new dts file for imx6q and imx6dl SabreSD board, enable hdcp and disable i2c2 in these dts files. Remove hdmi pins property from mx6qdl-sabresd.dtsi. ENGR00279402-1 ARM: dts: imx6: add wdog reset source seclect in dts Some boards use another WDOG reset source to reboot system in ldo-bypass mode. We need add the property in board dts file so that we can easily know the WDOG reset source currently. For Sabresd, WDOG1 for ldo-enable mode(WDOG event), WDOG2 for ldo-bypass mode (reset external pmic to trigger POR event). For sl-evk board, there is no WDOG pin connected with external pmic as Sabresd , because mx6sl boot at 400Mhz. Then both ldo-enable and ldo-bypass mode use the common WDOG1 as reset source. ENGR00277895: dts: ARM: imx6: add ldo-enable dts files Currently, we use different dts files to support ldo-bypass or ldo-enable, then we need add both dts files for the boards which can support ldo-bypass mode(all boards support ldo-enable at least). So for below boards we need add ldo-enable dts file so that we can use this to easily support ldo-enable mode: 1)mx6q-sabresd board: ldo-bypass dts->mx6q-sabresd.dtb, ldo-enable dts->mx6q-sabresd-ldo.dtb 2)mx6q-sabresd board: ldo-bypass dts->mx6dl-sabresd.dtb, ldo-enable dts->mx6dl-sabresd-ldo.dtb 3)mx6sl-evk board: ldo-bypass dts->mx6sl-evk.dtb, ldo-enable dts->mx6sl-evk-ldo.dtb Change-Id: I8a5863d135e5c72419c1eb8f4f34483c2397e567 Signed-off-by: Lauren Post <[email protected]> commit 6097d786073999d100a60b1600e20e99563a2e9a Author: Lauren Post <[email protected]> Date: Tue Oct 1 11:29:20 2013 -0500 imxdlsabreauto.conf: Add gpmi-weim DTS ENGR00269945: ARM: imx6: add the secondary sabreauto dts for pin conflict The patch is to solve the pin conflicts between devices that are currently added in imx6qdl-sabreauto dts file. It has ecspi1, i2c3, and uart3 enabled while gpmi and weim disabled in the primary imx6qdl-sabreauto.dtsi, and creates the secondary imx6q/dl-sabreauto dts to have gpmi and weim enabled while others disabled. Since usbh1 and usbotg depend on GPIO from max7310 on i2c3, they have to be disabled as well in the secondary sabreauto dts files. Change-Id: I1f51cda59468140a2552a73fca5d710ecde1967e Signed-off-by: Lauren Post <[email protected]> commit 068a234a1699046c8e7ad59b1566d0293b6dd5c8 Author: Lauren Post <[email protected]> Date: Tue Oct 1 11:56:42 2013 -0500 linux-imx: Upgrade 3.5.7-1.0.0_alpha to 3.10.9-1.0.0_alpha kernel The new dependency against 'bc-native' is due used of it during kernel build and has been introduced in 3.9 kernel. Change-Id: I399007e92bb6ff401faf4c7544a924d990cc19cd Signed-off-by: Lauren Post <[email protected]> commit 9e4d8136306a112c9e153b7e774cd3af9175be23 Author: Lauren Post <[email protected]> Date: Tue Oct 1 12:00:37 2013 -0500 u-boot-imx (2013.04): Update 3.10.9-1.0.0 alpha Change-Id: Ibf044f87e090ebdbf303a3dedd0ddf74e621ab08 Signed-off-by: Lauren Post <[email protected]> commit e7acf6e409204ed5a622ae454df19e514f22e458 Author: Otavio Salvador <[email protected]> Date: Tue Nov 12 21:55:13 2013 -0200 linux-fslc: Update to revision 928c8b1 This fixes MX23 NULL pointer derreference when probing NAND chips. The commit which fixes the issue is: 928c8b1 mtd: gpmi: fix the NULL pointer Change-Id: I9f7b54900aed8bad164fd134f8a9c90b93dc0418 Reported-by: Fabio Estevam <[email protected]> Signed-off-by: Otavio Salvador <[email protected]> commit 3f2f08fe88a1a5da2d726402b77381c7311f8e74 Author: Otavio Salvador <[email protected]> Date: Tue Nov 12 16:13:57 2013 -0200 fsl-default-providers.inc: Make virtual/kernel assigment delayed In 01851da (machine/*: Allow kernel provider override) the assigment of preferred provider for virtual/kernel has been changed to a weak assignment. This works for most of cases but has caused a regression in some machines. When a machine includes the imx-base.inc file, the assignment is done and the intended setting of the machine does not take effect. For example, in the below code fragment: ,----[ Wandboard board configuration fragment ] | include conf/machine/include/imx-base.inc | ... | PREFERRED_PROVIDER_virtual/kernel ?= "linux-wandboard" `---- the virtual/kernel provider would be 'linux-imx' as, at the time of imx-base.inc inclusion, it was undefined. The expected behaviour would be to use 'linux-imx' /only/ when no setting has been done. The ??= operator solves this as it is used /only/ if no assignment is done to the virtual/kernel provider in the end of the parsing. So it gives the expected behaviour. Change-Id: Iab73dcff8bef7f2df1064a0d5d04fd506a4c3144 Reported-by: Alfonso Tamés <[email protected]> Signed-off-by: Otavio Salvador <[email protected]> Regards, -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
