Skip to content

powerpc: apm82181: adding customer devices

Christian Lamparter linux-devicetree linuxppc-dev 3 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v3 Latest5 patches 8 repliesIn review
  2. v24 patches 0 repliesSuperseded
  3. v1 RFC4 patches 0 repliesSuperseded

Patches in v3 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/5dt-bindings: powerpc: define apm,apm82181 bindingDocumentation/devicetree/bindings/powerpc/4xx/apm,apm82181.yaml+29 -01 reply
2/5powerpc: apm82181: create shared dtsi for APM bluestonearch/powerpc/boot/dts/apm82181.dtsi+466 -04 replies
3/5powerpc: apm82181: add WD MyBook Live NASarch/powerpc/boot/dts/wd-mybooklive.dts arch/powerpc/platforms/44x/ppc44x_simple.c+202 -10 replies
4/5powerpc: apm82181: add Meraki MR24 AParch/powerpc/boot/dts/meraki-mr24.dts arch/powerpc/platforms/44x/ppc44x_simple.c+238 -00 replies
5/5powerpc: apm82181: integrate bluestone.dtsarch/powerpc/boot/dts/bluestone.dts+104 -3540 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.

Read the v3 thread

Cover letter [PATCH v3 0/5] powerpc: apm82181: adding customer devices

Hello,

I've been holding on to these devices dts' for a while now. But ever since the recent purge of the PPC405, I'm feeling the urge to move forward.

The devices in question have been running with OpenWrt since around 2016/2017. Back then it was linux v4.4 and required many out-of-tree patches (for WIFI, SATA, CRYPTO...), that since have been integrated. So, there's nothing else in the way I think.

A patch that adds the Meraki vendor-prefix has been sent separately, as there's also the Meraki MR32 that I'm working on as well. Here's the link to the patch:
<https://lore.kernel.org/linuxppc-dev/[email protected]/>

Now, I've looked around in the arch/powerpc for recent .dts and device submissions to get an understanding of what is required.
From the looks of it, it seems like every device gets a skeleton defconfig and a CONFIG_$DEVICE symbol (Like:
CONFIG_MERAKI_MR24, CONFIG_WD_MYBOOKLIVE).

Will this be the case? Or would it make sense to further unite the Bluestone, MR24 and MBL under a common CONFIG_APM82181 and integrate the BLUESTONE device's defconfig into it as well? (I've stumbled across the special machine compatible handling of ppc in the Documentation/devicetree/usage-model.rst already.)

Cheers,
Christian

Note:
If someone has a WD MyBook Live (DUO) and is interested in giving it a spin with 5.8. I've made a:
"build your own Debian System" sort of script that can be found on github: <https://github.com/chunkeey/mbl-debian>
(the only remaining patch hack is for debian's make-kpkg crossbuild)

Furthermore, the OpenWrt project currently has images for the additional apm82181-based devices:
Cisco Meraki MX60(W) - Needs DSA for the AR8327 Netgear WNDAP620/WNDAP660 - (Could be next) Netgear WNDR4700 - Needs DSA for the AR8327

Note2: I do have a stash of extensive APM82181 related documentation.

Signature · 1 line
2.28.0

Read the cover letter in its thread