All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: Suman Anna <s-anna@ti.com>
Cc: Lokesh Vutla <lokeshvutla@ti.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,  <u-boot@lists.denx.de>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Praneeth Bajjuri <praneeth@ti.com>,
	Grygorii Strashko <grygorii.strashko@ti.com>
Subject: Re: [PATCH] board: ti: k2g: Program PadConfig_202 before locking RSTMUX8
Date: Thu, 29 Jul 2021 10:44:31 +0530	[thread overview]
Message-ID: <162753558687.21966.14043207878604351394.b4-ty@ti.com> (raw)
In-Reply-To: <20210726232248.24395-1-s-anna@ti.com>

On Mon, 26 Jul 2021 18:22:48 -0500, Suman Anna wrote:
> The PADCONFIG_202 register (0x02621328) is affected by the locking
> of the RSTMUX8 register (0x02620328), and so cannot be configured
> in kernel. This has been confirmed as a hardware bug and affects
> all K2G SoCs.
> 
> Setup the pinmux for this pin before locking the RSTMUX8 register
> to allow the ICSS1 PRU1 Ethernet PHY port to work properly. The
> workaround was added only for the K2G-ICE board to configure the
> pins needed for the PRUSS Ethernet usecase.
 
Applied to https://source.denx.de/u-boot/custodians/u-boot-ti.git for-rc, thanks!
[1/1] board: ti: k2g: Program PadConfig_202 before locking RSTMUX8
      https://source.denx.de/u-boot/custodians/u-boot-ti/-/commit/a6c64d255e
 
--
Thanks and Regards,
Lokesh

      reply	other threads:[~2021-07-29  5:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26 23:22 [PATCH] board: ti: k2g: Program PadConfig_202 before locking RSTMUX8 Suman Anna
2021-07-29  5:14 ` Lokesh Vutla [this message]

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=162753558687.21966.14043207878604351394.b4-ty@ti.com \
    --to=lokeshvutla@ti.com \
    --cc=grygorii.strashko@ti.com \
    --cc=kishon@ti.com \
    --cc=praneeth@ti.com \
    --cc=s-anna@ti.com \
    --cc=u-boot@lists.denx.de \
    --cc=vigneshr@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.