From: Krzysztof Kozlowski <krzk@kernel.org>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"tsbogend@alpha.franken.de" <tsbogend@alpha.franken.de>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"paulburton@kernel.org" <paulburton@kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"mail@birger-koblitz.de" <mail@birger-koblitz.de>,
"bert@biot.com" <bert@biot.com>,
"john@phrozen.org" <john@phrozen.org>,
"sander@svanheule.net" <sander@svanheule.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"kabel@kernel.org" <kabel@kernel.org>,
"ericwouds@gmail.com" <ericwouds@gmail.com>
Subject: Re: [PATCH v2 3/8] dt-bindings: mips: realtek: Add rtl930x-soc compatible
Date: Thu, 27 Jun 2024 08:59:15 +0200 [thread overview]
Message-ID: <905b483a-b011-44f9-bec9-c6b1c07f4fec@kernel.org> (raw)
In-Reply-To: <5267bf22-0b95-48ab-b207-ead4a697c263@alliedtelesis.co.nz>
On 26/06/2024 23:01, Chris Packham wrote:
>>>>> + - realtek,rtl9302c
>>>> Why board has the name of SoC?
>>> What I have is actually a reference board with the name
>>> RTL9302C_2xRTL8224_2XGE. If found that a bit incomprehensible so I
>>> (over) shortened it. Technically it would be something like
>>> cameo,rtl9302c-2x-rtl8224-2xge which I can include in the next round.
>> Looks fine to me.
>>
>>>>> + - const: realtek,rtl9302-soc
>>>> Drop the -soc suffix. The rtl9302 is the soc.
>>> On that. I hope to eventually add "realtek,rtl9302-switch" for the DSA
>>> switch block in the same chip. So keeping the -soc suffix was
>>> intentional to try to disambiguate things. I can drop the -soc if the
>>> consensus is that there is no need to disambiguate the two.
>> Thanks for explanation, kind of depends on what exactly is this. Most of
>> SoCs comprise of several items. The entire chip is the soc, e.g.
>> "qcom,foo1234". It might have MAC/Ethernet/whatever inside, controllable
>> by the SoC (Linux, bootloader, TF, hypervisor, other VM guest) and that
>> part is "qcom,foo1234-ethernet". Regardless whether Linux OS actually
>> controls it or not.
>>
>> The question is whether DSA switch is part of the SoC or not.
>
> The RTL9302C is a single package but I'd assume internally it has
> multiple dies.
>
> From the block diagram in the datasheet they do have a portion they
> call the "SoC" which has the CPU and peripherals like UARTs, GPIOs, SPI
> etc. That is separate from the switch block which has a bunch of MACs,
> SERDES and various network switch tables. So based on that
> "realtek,rtl9302-soc" and "realtek,rtl9302-switch" as two separate
> things make sense to me.
>
OK, -soc and -switch are fine with me.
> I'm still trying to figure out a bit more of the details. The block
> diagram looks a lot like you'd expect to see with a traditional DSA
> switch where you have a SoC Ethernet NIC/MAC connected to one port of a
> switch. But getting into the datasheet it looks like what they call the
> NIC is actually just the DMA portion of the switch as the registers are
> all in that second block. As is the MDIO interface. I'm considering that
> maybe the DSA model isn't right for this and I should be looking at
> switchdev instead.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-06-27 6:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 1:22 [PATCH v2 0/8] mips: Support for RTL9302C Chris Packham
2024-06-24 1:22 ` [PATCH v2 1/8] mips: dts: realtek: use "serial" instead of "uart" in node name Chris Packham
2024-06-24 1:22 ` [PATCH v2 2/8] mips: dts: realtek: add device_type property to cpu node Chris Packham
2024-06-24 1:22 ` [PATCH v2 3/8] dt-bindings: mips: realtek: Add rtl930x-soc compatible Chris Packham
2024-06-24 4:48 ` Krzysztof Kozlowski
2024-06-24 5:00 ` Chris Packham
2024-06-26 7:12 ` Krzysztof Kozlowski
2024-06-26 21:01 ` Chris Packham
2024-06-27 6:59 ` Krzysztof Kozlowski [this message]
2024-06-24 1:22 ` [PATCH v2 4/8] dt-bindings: timer: Add schema for realtek,otto-timer Chris Packham
2024-06-24 4:49 ` Krzysztof Kozlowski
2024-06-24 5:21 ` Chris Packham
2024-06-26 7:13 ` Krzysztof Kozlowski
2024-06-26 21:07 ` Chris Packham
2024-06-24 1:22 ` [PATCH v2 5/8] dt-bindings: interrupt-controller: realtek,rtl-intc: Add rtl9300-intc Chris Packham
2024-06-24 4:50 ` Krzysztof Kozlowski
2024-06-24 1:22 ` [PATCH v2 6/8] clocksource: realtek: Add timer driver for rtl-otto platforms Chris Packham
2024-06-26 21:22 ` kernel test robot
2024-06-24 1:22 ` [PATCH v2 7/8] mips: generic: add fdt fixup for Realtek reference board Chris Packham
2024-06-24 1:23 ` [PATCH v2 8/8] mips: dts: realtek: Add RTL9302C board Chris Packham
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=905b483a-b011-44f9-bec9-c6b1c07f4fec@kernel.org \
--to=krzk@kernel.org \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=bert@biot.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=ericwouds@gmail.com \
--cc=john@phrozen.org \
--cc=kabel@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mail@birger-koblitz.de \
--cc=paulburton@kernel.org \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=sander@svanheule.net \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.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
all inboxes | Powered by JetHome®