Patchwork imx6qsabresd.conf: Add ldo and hdcp DTS - Breaks linux-fslc

login
register
mail settings
Submitter Lewis, Nick
Date Nov. 29, 2013, 3:22 p.m.
Message ID <AAE0766F5AF36B46BAB7E0EFB92732063131CC1113@GBTWK10E001.Technology.local>
Download mbox | patch
Permalink /patch/62623/
State Not Applicable
Delegated to: Otavio Salvador
Headers show

Comments

Lewis, Nick - Nov. 29, 2013, 3:22 p.m.
Otavio

This change appears to break linux-fslc

Best Regards
Nick

Nick Lewis
nick.lewis@usa.g4s.com
+44 1684 277137
www.g4stechnology.com
New Challenge House, International Drive, Tewkesbury, Gloucestershire, GL20 8UQ, UK

? Please consider the environment before printing this email

-----Original Message-----
From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-bounces@yoctoproject.org] On Behalf Of Otavio Salvador

Sent: 13 November 2013 00:01
To: meta-freescale Mailing List
Subject: [meta-freescale] [meta-fsl-arm][PATCH 08/10] imx6qsabresd.conf: Add ldo and hdcp DTS

From: 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>

---
 conf/machine/imx6qsabresd.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--
1.8.4.rc3

_______________________________________________
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


This company is part of the G4S group of companies. This communication contains information which may be confidential, personal and/or privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, forwarding, copying or use of this communication or the information in it is strictly prohibited. Any personal views expressed in this e-mail are those of the individual sender and the Company does not endorse or accept responsibility for them. Prior to taking any action based upon this e-mail message, you should seek appropriate confirmation of its authenticity. This message has been checked for viruses on behalf of the Company.



The details of this company are as follows:
G4S Technology Limited, Registered Office: Challenge House, International Drive, Tewkesbury, Gloucestershire GL20 8UQ, Registered in England No. 2382338.

This communication may contain information which is confidential, personal and/or privileged.

It is for the exclusive use of the intended recipient(s).
If you are not the intended recipient(s), please note that any distribution, forwarding, copying or use of this communication or the information in it is strictly prohibited.

Any personal views expressed in this e-mail are those of the individual sender and the company does not endorse or accept responsibility for them.

Prior to taking any action based upon this e-mail message, you should seek appropriate confirmation of its authenticity.

This e-mail has been scanned for all viruses by MessageLabs.
Otavio Salvador - Nov. 30, 2013, 4:49 p.m.
Hello Nick,

On Fri, Nov 29, 2013 at 1:22 PM, Lewis, Nick <nick.lewis@usa.g4s.com> wrote:
> This change appears to break linux-fslc

I know; however we cannot support both at same time (well, not yet) as
Yocto does not have a way to be aware of which kernel support which
DTB files. So for now, people will need to live with this :-(
Lewis, Nick - Dec. 2, 2013, 10:19 a.m.
>> This change appears to break linux-fslc
>
> I know; however we cannot support both at same time (well, not yet)
> as Yocto does not have a way to be aware of which kernel support
> which DTB files. So for now, people will need to live with this :-(

Otavio

I added a conf/machine/imx6qsabresd.conf file that is suitable for linux-fslc to a client layer that has higher priority but the conf/machine/imx6qsabresd.conf in meta-fsl-arm is still used instead. Is this a bug in bitbake or have I overlooked something?

--
Nick

The details of this company are as follows:
G4S Technology Limited, Registered Office: Challenge House, International Drive, Tewkesbury, Gloucestershire GL20 8UQ, Registered in England No. 2382338.

This communication may contain information which is confidential, personal and/or privileged.

It is for the exclusive use of the intended recipient(s).
If you are not the intended recipient(s), please note that any distribution, forwarding, copying or use of this communication or the information in it is strictly prohibited.

Any personal views expressed in this e-mail are those of the individual sender and the company does not endorse or accept responsibility for them.

Prior to taking any action based upon this e-mail message, you should seek appropriate confirmation of its authenticity.

This e-mail has been scanned for all viruses by MessageLabs.
Otavio Salvador - Dec. 2, 2013, 12:16 p.m.
On Mon, Dec 2, 2013 at 8:19 AM, Lewis, Nick <nick.lewis@usa.g4s.com> wrote:
>>> This change appears to break linux-fslc
>>
>> I know; however we cannot support both at same time (well, not yet)
>> as Yocto does not have a way to be aware of which kernel support
>> which DTB files. So for now, people will need to live with this :-(
>
> Otavio
>
> I added a conf/machine/imx6qsabresd.conf file that is suitable for linux-fslc to a client layer that has higher priority but the conf/machine/imx6qsabresd.conf in meta-fsl-arm is still used instead. Is this a bug in bitbake or have I overlooked something?

The machine files respect the order in bblayers.conf file.
Lauren Post - Dec. 3, 2013, 4:33 p.m.
I'm curious can we just add these new dtb files as patches for the linux-fslc recipe to apply to avoid the build issue?

We do have a few more dtb files coming in the beta release (not as many though) so this will happen again.  

Lauren

-----Original Message-----
From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-bounces@yoctoproject.org] On Behalf Of Otavio Salvador
Sent: Monday, December 02, 2013 6:17 AM
To: Lewis, Nick
Cc: meta-freescale@yoctoproject.org; meta-fsl-arm@yoctoproject.org
Subject: Re: [meta-freescale] imx6qsabresd.conf: Add ldo and hdcp DTS - Breaks linux-fslc

On Mon, Dec 2, 2013 at 8:19 AM, Lewis, Nick <nick.lewis@usa.g4s.com> wrote:
>>> This change appears to break linux-fslc
>>
>> I know; however we cannot support both at same time (well, not yet) 
>> as Yocto does not have a way to be aware of which kernel support 
>> which DTB files. So for now, people will need to live with this :-(
>
> Otavio
>
> I added a conf/machine/imx6qsabresd.conf file that is suitable for linux-fslc to a client layer that has higher priority but the conf/machine/imx6qsabresd.conf in meta-fsl-arm is still used instead. Is this a bug in bitbake or have I overlooked something?

The machine files respect the order in bblayers.conf file.

Patch

diff --git a/conf/machine/imx6qsabresd.conf b/conf/machine/imx6qsabresd.conf index f0eff4a..ccac357 100644

--- a/conf/machine/imx6qsabresd.conf

+++ b/conf/machine/imx6qsabresd.conf

@@ -7,7 +7,7 @@  require conf/machine/include/imx6sabresd-common.inc


 SOC_FAMILY = "mx6:mx6q"

-KERNEL_DEVICETREE = "imx6q-sabresd.dtb"

+KERNEL_DEVICETREE = "imx6q-sabresd.dtb imx6q-sabresd-ldo.dtb imx6q-sabresd-hdcp.dtb"


 UBOOT_CONFIG ??= "sd"
 UBOOT_CONFIG[sd] = "mx6qsabresd_config,sdcard"