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 <lauren.post@freescale.com>

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 <lauren.post@freescale.com>

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 <lauren.post@freescale.com>

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 <lauren.post@freescale.com>

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 <lauren.post@freescale.com>

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 <lauren.post@freescale.com>

Change-Id: Ibf044f87e090ebdbf303a3dedd0ddf74e621ab08
Signed-off-by: Lauren Post <lauren.post@freescale.com>

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 <fabio.estevam@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

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 <alfonso@mantic.mx>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

This merges the v3.12 final changes into patches-3.12 branch.

Change-Id: I4bd512f90da5814cbf06fc0a1baf08f2966f316d
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

The uapi files are inside kernel source and we shouldn't have extra
include paths here where it is not expected to be placed.

Change-Id: Ieab7fa0cdb3a92e921ac4268f4dbc4fc8b9b080f
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

This fixes the support for proper detecting Freescale specific headers
in include/linux and include/uapi.

Without this patch I have the configure log with the same feature in
'enabled' and 'disabled' state and it was impossible to proper
override CPPFLAGS.

After this patch, building it against MX53 I get:

Configure result:
        Enabled features:
                plugin: aac_dec
                plugin: mp3_dec
                plugin: vorbis_dec
                plugin: amr_dec
                plugin: mp3_enc
                plugin: h264_dec
                plugin: mpeg4_dec
                plugin: mpeg2_dec
                plugin: aiur
                plugin: beep
                plugin: v4lsink
                plugin: isink
                plugin: ipucsc
                library: libipu
                library: libX11
        Disabled features:
                plugin: aacp_dec
                plugin: wma10_dec
                plugin: ac3_dec
                plugin: wma8_enc
                plugin: downmix
                plugin: wmv9mp_dec
                plugin: wmv78_dec
                plugin: vpu_wrap

and building it against MX6Q I get:

Configure result:
        Enabled features:
                plugin: aac_dec
                plugin: mp3_dec
                plugin: vorbis_dec
                plugin: amr_dec
                plugin: mp3_enc
                plugin: h264_dec
                plugin: mpeg4_dec
                plugin: mpeg2_dec
                plugin: vpu_wrap
                plugin: aiur
                plugin: beep
                plugin: v4lsink
                plugin: isink
                plugin: ipucsc
                library: libipu
                library: libX11
        Disabled features:
                plugin: aacp_dec
                plugin: wma10_dec
                plugin: ac3_dec
                plugin: wma8_enc
                plugin: downmix
                plugin: wmv9mp_dec
                plugin: wmv78_dec

Change-Id: Icdd40a1686212275b67baede34bb45eb41be3cf1
Reported-by: Jānis Čoders <janis.coders@gmail.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

There're no reason to keep the directories split and we follow now how
done in OE-Core and Meta-OE putting it inside
recipes-multimedia/gstreamer/.

Change-Id: Ib6e6ba20880434d500334b6f4d2f48f367c773aa
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

This changes the gst-fsl-plugin.inc to include the 'uapi' into include
paths for kernels >= 3.10 and adds the need changes to proper build
for i.MX6 and i.MX6SL (which does not has VPU support).

Change-Id: I88d95390c966d37a52ec5b59aa4182c879e46444
Signed-off-by: Lauren Post <lauren.post@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

The special and excluded plugins require explicit runtime dependencies
so those are add throught PACKAGECONFIG.

Change-Id: I4c87f3ac9f3a9f8d7f5b0b57ebc0bf2e4960d30a
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

Released with 3.10.9-1.0.0_alpha release

Change-Id: I056e872cfdf52ae54c8ff8e4bce8fe08494a6534
Signed-off-by: Lauren Post <lauren.post@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

Released with 3.10.9-1.0.0_alpha

Change-Id: Ieb2aeb526d0bb8cda64449296ab247473e97b6c4
Signed-off-by: Lauren Post <lauren.post@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

Released with 3.10.9-1.0.0 release

