From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 184D4E00C89; Mon, 18 Sep 2017 11:03:37 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, HTML_MESSAGE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [198.47.19.16 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from fllnx209.ext.ti.com (fllnx209.ext.ti.com [198.47.19.16]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 87C9FE00C89 for ; Mon, 18 Sep 2017 11:03:35 -0700 (PDT) Received: from dflxv15.itg.ti.com ([128.247.5.124]) by fllnx209.ext.ti.com (8.15.1/8.15.1) with ESMTP id v8II3O7p008249 for ; Mon, 18 Sep 2017 13:03:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ti.com; s=ti-com-17Q1; t=1505757804; bh=GlH1F5uFpgHIU07gI4xUpI6vMP80Pjl6hztNvbDqLks=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=HUjvU1AFuZfW5wUhwEyjUqlfgIiiaWK33g65JwK2rOgve0u6x1MyZ60kKiNKMPFpF ttOOyerz6fHIC/ZeG5p3Gf/kr6d5zPTp7l57crFS4YnJMKDwBE0aQPPlYOmG2MhaD3 2KkmgDIvbi1sEECdn3keFtyHbnVcQSH8SE2BTCEs= Received: from DLEE70.ent.ti.com (dlee70.ent.ti.com [157.170.170.113]) by dflxv15.itg.ti.com (8.14.3/8.13.8) with ESMTP id v8II3JoT016884 for ; Mon, 18 Sep 2017 13:03:19 -0500 Received: from DFLE12.ent.ti.com ([fe80::e9a3:bf19:af96:227b]) by DLEE70.ent.ti.com ([fe80::c4c6:f618:54e7:ad11%28]) with mapi id 14.03.0294.000; Mon, 18 Sep 2017 13:03:19 -0500 From: "Radhakrishnan, Mahesh" To: "Dmytriyenko, Denys" Thread-Topic: [meta-ti] [PATCH v2 25/37] pm-lld-rtos: Adding rtos recipe for pm-lld Thread-Index: AQHTABo/4dA9rIaZ80qoj7DcuKpQZ6KUeIKAgCbWZKA= Date: Mon, 18 Sep 2017 18:03:18 +0000 Message-ID: <5130E41A1BA9D145BA0F3B18D5CFB0A7437F42A1@DFLE12.ent.ti.com> References: <1500419028-3361-1-git-send-email-m-radhakrishnan2@ti.com> <1500419028-3361-25-git-send-email-m-radhakrishnan2@ti.com> <20170824195159.GH28233@edge> In-Reply-To: <20170824195159.GH28233@edge> Accept-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.172.224.221] MIME-Version: 1.0 Cc: "meta-ti@yoctoproject.org" Subject: Re: [PATCH v2 25/37] pm-lld-rtos: Adding rtos recipe for pm-lld X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2017 18:03:37 -0000 X-Groupsio-MsgNum: 10372 Content-Language: en-US Content-Type: multipart/mixed; boundary="_004_5130E41A1BA9D145BA0F3B18D5CFB0A7437F42A1DFLE12entticom_" --_004_5130E41A1BA9D145BA0F3B18D5CFB0A7437F42A1DFLE12entticom_ Content-Type: multipart/alternative; boundary="_000_5130E41A1BA9D145BA0F3B18D5CFB0A7437F42A1DFLE12entticom_" --_000_5130E41A1BA9D145BA0F3B18D5CFB0A7437F42A1DFLE12entticom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Denys, Submitted a new patch for pm-lld (attached). Responses linline. Please let me know if it looks okay now. Regards Mahesh -----Original Message----- From: Dmytriyenko, Denys Sent: Thursday, August 24, 2017 3:52 PM To: Radhakrishnan, Mahesh Cc: meta-ti@yoctoproject.org Subject: Re: [meta-ti] [PATCH v2 25/37] pm-lld-rtos: Adding rtos recipe for= pm-lld On Tue, Jul 18, 2017 at 07:03:36PM -0400, Mahesh Radhakrishnan wrote: > Upstreaming TI RTOS low level driver for Power Management module (PM) > Signed-off-by: Mahesh Radhakrishnan > > --- > > v2 - Added summary & merged in to a single recipe > > recipes-bsp/pm-lld/pm-lld-rtos_git.bb | 95 > +++++++++++++++++++++++++++++++++++ > 1 file changed, 95 insertions(+) > create mode 100644 recipes-bsp/pm-lld/pm-lld-rtos_git.bb > > diff --git a/recipes-bsp/pm-lld/pm-lld-rtos_git.bb > b/recipes-bsp/pm-lld/pm-lld-rtos_git.bb > new file mode 100644 > index 0000000..c976deb > --- /dev/null > +++ b/recipes-bsp/pm-lld/pm-lld-rtos_git.bb > @@ -0,0 +1,95 @@ > +SUMMARY =3D "TI RTOS driver for Power Management module (PM)" > + > +require recipes-ti/includes/ti-paths.inc > + > +LICENSE =3D "BSD-3-Clause" > +LIC_FILES_CHKSUM =3D "file://Power.h;beginline=3D1;endline=3D31;md5=3D52= 7b91fdcd26cd19ac07a754f45dedbe" > + > +COMPATIBLE_MACHINE =3D "ti33x|ti43x|omap-a15|k2g" > +PACKAGE_ARCH =3D "${MACHINE_ARCH}" > + > + > +PM_LLD_GIT_URI =3D "git://git.ti.com/keystone-rtos/pm-lld.git" > +PM_LLD_GIT_PROTOCOL =3D "git" > +PM_LLD_GIT_BRANCH =3D "int_pm_am335x" > +PM_LLD_GIT_BRANCH_dra7xx-evm =3D "master" ^^^ > +PM_LLD_GIT_DESTSUFFIX =3D "git/ti/drv/pm" > + > +# Below commit ID corresponds to "DEV.PM_LLD.01.04.00.01" > +PM_LLD_SRCREV =3D "c4908f94b3e655e6298aa9bfe9bbffbbc5d16111" > + > +# Below commit ID corresponds to "REL.PDK.TDA.01.07.00.06" > +PM_LLD_SRCREV_dra7xx-evm =3D "46ea13503d2991f636197edb206a9f62cea398d4" ^^^ In some places here you use more generic "omap-a15" SOC family, but in thes= e 2 places I highlighted, you use very specific "dra7xx-evm", which will ex= clude platforms like "dra7xx-hs-evm" as well as "am57xx-evm" and use "int_p= m_am335x" branch for those. Please confirm you actually want to do that. Yes. I have confirmed with automotive team that we use specific versions fo= r dra7xx-evm. This module is not used for dra7xx-hs-evm. > + > +BRANCH =3D "${PM_LLD_GIT_BRANCH}" > +SRC_URI =3D "${PM_LLD_GIT_URI};destsuffix=3D${PM_LLD_GIT_DESTSUFFIX};pro= tocol=3D${PM_LLD_GIT_PROTOCOL};branch=3D${BRANCH}" > + > +#PATCHTOOL =3D "git" > +#SRC_URI_append =3D " \ > +# file://.patch \ > +#" Leftovers ^^^ Yes. They have been removed in the latest patch. > +SRCREV =3D "${PM_LLD_SRCREV}" > +PV =3D "01.04.00.01" > +PR =3D "r0" > + > +S =3D "${WORKDIR}/${PM_LLD_GIT_DESTSUFFIX}" > + > +DEPENDS =3D " ti-sysbios \ > + gcc-arm-none-eabi-native \ > + osal-rtos \ > + ca-certificates-native \ > + ti-pdk-setup \ > +" > +DEPENDS_append_omap-a15 =3D " ti-cgt-arm-native \ > + ti-cgt6x-native \ > + common-csl-ip-rtos \ " > +DEPENDS_append_ti33x =3D " starterware-rtos \ " > +DEPENDS_append_ti43x =3D " starterware-rtos \ " > +DEPENDS_append_k2g =3D " common-csl-ip-rtos \ > + ti-cgt6x-native \ " > + > +# Fetch task cannot be completed until after ca-certificates-native > +populates sysroot with the SSL certificates do_fetch[depends] =3D "ca-ce= rtificates-native:do_populate_sysroot" Why? Shouldn't be a problem accessing git.ti.com over git protocol. Yes. They have been removed in the latest patch. > +export TOOLCHAIN_PATH_A15 =3D "${GCC_ARM_NONE_TOOLCHAIN}" > +export TOOLCHAIN_PATH_A8 =3D "${GCC_ARM_NONE_TOOLCHAIN}" > +export TOOLCHAIN_PATH_A9 =3D "${GCC_ARM_NONE_TOOLCHAIN}" > +export FPULIB_PATH =3D "${GCC_ARM_NONE_TOOLCHAIN}/lib/gcc/arm-none-eabi/= 4.9.3/fpu/" > +export TOOLCHAIN_PATH_M4 =3D "${M4_TOOLCHAIN_INSTALL_DIR}" > +export C6X_GEN_INSTALL_PATH =3D "${STAGING_DIR_NATIVE}/usr/share/ti/cgt-= c6x" > +export PDK_INSTALL_PATH =3D "${PDK_INSTALL_DIR}/packages" > +export BIOS_INSTALL_PATH =3D "${SYSBIOS_INSTALL_DIR}" > +export XDC_INSTALL_PATH =3D "${XDC_INSTALL_DIR}" Aren't those already defined in a .inc file? In the latest patch submitted, ti-pdk.bbclass has been used and the above a= re removed. > +export PDK_PM_ROOT_PATH =3D "${WORKDIR}/git" > + > +# Used by DEST_ROOT to redirect binary and obj files away from > +sysroot PDK tree OBJ_DIR =3D "${WORKDIR}/git/ti/binary" > + > +do_compile() { > + make clean lib xdc_meta doxygen LIMIT_SOCS=3D"${TI_PDK_LIMIT_SOCS}" > +LIMIT_BOARDS=3D"${TI_PDK_LIMIT_BOARDS}" DEST_ROOT=3D${OBJ_DIR} BTW, doxygen is not available in meta-ti nor in the only other dependent la= yer which is oe-core. The doxygen target is no longer built with the latest patch. > + # Remove unnecessary files from packaging > + rm -rf patches/ > + > + # Cleanup docs > + rm -rf docs/ReleaseNotes_PM_LLD.doc > + rm -rf internal/ > + > + #archive > + tar -cf pm_lld.tar --exclude=3D'*.tar' ./* > +} > + > +do_install() { > + install -d ${D}${PDK_INSTALL_DIR_RECIPE}/packages/ti/drv/pm > + find -name "*.tar" -exec tar xf {} --no-same-owner -C ${D}${PDK_INST= ALL_DIR_RECIPE}/packages/ti/drv/pm \; Is it necessary to tar-up everything at the end of do_compile and then un-t= ar in do_install? The latest patch uses ti-pdk.bbclass and the do_Compile has been appended b= y generating a tar file which the do_install of ti-pdk.bbclass will unta= r. > +} > + > +FILES_${PN} +=3D "${PDK_INSTALL_DIR_RECIPE}/packages" > + > +INSANE_SKIP_${PN} =3D "arch staticdev" > -- > 1.9.1 > > -- > _______________________________________________ > meta-ti mailing list > meta-ti@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-ti --_000_5130E41A1BA9D145BA0F3B18D5CFB0A7437F42A1DFLE12entticom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Denys,

Submitted a new pat= ch for pm-lld (attached). Responses linline.

Please let me know if it looks okay now.

 

Regards<= /span>

Mahesh

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Thursday, August 24, 2017 3:52 PM
To: Radhakrishnan, Mahesh
Cc: meta-ti@yoctoproject.org
Subject: Re: [meta-ti] [PATCH v2 25/37] pm-lld-rtos: Adding rtos recipe for= pm-lld

 

On Tue, Jul 18, 2017 at 07:03:36PM -0400, Mahesh = Radhakrishnan wrote:

> Upstreaming TI RTOS low level driver for Pow= er Management module (PM)

> Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>

> ---

>

> v2 - Added summary & merged in to a sing= le recipe

>

>  recipes-bsp/pm-lld/pm-lld-rtos_git.bb = | 95

> +++++++++= ;+++++++++++++++= ;+++++++++++

>  1 file changed, 95 insertions(+)

>  create mode 100644 recipes-bsp/pm-lld/= pm-lld-rtos_git.bb

>

> diff --git a/recipes-bsp/pm-lld/pm-lld-rtos_= git.bb

> b/recipes-bsp/pm-lld/pm-lld-rtos_git.bb=

> new file mode 100644

> index 0000000..c976deb

> --- /dev/null

> +++ b/recipes-bsp/pm-lld/pm-lld-= rtos_git.bb

> @@ -0,0 +1,95 @@

> +SUMMARY =3D "TI RTOS driver for Po= wer Management module (PM)"

> +

> +require recipes-ti/includes/ti-paths.in= c

> +

> +LICENSE =3D "BSD-3-Clause"

> +LIC_FILES_CHKSUM =3D "file://Power= .h;beginline=3D1;endline=3D31;md5=3D527b91fdcd26cd19ac07a754f45dedbe= "

> +

> +COMPATIBLE_MACHINE =3D "ti33x|ti43= x|omap-a15|k2g"

> +PACKAGE_ARCH =3D "${MACHINE_ARCH}&= quot;

> +

> +

> +PM_LLD_GIT_URI =3D "git://git.ti.c= om/keystone-rtos/pm-lld.git"

> +PM_LLD_GIT_PROTOCOL =3D "git"=

> +PM_LLD_GIT_BRANCH =3D "int_pm_am33= 5x"

> +PM_LLD_GIT_BRANCH_dra7xx-evm =3D "= master"

 

^^^

 

 

> +PM_LLD_GIT_DESTSUFFIX =3D "git/ti/= drv/pm"

> +

> +# Below commit ID corresponds to "= DEV.PM_LLD.01.04.00.01"

> +PM_LLD_SRCREV =3D "c4908f94b3e655e= 6298aa9bfe9bbffbbc5d16111"

> +

> +# Below commit ID corresponds to "= REL.PDK.TDA.01.07.00.06"

> +PM_LLD_SRCREV_dra7xx-evm =3D "46ea= 13503d2991f636197edb206a9f62cea398d4"

 

^^^

 

In some places here you use more generic "om= ap-a15" SOC family, but in these 2 places I highlighted, you use very = specific "dra7xx-evm", which will exclude platforms like "dr= a7xx-hs-evm" as well as "am57xx-evm" and use "int_pm_am= 335x"

branch for those. Please confirm you actually wan= t to do that.

Yes. I have confirm= ed with automotive team that we use specific versions for dra7xx-evm. This = module is not used for dra7xx-hs-evm.

 

> +

> +BRANCH =3D "${PM_LLD_GIT_BRANCH}&q= uot;

> +SRC_URI =3D "${PM_LLD_GIT_URI};des= tsuffix=3D${PM_LLD_GIT_DESTSUFFIX};protocol=3D${PM_LLD_GIT_PROTOCOL};branch= =3D${BRANCH}"

> +

> +#PATCHTOOL =3D "git"

> +#SRC_URI_append =3D " \=

> +#    file://.pat= ch \

> +#"

 

Leftovers ^^^

Yes. They have been= removed in the latest patch.

 

 

> +SRCREV =3D "${PM_LLD_SRCREV}"=

> +PV =3D "01.04.00.01"

> +PR =3D "r0"

> +

> +S =3D "${WORKDIR}/${PM_LLD_GIT_DES= TSUFFIX}"

> +

> +DEPENDS =3D " ti-sysbios \

> +      &nb= sp;     gcc-arm-none-eabi-native \

> +      &nb= sp;     osal-rtos \

> +      &nb= sp;     ca-certificates-native \

> +      &nb= sp;     ti-pdk-setup \

> +"

> +DEPENDS_append_omap-a15 =3D " ti-c= gt-arm-native \

> +      &nb= sp;            =          ti-cgt6x-native \

> +      &nb= sp;            =          common-csl-ip-rtos \ "= ;

> +DEPENDS_append_ti33x =3D " starter= ware-rtos \ "

> +DEPENDS_append_ti43x =3D " starter= ware-rtos \ "

> +DEPENDS_append_k2g =3D " common-cs= l-ip-rtos \

> +      &nb= sp;            =     ti-cgt6x-native \ "

> +

> +# Fetch task cannot be completed until = after ca-certificates-native

> +populates sysroot with the SSL certific= ates do_fetch[depends] =3D "ca-certificates-native:do_populate_sysroot= "

 

Why? Shouldn't be a problem accessing git.ti.com = over git protocol.

Yes. They have been= removed in the latest patch.

 

 

> +export TOOLCHAIN_PATH_A15 =3D "${G= CC_ARM_NONE_TOOLCHAIN}"

> +export TOOLCHAIN_PATH_A8 =3D "${GC= C_ARM_NONE_TOOLCHAIN}"

> +export TOOLCHAIN_PATH_A9 =3D "${GC= C_ARM_NONE_TOOLCHAIN}"

> +export FPULIB_PATH =3D "${GCC_ARM_= NONE_TOOLCHAIN}/lib/gcc/arm-none-eabi/4.9.3/fpu/"

> +export TOOLCHAIN_PATH_M4 =3D "${M4= _TOOLCHAIN_INSTALL_DIR}"

> +export C6X_GEN_INSTALL_PATH =3D "$= {STAGING_DIR_NATIVE}/usr/share/ti/cgt-c6x"

> +export PDK_INSTALL_PATH =3D "${PDK= _INSTALL_DIR}/packages"

> +export BIOS_INSTALL_PATH =3D "${SY= SBIOS_INSTALL_DIR}"

> +export XDC_INSTALL_PATH =3D "${XDC= _INSTALL_DIR}"

 

Aren't those already defined in a .inc file?=

In the latest patch= submitted, ti-pdk.bbclass has been used and the above are removed.

 

> +export PDK_PM_ROOT_PATH =3D "${WOR= KDIR}/git"

> +

> +# Used by DEST_ROOT to redirect binary = and obj files away from

> +sysroot PDK tree OBJ_DIR =3D "${WO= RKDIR}/git/ti/binary"

> +

> +do_compile() {

> +    make clean lib xdc_m= eta doxygen LIMIT_SOCS=3D"${TI_PDK_LIMIT_SOCS}"

> +LIMIT_BOARDS=3D"${TI_PDK_LIMIT_BOA= RDS}" DEST_ROOT=3D${OBJ_DIR}

 

BTW, doxygen is not available in meta-ti nor in t= he only other dependent layer which is oe-core.

The doxygen target = is no longer built with the latest patch.

 

> +    # Remove unnecessary= files from packaging

> +    rm -rf patches/=

> +

> +    # Cleanup docs<= /o:p>

> +    rm -rf docs/ReleaseN= otes_PM_LLD.doc

> +    rm -rf internal/

> +

> +    #archive<= /p>

> +    tar -cf pm_lld.tar -= -exclude=3D'*.tar' ./*

> +}

> +

> +do_install() {

> +    install -d ${D}${PDK= _INSTALL_DIR_RECIPE}/packages/ti/drv/pm

> +    find -name "*.t= ar" -exec tar xf {} --no-same-owner -C ${D}${PDK_INSTALL_DIR_RECIPE}/p= ackages/ti/drv/pm \;

 

Is it necessary to tar-up everything at the end o= f do_compile and then un-tar

in do_install?

 

The latest patch us= es ti-pdk.bbclass and the do_Compile has been appended by generating a tar = file    which the do_install of ti-pdk.bbclass will untar.

> +}

> +

> +FILES_${PN} +=3D "${PDK_INSTAL= L_DIR_RECIPE}/packages"

> +

> +INSANE_SKIP_${PN} =3D "arch static= dev"

> --

> 1.9.1

>

> --

> ____________________________________________= ___

> meta-ti mailing list

> = meta-ti@yoctoproject.= org

> https://lists.yoctopr= oject.org/listinfo/meta-ti

--_000_5130E41A1BA9D145BA0F3B18D5CFB0A7437F42A1DFLE12entticom_-- --_004_5130E41A1BA9D145BA0F3B18D5CFB0A7437F42A1DFLE12entticom_ Content-Type: message/rfc822 Content-Disposition: attachment; creation-date="Mon, 18 Sep 2017 18:03:18 GMT"; modification-date="Mon, 18 Sep 2017 18:03:18 GMT" Received: from DFLE103.ent.ti.com (10.64.6.24) by DLEE70.ent.ti.com (157.170.170.113) with Microsoft SMTP Server (TLS) id 14.3.294.0; Mon, 18 Sep 2017 12:54:32 -0500 Received: from DFLE108.ent.ti.com (10.64.6.29) by DFLE103.ent.ti.com (10.64.6.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.845.34; Mon, 18 Sep 2017 12:54:32 -0500 Received: from dflp33.itg.ti.com (10.64.6.16) by DFLE108.ent.ti.com (10.64.6.29) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.845.34 via Frontend Transport; Mon, 18 Sep 2017 12:54:32 -0500 Received: from uda0875154a.am.dhcp.ti.com (ileax41-snat.itg.ti.com [10.172.224.153]) by dflp33.itg.ti.com (8.14.3/8.13.8) with ESMTP id v8IHsWeb012844; Mon, 18 Sep 2017 12:54:32 -0500 From: "Radhakrishnan, Mahesh" To: "meta-ti@yoctoproject.org" CC: "Radhakrishnan, Mahesh" Subject: [PATCH v4] pm-lld-rtos: Adding rtos recipe for pm-lld Thread-Topic: [PATCH v4] pm-lld-rtos: Adding rtos recipe for pm-lld Thread-Index: AQHTMKcuRYaJYc9W/UitrntDyLPAnw== Date: Mon, 18 Sep 2017 17:54:28 +0000 Message-ID: <1505757268-4687-1-git-send-email-m-radhakrishnan2@ti.com> Content-Language: en-US X-MS-Exchange-Organization-AuthMechanism: 10 X-MS-Exchange-Organization-AuthSource: DFLE108.ent.ti.com X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 TI RTOS low level driver for Power Management module (PM) Signed-off-by: Mahesh Radhakrishnan --- v4 - Modified to use ti-pdk.bbclass and addressed review comments v3 - Removed the intermediate tar-untar for install v2 - Added summary & merged in to a single recipe recipes-bsp/pm-lld/pm-lld-rtos_git.bb | 56 +++++++++++++++++++++++++++++++= ++++ 1 file changed, 56 insertions(+) create mode 100644 recipes-bsp/pm-lld/pm-lld-rtos_git.bb diff --git a/recipes-bsp/pm-lld/pm-lld-rtos_git.bb b/recipes-bsp/pm-lld/pm-= lld-rtos_git.bb new file mode 100644 index 0000000..6fedc80 --- /dev/null +++ b/recipes-bsp/pm-lld/pm-lld-rtos_git.bb @@ -0,0 +1,56 @@ +SUMMARY =3D "TI RTOS driver for Power Management module (PM)" + +require recipes-ti/includes/ti-paths.inc +inherit ti-pdk + +LICENSE =3D "BSD-3-Clause" +LIC_FILES_CHKSUM =3D "file://Power.h;beginline=3D1;endline=3D31;md5=3D527b= 91fdcd26cd19ac07a754f45dedbe" + +COMPATIBLE_MACHINE =3D "ti33x|ti43x|omap-a15|k2g" +PACKAGE_ARCH =3D "${MACHINE_ARCH}" + + +PM_LLD_GIT_URI =3D "git://git.ti.com/keystone-rtos/pm-lld.git" +PM_LLD_GIT_PROTOCOL =3D "git" +PM_LLD_GIT_BRANCH =3D "int_pm_am335x" +PM_LLD_GIT_BRANCH_dra7xx-evm =3D "master" +PM_LLD_GIT_DESTSUFFIX =3D "git/ti/drv/pm" + +# Below commit ID corresponds to "DEV.PM_LLD.01.04.00.01" +PM_LLD_SRCREV =3D "c4908f94b3e655e6298aa9bfe9bbffbbc5d16111" + +# Below commit ID corresponds to "REL.PDK.TDA.01.07.00.06" +PM_LLD_SRCREV_dra7xx-evm =3D "46ea13503d2991f636197edb206a9f62cea398d4" + +BRANCH =3D "${PM_LLD_GIT_BRANCH}" +SRC_URI =3D "${PM_LLD_GIT_URI};destsuffix=3D${PM_LLD_GIT_DESTSUFFIX};proto= col=3D${PM_LLD_GIT_PROTOCOL};branch=3D${BRANCH}" + +SRCREV =3D "${PM_LLD_SRCREV}" +PV =3D "01.04.00.01" +PR =3D "r0" + +S =3D "${WORKDIR}/${PM_LLD_GIT_DESTSUFFIX}" + +DEPENDS_append =3D " ti-sysbios \ + osal-rtos \ +" +DEPENDS_append_ti33x =3D " starterware-rtos \ +" +DEPENDS_append_ti43x =3D " starterware-rtos \ +" +export PDK_PM_ROOT_PATH =3D "${WORKDIR}/build" +export DEST_ROOT=3D"${S}" + +# Build with make instead of XDC +TI_PDK_XDCMAKE =3D "0" + +do_compile_append() { + # Delete archive created by XDC release command since it does not cont= ain all content + find -name "*.tar" -exec rm -f {} \; + + # Archive from build/ to capture ti/drv/pm/ in archive + cd ${B} + tar -cf pm_lld.tar --exclude=3D'*.tar' ./* +} + +INSANE_SKIP_${PN} =3D "arch staticdev" -- 1.9.1 --_004_5130E41A1BA9D145BA0F3B18D5CFB0A7437F42A1DFLE12entticom_--