public inbox for openbmc@ozlabs.org
 help / color / mirror / Atom feed
From: Marc Olberding <molberding@nvidia.com>
To: Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: joel@jms.id.au, openbmc@lists.ozlabs.org
Subject: Re: [PATCH u-boot 1/2] Add a new board for the gigabyte msx4
Date: Tue, 25 Nov 2025 17:30:44 -0800	[thread overview]
Message-ID: <aSZYRPXSGcHImegq@molberding.nvidia.com> (raw)
In-Reply-To: <9e3bee690272f89ea0f25120c95f166065a3d888.camel@codeconstruct.com.au>

On Wed, Nov 26, 2025 at 11:00:33AM +1030, Andrew Jeffery wrote:
> On Fri, 2025-11-21 at 16:02 -0800, Marc Olberding wrote:
> > +}
> 
> Can we rather add support to the SPI driver, and disable it via a
> devicetree property?
> 
> That way the option is available to other platforms and minimises the
> spread of board file code.

I think that's reasonable, and I can put up a patchset for that.

are you okay with something like:
```
&fmc {
	status = "okay";
	fmc-wdt2-disable;
....
};
```

as the target config? or potentially drop the extra fmc...

For what its worth, WDT2 is actually disabled in the platform.S for the 2600
but its disabled by an #if 0 preproc directive. I think dealing with this in the driver
is a good idea and relatively low lift. In the response to the cover letter I had asked
for any ideas without reading this email :). I'll get this patch set up, thanks for the
feedback. 
> 
> What is the behavioural difference to what's in
> board/aspeed/ast2600_intel/intel.c? It's a little annoying to tell
> because intel.c uses macro symbols for the register offsets where
> you've open-coded the values here.
> 
> Can we try to make the implementation common?
> 
> Andrew

It's functionally the same, and to be honest this code is proliferated across
at least 3 board files. I can certainly make a helper function,
but I don't have access to test all of the boards. If you're happy with
it being "correct by inspection that it does the same thing" and "it builds",
I can move these board files over to using the common helper.

Thanks
Marc


  reply	other threads:[~2025-11-26  1:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-22  0:02 [PATCH u-boot 0/2] aspeed: Add support for msx4 Marc Olberding
2025-11-22  0:02 ` [PATCH u-boot 1/2] Add a new board for the gigabyte msx4 Marc Olberding
2025-11-26  0:30   ` Andrew Jeffery
2025-11-26  1:30     ` Marc Olberding [this message]
2025-12-01 23:14       ` Andrew Jeffery
2025-12-01 23:33         ` Marc Olberding
2025-12-01 23:43           ` Andrew Jeffery
2025-11-22  0:02 ` [PATCH u-boot 2/2] arch: arm: dts: Add dts for the nvidia msx4 board Marc Olberding
2025-11-26  0:22 ` [PATCH u-boot 0/2] aspeed: Add support for msx4 Andrew Jeffery
2025-11-26  1:20   ` Marc Olberding
2025-12-01 23:24     ` Andrew Jeffery

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=aSZYRPXSGcHImegq@molberding.nvidia.com \
    --to=molberding@nvidia.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.org \
    /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