Change-Id: I1fd4fd1e3eb7dad5196c58ccfa71501954ecae20
Signed-off-by: Lauren Post <lauren.post@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

The build system needs to allow override of CC and AR variables so OE
can pass proper flags for it; this includes a patch to allow it to
happen and fix builds in O.S. Systems autobuilder.

Change-Id: I974166244df3f743b21a00d705097602108449b2
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

The code in 3.10.9-1.0.0 version was duplicating the logic used in the
imx-vpu.inc so we removed this duplication.

Change-Id: Ie6fc0c5f1a43f7a3bc2b89c155e47b8fa5cdb1a7
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

Change-Id: Id9acfc1fd5a9d2754d94495716be7e6bde88b4eb
Signed-off-by: Prabhu Sundararaj <prabhu.sundararaj@freescale.com>

The goal here is to ensure we are able to use 3.10.9-1.0.0 BSP
packages and keep 3.0.35 kernel for boards that were not yet ported to
the 3.10-based kernel.

Change-Id: I4fa603d6bebad4e5712dcd1f8ec80a77c8487b12
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

This was previously part of imx-lib but separated starting in 3.0.35-4.1.0
because vpu is Freescale Proprietary license.

Note that libvpu was previously part of imx-lib but has been pulled out
because vpu is now Freescale Proprietary license

Change-Id: I3293b94ee3c3474d305c13c0c8c62480317713fc
Signed-off-by: Lauren Post <lauren.post@freescale.com>

imx-test includes exclusion for imx6 solo lite for vpu test cases
and inclusion on epdc test cases

Previous patches on imx-test have been applied to imx-test package

Update to handle 3.10 kernel uapi directory which has the mxc headers

Change-Id: Ifc98af6ca1c035879dba0ccb94ade5e0b276db03
Signed-off-by: Lauren Post <lauren.post@freescale.com>

This includes following main changes:

- imx-lib requires uapi header include for 3.10 kernel
- imx-lib no longer contains imx-vpu so all of imx-lib is LGPL
- libvpu is now in a separate component so eula-unpack inherit is not required

Also will not build libraries on mx6 only applicable to mx53

Previous kernels supported all the headers but 3.5.7 and 3.10.9
linux-imx do not inclue mx53 headers

Change-Id: Ia747ee6adf2c2e1a3425ae183ac9e3e0018c5a79
Signed-off-by: Lauren Post <lauren.post@freescale.com>

Enable CONFIG_FEC_NAPI option. This was disabled earlier as it was causing
a crash during boot, this issue has been fixed by commit: <ef3b62c1bab6f8>
ENGR00266268 net: fec: napi cause system crash
Signed-off-by: Mahesh Mahadevan <Mahesh.Mahadevan@freescale.com>

Update 2.6.35.3 maintain branch to commit 903363ed (ENGR00285435
Fix USB crash on MX53).

Change-Id: I66fa4fa4e01dd3dd3a47ceec9e6ebe435d608e65
Signed-off-by: Mahesh Mahadevan <Mahesh.Mahadevan@freescale.com>

This includes following commit:

commit 079e214888279518ce061c71238a74a0c3db2c28
Author: Fabio Estevam <fabio.estevam@freescale.com>
Date:   Mon Sep 30 13:16:52 2013 -0300

    ARM: mx5: Enable L2 cache

    Enable L2 cache for improving the system performance.
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>

Change-Id: I33c66775b42e46beff8868daeb46404541c2f387
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

All machine configurations now allow user override of the preferred
kernel provider.
Signed-off-by: Gary Thomas <gary@mlbassoc.com>

Signed-off-by: Gary Thomas <gary@mlbassoc.com>

Change-Id: Iae31c37b6c90d936123162d2ec24567e96f6c1b2
Signed-off-by: Lauren Post <lauren.post@freescale.com>

Hardware and software floating point packages updated; adds also a
runtime dependency against libgl-mesa-dev for libgl-mx6-dev.

Change-Id: Ic2c9bec2df8147e17d7299ddea0a7b077c0e2f69
Signed-off-by: Lauren Post <lauren.post@freescale.com>

