public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ralph Siemsen <ralph.siemsen@linaro.org>
To: Marek Vasut <marek.vasut@mailbox.org>
Cc: u-boot@lists.denx.de, Chris Packham <judge.packham@gmail.com>
Subject: Re: [PATCH v5 08/10] board: schneider: add RZN1 board support
Date: Fri, 12 May 2023 16:12:42 -0400	[thread overview]
Message-ID: <20230512201242.GA2295717@maple.netwinder.org> (raw)
In-Reply-To: <20230509132102.GB3431193@maple.netwinder.org>

On Tue, May 09, 2023 at 09:21:02AM -0400, Ralph Siemsen wrote:
>On Tue, May 09, 2023 at 04:26:57AM +0200, Marek Vasut wrote:
>>On 5/8/23 20:23, Ralph Siemsen wrote:
>>>I moved it to board-specific directory as an interim step. 
>>>Hopefully we can do some consolidation of the multiple CDNS DDR 
>>>controller implementations, and then figure out the right way to 
>>>split things up.
>>>
>>>For now this seemed like the less-bad option.
>>
>>How about putting it into drivers/soc/ ?
>
>Possibly, although it would complicate things for me right now. I have 
>some (as yet unfinished) patches to handle the RZ/N1 variants using 
>drivers/soc.

As discussed on IRC, it is now moved into drivers/ram/renesas/rzn1

Ralph

  reply	other threads:[~2023-05-12 20:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24  1:15 [PATCH v5 00/10] Renesas RZ/N1 SoC initial support Ralph Siemsen
2023-04-24  1:15 ` [PATCH v5 01/10] ARM: armv7: add non-SPL enable for Cortex SMPEN Ralph Siemsen
2023-04-24  1:15 ` [PATCH v5 02/10] clk: renesas: prepare for non R-Car clock drivers Ralph Siemsen
2023-05-07 15:51   ` Marek Vasut
2023-04-24  1:15 ` [PATCH v5 03/10] clk: renesas: add R906G032 driver Ralph Siemsen
2023-05-07 15:53   ` Marek Vasut
2023-04-24  1:15 ` [PATCH v5 04/10] pinctrl: " Ralph Siemsen
2023-04-24  1:15 ` [PATCH v5 05/10] ram: cadence: add driver for Cadence EDAC Ralph Siemsen
2023-05-07 16:12   ` Marek Vasut
2023-04-24  1:15 ` [PATCH v5 06/10] ARM: dts: add devicetree for Renesas RZ/N1 SoC Ralph Siemsen
2023-05-07 15:54   ` Marek Vasut
2023-04-24  1:15 ` [PATCH v5 07/10] ARM: rmobile: Add support " Ralph Siemsen
2023-05-07 15:57   ` Marek Vasut
2023-04-24  1:15 ` [PATCH v5 08/10] board: schneider: add RZN1 board support Ralph Siemsen
2023-05-07 16:06   ` Marek Vasut
2023-05-08 18:23     ` Ralph Siemsen
2023-05-09  2:26       ` Marek Vasut
2023-05-09 13:21         ` Ralph Siemsen
2023-05-12 20:12           ` Ralph Siemsen [this message]
2023-04-24  1:15 ` [PATCH v5 09/10] tools: spkgimage: add Renesas SPKG format Ralph Siemsen
2023-05-07 16:08   ` Marek Vasut
2023-05-08 17:50     ` Ralph Siemsen
2023-05-09  2:25       ` Marek Vasut
2023-05-09 13:07         ` Ralph Siemsen
2023-05-09 14:52           ` Marek Vasut
2023-05-09 15:42             ` Ralph Siemsen
2023-05-12 20:14               ` Ralph Siemsen
2023-04-24  1:15 ` [PATCH v5 10/10] doc: renesas: add Renesas board docs Ralph Siemsen
2023-05-07 16:10   ` Marek Vasut
  -- strict thread matches above, loose matches on Subject: below --
2023-05-12 20:15 [PATCH v5 00/10] Renesas RZ/N1 SoC initial support Ralph Siemsen
2023-05-12 20:15 ` [PATCH v5 08/10] board: schneider: add RZN1 board support Ralph Siemsen
2023-05-12 20:36   ` Marek Vasut

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=20230512201242.GA2295717@maple.netwinder.org \
    --to=ralph.siemsen@linaro.org \
    --cc=judge.packham@gmail.com \
    --cc=marek.vasut@mailbox.org \
    --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