From: Ralph Siemsen <ralph.siemsen@linaro.org>
To: Bryan Brattlof <bb@ti.com>
Cc: u-boot@lists.denx.de, Andrew Davis <afd@ti.com>,
Gowtham Tammana <g-tammana@ti.com>, Jagan Teki <jagan@edgeble.ai>,
Kever Yang <kever.yang@rock-chips.com>,
Suman Anna <s-anna@ti.com>
Subject: Re: [RFC PATCH v3 5/9] ram: cadence: add driver for Cadence EDAC
Date: Tue, 7 Mar 2023 20:19:35 -0500 [thread overview]
Message-ID: <20230308011935.GA1923658@maple.netwinder.org> (raw)
In-Reply-To: <CANp-EDZAeVQoQvuE=39S5OtgViYMMkzrduWxCfYnaU1dYt0OOg@mail.gmail.com>
On Fri, Feb 24, 2023 at 10:19:53AM -0500, Ralph Siemsen wrote:
>Hi Bryan,
>
>On Thu, Feb 23, 2023 at 2:54 PM Bryan Brattlof <bb@ti.com> wrote:
>>
>> Hi Ralph!
>> Love seeing more boards here, though I know of a few chips that use some
>> type of cadence controller. I'm just curious if it would it make sense
>> to name this with some type of Renesas specific branding?
>
>Indeed the this IP from Cadence likely is used in quite a few places.
>However it is usually quite difficult to figure out exactly which
>version of the IP is present, what bugs/workarounds are needed, etc.
>
>I am fine with renaming this in a more renesas-specific manner
>(suggestions welcomed!). On the other hand, it would good to try and
>encourage having one driver for this, rather than a bunch of
>similar-but-not-quite-equivalent ones scattered about. Perhaps a
>non-specific name might help?
Can anyone offer guidance on the naming of the DDR controller? Other
than this issue, I have v4 of this patch series ready to post.
Thanks!
Ralph
next prev parent reply other threads:[~2023-03-08 1:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 15:44 [RFC PATCH v3 0/9] Renesas RZ/N1 SoC initial support Ralph Siemsen
2023-02-22 15:44 ` [RFC PATCH v3 1/9] ARM: armv7: add non-SPL enable for Cortex SMPEN Ralph Siemsen
2023-02-22 15:44 ` [RFC PATCH v3 2/9] clk: renesas: prepare for non-RCAR clock drivers Ralph Siemsen
2023-02-22 15:44 ` [RFC PATCH v3 3/9] clk: renesas: add R906G032 driver Ralph Siemsen
2023-02-22 16:06 ` Marek Vasut
2023-02-22 16:57 ` Ralph Siemsen
2023-02-22 17:07 ` Marek Vasut
2023-02-22 17:21 ` Ralph Siemsen
2023-02-22 17:47 ` Marek Vasut
2023-02-22 18:32 ` Ralph Siemsen
2023-02-22 18:45 ` Marek Vasut
2023-02-22 19:32 ` Ralph Siemsen
2023-02-23 0:12 ` Marek Vasut
2023-02-23 7:17 ` Miquel Raynal
2023-02-23 13:56 ` Marek Vasut
2023-02-23 14:09 ` Miquel Raynal
2023-02-24 15:14 ` Ralph Siemsen
2023-02-24 17:05 ` Marek Vasut
2023-02-24 18:00 ` Ralph Siemsen
2023-02-25 6:16 ` Marek Vasut
2023-02-22 15:44 ` [RFC PATCH v3 4/9] pinctrl: " Ralph Siemsen
2023-02-22 15:44 ` [RFC PATCH v3 5/9] ram: cadence: add driver for Cadence EDAC Ralph Siemsen
2023-02-23 19:54 ` Bryan Brattlof
2023-02-24 15:19 ` Ralph Siemsen
2023-03-08 1:19 ` Ralph Siemsen [this message]
2023-02-22 15:44 ` [RFC PATCH v3 6/9] dts: basic devicetree for Renesas RZ/N1 SoC Ralph Siemsen
2023-02-22 15:44 ` [RFC PATCH v3 7/9] ARM: rzn1: basic support " Ralph Siemsen
2023-02-22 15:44 ` [RFC PATCH v3 8/9] board: schneider: add RZN1 board support Ralph Siemsen
2023-02-22 15:44 ` [RFC PATCH v3 9/9] tools: spkgimage: add Renesas SPKG format Ralph Siemsen
2023-02-22 19:16 ` Simon Glass
2023-02-22 21:17 ` Ralph Siemsen
2023-02-22 21:20 ` Simon Glass
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=20230308011935.GA1923658@maple.netwinder.org \
--to=ralph.siemsen@linaro.org \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=g-tammana@ti.com \
--cc=jagan@edgeble.ai \
--cc=kever.yang@rock-chips.com \
--cc=s-anna@ti.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 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.