Change-Id: Iaedeb955467d820717b200bfd85d61dd920ae79e
Signed-off-by: Lauren Post <lauren.post@freescale.com>

The kernel now needs to use GNU bc to be built since version 3.9. The following
commit message from the kernel explains the reason:

commit 70730bca1331fc50c3caacaea00439de1325bd6e
Author: H. Peter Anvin <hpa@zytor.com>
Date:   Thu Feb 14 15:13:55 2013 -0800

    kernel: Replace timeconst.pl with a bc script

    bc is the standard tool for multi-precision arithmetic.  We switched
    to Perl because akpm reported a hard-to-reproduce build hang, which
    was very odd because affected and unaffected machines were all running
    the same version of GNU bc.

    Unfortunately switching to Perl required a really ugly "canning"
    mechanism to support Perl < 5.8 installations lacking the Math::BigInt
    module.

    It was recently pointed out to me that some very old versions of GNU
    make had problems with pipes in subshells, which was indeed the
    construct used in the Makefile rules in that version of the patch;
    Perl didn't need it so switching to Perl fixed the problem for
    unrelated reasons.  With the problem (hopefully) root-caused, we can
    switch back to bc and do the arbitrary-precision arithmetic naturally.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
    Cc: Andrew Morton <akpm@linux-foundation.org>
Acked-by: Sam Ravnborg <sam@ravnborg.org>
Signed-off-by: Michal Marek <mmarek@suse.cz>

Change-Id: I09ec3629bf47aa4768bd21b0cfb1ca6fb6f5b18f
Signed-off-by: Lucas Dutra Nunes <ldnunes@ossystems.com.br>

libvpu was changed from imx-lib to imx-vpu so
now gst-fsl-plugins depends on both imx-lib
and imx-vpu.

imx-lib does provide libipu required by
gst-fsl-plugin

Change-Id: I623f5aec270f9c0bd19aefdfbf93e4e6222f8fd2
Signed-off-by: Daiane Angolini <daiane.angolini@freescale.com>

This includes following commit:

commit 3832258715cd19aa3e26ac5f35ef7be230454924
Author: Otavio Salvador <otavio@ossystems.com.br>
Date:   Tue Oct 29 15:00:24 2013 -0200

    mx6sabre{auto,sd}: Change FDT loading address to avoid overlaping

    The new FSL 3.10.9_1.0.0-alpha kernel requires more memory space and
    with the previous loading address we had ovelap; change it for the
    same address used in 2013.04-3.10.9_1.0.0-alpha U-Boot.
Tested-by: Daiane Angolini <daiane.angolini@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

Change-Id: I7bf08f962b7956ba6f4c645a1d3ed0188eb8ac0d
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

Change-Id: I53be94701187e7a7bdbfc371a3ba84d0d28ead39
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

Signed-off-by: Andy Voltz <andy.voltz@timesys.com>

FSL_EULA_FILE is defined with :=, which means it contains a full absolute path
to the layer directory. If this is allowed to make it into the task checksum,
it becomes impossible to use the shared states for these recipes without
having meta-fsl-arm in the exact same path in the filesystem it was in when
the sstate archives were created. Add FSL_EULA_FILE to
do_unpack[vardepsexclude].
Signed-off-by: Christopher Larson <kergoth@gmail.com>

When the buffer time is 512000, there are many audio
bitstreams can't be played, like 88.2k/6channles/16b
on sabre_SD and 96k/24b/6channels on sabre_auto.
Because ALSA can't calculate a suitable playback parameter
group (period_size, period_time, period_count, buffer_size,
buffer_count and so on) for these bitstreams.

So update the buffer time to 450000, which will fix the problem.

Change-Id: Idf2c59c3e5a2447f5d22e00d9f1b35ddb1a6fc4d
Signed-off-by: Wang Shengjiu  <B02247@freescale.com>
Signed-off-by: Daiane Angolini <daiane.angolini@freescale.com>