| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
The SOC_FAMILY is an indirection which makes the understanding, from
OpenEmbedded versed developers and users, more difficult. Instead of
using the SOC_FAMILY indirection which is rarely used, we now move to
the MACHINEOVERRIDES mechanism as this is in fact what is in use.
Change-Id: Ic6e58b79bdc990ac853c87761c3fff635786e4e5
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
|
| |
Add Murata Type ZP (BCM4339) module support on below platforms:
- i.MX6Q/DL/QP SabreSD(SD2 slot) + Murata adapter V2.0
Note: MX6Q/DL/QP SabreSD board requires HW rework.
Please refer to rework guide specified in schematic.
Signed-off-by: Lauren Post <lauren.post@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
| |
Signed-off-by: Lauren Post <lauren.post@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
| |
Add uart5 DTE mode pinctrl set for imx6q-sabresd board becuase
of pin conflict.
Signed-off-by: Lauren Post <lauren.post@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Apply ENET IRQ workaround for sabresd board
This is pretty much an example to demonstrate how the GPIO6 workaround
for bug ERR006687 (ENET: Only the ENET wake-up interrupt request can
wake the system from Wait mode) should be applied for a board.
Basically it requires a setup of MX6QDL_PAD_GPIO_6__ENET_IRQ in pinctrl
entry, and an overwrite on the property interrupts-extended to replace
the ENET GIC IRQ with GPIO1_6.
Since the pad GPIO6 is used by I2C3 on the board, we have to create
sabresd-enetirq.dts with I2C3 disabled to enable this workaround.
Signed-off-by: Lauren Post <lauren.post@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
| |
This allow the mfgtool variant into the UBOOT_CONFIG set.
Change-Id: Ia96cffe65f0ce4a97c705a1c5dd69de2f6bfc5bd
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
| |
Change-Id: Iac335650f96510c4ce6178fa69be92f157d01f0a
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
| |
devices
Supported boot devices: sd and sata.
Change-Id: I66a3a5fcfa8624d1aba35003a873ba3a3bb1dcaf
Signed-off-by: Mario Domenech Goulart <mario@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The linux-dtb.inc has been reworked to use the Linux kernel build
system to generate the DeviceTree binaries so now KERNEL_DEVICETREE
variable should has the /target/ name, not the file path. This patch
reworks following machines:
- imx23evk
- imx28evk
- imx51evk
- imx53ard
- imx53qsb
- imx6dlsabreauto
- imx6dlsabresd
- imx6qsabreauto
- imx6qsabresd
- imx6solosabreauto
- imx6solosabresd
Change-Id: I37e9c3737552299677e315b6279a6e0a8e217836
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Freescale i.MX6 SABRE SD machines have some common
configuration. This file is used in order to avoid
duplicating in all SABRE SD boards.
Replace any 'include' to 'require' to make sure an
error is launched in case the file is missing.
Change-Id: Ic50956c49a35c2e4f0af6c21e7495cce42698b56
Signed-off-by: Daiane Angolini <daiane.angolini@freescale.com>
|
| |
|
|
|
|
|
|
|
|
| |
Include vendor name to machine name
Fix machine name
Include SOC
Fix description
Change-Id: Idb7dffba9fac08290ac465684b5dc080b058791d
Signed-off-by: Daiane Angolini <daiane.angolini@freescale.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
The SOC_FAMILY uses the MACHINEOVERRIDES and it evaluates from left to
right. In this case, the most SoC specific value needs to be kept in
the right so it take precedence.
This has been catch when finding out why i.MX6SL EVK where using the
wrong value as entry point, and this was the root cause.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
| |
Change-Id: I3afbbe9acc2fe91bbbb2caf246cfb781e030e2d5
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
| |
Change-Id: I952910e3d6d96a78acbeacad31cbf1034f31cce5
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
|
Change-Id: I548d97f785ab05099d290b10121963feb2952c8b
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Acked-by: Daiane Angolini <daiane.angolini@freescale.com>
|
