public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: Chris Packham <judge.packham@gmail.com>, u-boot@lists.denx.de
Cc: "Baruch Siach" <baruch@tkos.co.il>,
	"Chris Packham" <chris.packham@alliedtelesis.co.nz>,
	"Kostya Porotchkin" <Kostya.Porotchkin@cavium.com>,
	"Marek Behún" <marek.behun@nic.cz>,
	"Moti Buskila" <motib@marvell.com>,
	"Nadav Haklai" <Nadav.Haklai@cavium.com>,
	"Tom Rini" <trini@konsulko.com>
Subject: Re: [PATCH] ARM: mvebu: x530: clearfog: Add ODT configuration
Date: Fri, 4 Mar 2022 08:29:07 +0100	[thread overview]
Message-ID: <fe75dc78-85c0-9df5-e322-bd4850a3fb03@denx.de> (raw)
In-Reply-To: <20220301005323.1786382-1-judge.packham@gmail.com>

On 3/1/22 01:53, Chris Packham wrote:
> Commit 369e532691e0 ("ddr: marvell: a38x: allow board specific ODT
> configuration") added the odt_config member to struct
> mv_ddr_topology_map ahead of the clk_enable and ck_delay members. This
> means that any boards that configured either of clk_enable or ck_delay
> needed to have their board topology updated. This affects the x530 and
> clearfog boards. Other A38x boards don't touch any of the trailing
> members of mv_ddr_topology_map so don't need updating.
> 
> Fixes: 369e532691e0 ("ddr: marvell: a38x: allow board specific ODT configuration")
> Signed-off-by: Chris Packham <judge.packham@gmail.com>

Reviewed-by: Stefan Roese <sr@denx.de>

Thanks,
Stefan

> ---
> 
>   board/alliedtelesis/x530/x530.c    | 1 +
>   board/solidrun/clearfog/clearfog.c | 1 +
>   2 files changed, 2 insertions(+)
> 
> diff --git a/board/alliedtelesis/x530/x530.c b/board/alliedtelesis/x530/x530.c
> index 8b31045a0743..c0ec2afa3011 100644
> --- a/board/alliedtelesis/x530/x530.c
> +++ b/board/alliedtelesis/x530/x530.c
> @@ -73,6 +73,7 @@ static struct mv_ddr_topology_map board_topology_map = {
>   	{0},				/* timing parameters */
>   	{ {0} },			/* electrical configuration */
>   	{0},				/* electrical parameters */
> +	0,				/* ODT configuration */
>   	0,				/* Clock enable mask */
>   	160				/* Clock delay */
>   };
> diff --git a/board/solidrun/clearfog/clearfog.c b/board/solidrun/clearfog/clearfog.c
> index c920cf8d6b50..03adb591d826 100644
> --- a/board/solidrun/clearfog/clearfog.c
> +++ b/board/solidrun/clearfog/clearfog.c
> @@ -147,6 +147,7 @@ static struct mv_ddr_topology_map board_topology_map = {
>   	{0},				/* timing parameters */
>   	{ {0} },			/* electrical configuration */
>   	{0,},				/* electrical parameters */
> +	0,				/* ODT configuration */
>   	0x3,				/* clock enable mask */
>   };
>   

Viele Grüße,
Stefan Roese

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-51 Fax: (+49)-8142-66989-80 Email: sr@denx.de

  parent reply	other threads:[~2022-03-04  7:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01  0:53 [PATCH] ARM: mvebu: x530: clearfog: Add ODT configuration Chris Packham
2022-03-01  5:21 ` Baruch Siach
2022-03-04  7:29 ` Stefan Roese [this message]
2022-03-04 12:23 ` Stefan Roese

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=fe75dc78-85c0-9df5-e322-bd4850a3fb03@denx.de \
    --to=sr@denx.de \
    --cc=Kostya.Porotchkin@cavium.com \
    --cc=Nadav.Haklai@cavium.com \
    --cc=baruch@tkos.co.il \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=judge.packham@gmail.com \
    --cc=marek.behun@nic.cz \
    --cc=motib@marvell.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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