On Wed, Mar 31, 2021 at 09:04:15AM +0200, Arnd Bergmann wrote: > On Wed, Mar 31, 2021 at 3:46 AM Daniel Walker <danielwa@xxxxxxxxx> wrote: > > From: Ofer Licht <olicht@xxxxxxxxx> > > Thanks for the submission, it's always nice to see a new platform > > Define craw64 config, dts and Makefile for Cisco > > SoCs known as Craw. > > I'd like some more information about the platform, e.g. the target > market and maybe a link to the product information. Our SoC is produced as an internal product. So SoC specifications aren't widely available. Here is an example of a Cisco product which uses this SoC, https://www.cisco.com/c/en/us/products/collateral/switches/catalyst-9200-series-switches/nb-06-cat9200-ser-data-sheet-cte-en.html I suspect that's not really what your looking for tho. > > Cc: xe-linux-external@xxxxxxxxx > > Signed-off-by: Ofer Licht <olicht@xxxxxxxxx> > > Signed-off-by: Daniel Walker <danielwa@xxxxxxxxx> > > --- > > .../devicetree/bindings/vendor-prefixes.yaml | 2 + > > arch/arm64/Kconfig.platforms | 5 + > > arch/arm64/boot/dts/Makefile | 1 + > > arch/arm64/boot/dts/cisco/Makefile | 5 + > > .../arm64/boot/dts/cisco/craw64-dopplerg2.dts | 239 +++++++++++ > > arch/arm64/boot/dts/cisco/craw64.dtsi | 392 ++++++++++++++++++ > > arch/arm64/configs/defconfig | 1 + > > We have separate branches for dt, defconfig, and the rest, so it would be > good to split this patch up a little more. > > There should also be an entry in the top-level MAINTAINERS file. > > > diff --git a/arch/arm64/boot/dts/cisco/craw64-dopplerg2.dts b/arch/arm64/boot/dts/cisco/craw64-dopplerg2.dts > > new file mode 100644 > > index 000000000000..20ecc57b4e5c > > --- /dev/null > > +++ b/arch/arm64/boot/dts/cisco/craw64-dopplerg2.dts > > @@ -0,0 +1,239 @@ > > +/dts-v1/; > > + > > +#include "craw64.dtsi" > > + > > +/ { > > + model = "Cisco Craw64 on DopplerG 2.0"; > > + compatible = "cisco,craw64-dopplerg2", "cisco,craw64"; > > + > > + memory { > > + device_type = "memory"; > > + reg = <0x0 0x80000000 0x0 0x80000000>; > > + }; > > The memory size is usually filled by the boot loader, just put an > empty node into the .dtsi file Arnd, I must regretfully inform you that Cisco has a deep dark addiction to bootloaders which, are, um, how do I say this diplomatically, um , brain dead. You have some other comments below related to moving things into the bootloader, and I can look into it, but bootloader inflexibility is wide spread inside Cisco. > > > + doppler { > > + #address-cells = <2>; > > + #size-cells = <2>; > > + compatible = "simple-bus"; > > + ranges; > > + }; > > What is this? > It's a device, but the driver is not submitted. I can remove it along with the other device driver binding we have where the drivers and bindings aren't submitted. I'll do my best to fix the comments your given an resubmit. Daniel
