From: Denys Dmytriyenko <denis@denix.org>
To: rs@ti.com
Cc: reatmon@ti.com, denys@ti.com, meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti] [dunfell][PATCH v2] ti-img-rogue-driver: AM62 Active power management
Date: Wed, 11 Jan 2023 17:33:49 -0500 [thread overview]
Message-ID: <20230111223349.GV22689@denix.org> (raw)
In-Reply-To: <20230111221434.2399898-1-rs@ti.com>
On Wed, Jan 11, 2023 at 04:14:34PM -0600, Randolph Sapp via lists.yoctoproject.org wrote:
> Bump source revision. Changelog from source:
> - Cleanup the device initialization routine for all platforms
> - Add a power safeguard for multicore initialization
> - Enable active power management for AM62 devices
>
> v2: This revision actually uses the correct commit hash. Not sure where
> I got the old one from.
Thanks, but patch revision changes are usually listed after the --- cut line
below to not get into the commit log history.
> Signed-off-by: Randolph Sapp <rs@ti.com>
> ---
Here.
> recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.15.6133109.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.15.6133109.bb b/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.15.6133109.bb
> index 94a7f220..9a5bc479 100644
> --- a/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.15.6133109.bb
> +++ b/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.15.6133109.bb
> @@ -26,7 +26,7 @@ SRC_URI = " \
>
> S = "${WORKDIR}/git"
>
> -SRCREV = "c901804e8221d477983a6f7224a9cdc6e832f050"
> +SRCREV = "1dd6291a5cad4f2b909fc2a14bd717a3bc5f0bb2"
>
> TARGET_PRODUCT_j7-evm = "j721e_linux"
> TARGET_PRODUCT_j7-hs-evm = "j721e_linux"
> --
> 2.34.1
next prev parent reply other threads:[~2023-01-11 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 22:14 [dunfell][PATCH v2] ti-img-rogue-driver: AM62 Active power management Randolph Sapp
2023-01-11 22:33 ` Denys Dmytriyenko [this message]
2023-01-11 23:34 ` [EXTERNAL] Re: [meta-ti] " Sapp, Randolph
2023-01-11 23:42 ` Ryan Eatmon
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=20230111223349.GV22689@denix.org \
--to=denis@denix.org \
--cc=denys@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@ti.com \
--cc=rs@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.