meta-freescale.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: "Val Kondratenko" <valeriy.kondratenko@jci.com>
To: Val Kondratenko <valeriy.kondratenko@jci.com>,
	Fabio Estevam <festevam@gmail.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>,
	"meta-freescale@lists.yoctoproject.org"
	<meta-freescale@lists.yoctoproject.org>
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?
Date: Fri, 25 Jun 2021 18:28:24 +0000	[thread overview]
Message-ID: <BN6P132MB00686CEEE2013B74A81E1AFAE1069@BN6P132MB0068.NAMP132.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <168BE6901ABD95ED.20408@lists.yoctoproject.org>

Oops, sorry for duplicate (ignore), meant to send to someone else.

And thanks (again) for quick response,

 Val

-----Original Message-----
From: meta-freescale@lists.yoctoproject.org <meta-freescale@lists.yoctoproject.org> On Behalf Of Val Kondratenko via lists.yoctoproject.org
Sent: Friday, June 25, 2021 1:54 PM
To: Val Kondratenko <valeriy.kondratenko@jci.com>; Fabio Estevam <festevam@gmail.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

Is the following a recommended upstream u-boot?

u-boot-v2021.04 from
https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsource.denx.de%2Fu-boot%2Fu-boot%2F&amp;data=04%7C01%7Cvaleriy.kondratenko%40jci.com%7C9d81ccfd81c14c0c3f5c08d93806c619%7Ca1f1e2147ded45b681a19e8ae3459641%7C0%7C0%7C637602424008919863%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=W7VRDmOAXNwxGNXX4kRgOvSij%2BOFq6k5I%2Fy%2FaBVnpiA%3D&amp;reserved=0

The cpuidle functionality would be in?

arch/arm/mach-imx/mx7/psci-mx7.c

From when/which release U-boot started support cpuidle?

Is there any documentation on how to move the cpuidle functionality from kernel to u-boot?
What is involved there?

Thanks in advance,
 Val

-----Original Message-----
From: meta-freescale@lists.yoctoproject.org <meta-freescale@lists.yoctoproject.org> On Behalf Of Val Kondratenko via lists.yoctoproject.org
Sent: Friday, June 11, 2021 11:12 AM
To: Fabio Estevam <festevam@gmail.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

One other thing I see missing in 5.12, that was in freeescale 5.4, is the rpmsg (Remote Processor Messaging) functionality.

Thanks again!!!
 Val

-----Original Message-----
From: Fabio Estevam <festevam@gmail.com> 
Sent: Thursday, June 10, 2021 5:12 PM
To: Val Kondratenko <valeriy.kondratenko@jci.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

On Thu, Jun 10, 2021 at 5:19 PM Val Kondratenko <valeriy.kondratenko@jci.com> wrote:
>
> OK thanks.
>
> Next question - does it have full support for imx7d?

Yes, imx7d is well supported in the mainline kernel.

> I noticed (as I am attempting to apply patches we use), that /arch/arm/mach-imx/cpuidle-imx7d.c exists in the 5.4.X.imx version we are currently using, but is not present in 5.12.  But mach-imx7d.c is.
>  Will I have to add files (via patches) to fully support imx7d?

cpuidle is supported via PSCI implementation in U-Boot.

I suggest you to use U-Boot mainline too.

  parent reply	other threads:[~2021-06-25 18:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 12:34 Safe to upgrade to a Community BSP? Val Kondratenko
2021-06-10 19:43 ` [meta-freescale] " Otavio Salvador
2021-06-10 20:18   ` Val Kondratenko
2021-06-10 21:11     ` Fabio Estevam
2021-06-11 15:12       ` Val Kondratenko
2021-06-11 16:19         ` Fabio Estevam
2021-06-11 16:42           ` Val Kondratenko
2021-07-09 19:22           ` Val Kondratenko
2021-06-23 17:48       ` Val Kondratenko
2021-06-23 20:05         ` Fabio Estevam
     [not found]       ` <16878FD7EE6FE05F.27948@lists.yoctoproject.org>
2021-06-25 17:53         ` Val Kondratenko
2021-06-25 18:11           ` Fabio Estevam
2021-06-29 20:03             ` Val Kondratenko
2021-07-06 14:29               ` Val Kondratenko
     [not found]         ` <168BE6901ABD95ED.20408@lists.yoctoproject.org>
2021-06-25 18:28           ` Val Kondratenko [this message]
2021-07-09 19:08   ` Val Kondratenko
2021-06-10 20:14 ` Fabio Estevam
2021-06-10 20:21   ` Val Kondratenko
2021-07-07 11:48 ` Val Kondratenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BN6P132MB00686CEEE2013B74A81E1AFAE1069@BN6P132MB0068.NAMP132.PROD.OUTLOOK.COM \
    --to=valeriy.kondratenko@jci.com \
    --cc=festevam@gmail.com \
    --cc=meta-freescale@lists.yoctoproject.org \
    --cc=otavio.salvador@ossystems.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).