mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Shiyan <eagle.alexander923@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: SAMA5D3-xplained board cleanup question
Date: Mon, 23 Jun 2025 11:31:02 +0200	[thread overview]
Message-ID: <aFke1jEhe1ICGEmG@pengutronix.de> (raw)
In-Reply-To: <CAP1tNvRTbyB7NXoaLOid9-7jH5Jxfa5MB6LGVfyZYwc7y+Sq_w@mail.gmail.com>

Hi Alexander,

On Fri, Jun 20, 2025 at 03:21:56PM +0300, Alexander Shiyan wrote:
> Hello All!
> 
>  I would like to propose a cleanup for the SAMA5D3-xplained board support.
> The board currently has code in board.c that configures the
> at91sam9-smc (Static Memory Controller).
> However, since the board uses devicetree, this configuration should be
> handled by the MFD driver
> that is responsible for the SMC and is devicetree-based.
> 
> Therefore, I think we can remove the SMC configuration from the board file.
> But I don't have a SAMA5D3-xplained board to test this change.
> 
> Could someone who has access to this board please test the removal of
> the SMC configuration?

It's rather unlikely that someone gives a positive answer here.
I'd say just send the patch and add a note that it's untested.

That said, we @Pengutronix should have such a board, at least I can find
it in our inventory list. Not sure if I can motivate someone to connect
it for me.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2025-06-23 10:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20 12:21 Alexander Shiyan
2025-06-23  9:31 ` Sascha Hauer [this message]
2025-06-23 10:16   ` Ahmad Fatoum
2025-06-24  9:14     ` Alexander Shiyan

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=aFke1jEhe1ICGEmG@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=eagle.alexander923@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox