From: Florian Fainelli <f.fainelli@gmail.com>
To: Christian Lamparter <chunkeey@gmail.com>,
linux-arm-kernel@lists.infradead.org
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
"Scott Branden" <scott.branden@broadcom.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Chris Blake" <chrisrblake93@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
"Ray Jui" <ray.jui@broadcom.com>
Subject: Re: [PATCH v2 0/6] ARM: BCM5301X: add Meraki MR32 series
Date: Wed, 26 Aug 2020 17:04:15 -0700 [thread overview]
Message-ID: <c3587ab9-eb92-a036-df26-4ed36a19cc7d@gmail.com> (raw)
In-Reply-To: <cover.1598111680.git.chunkeey@gmail.com>
On 8/22/2020 9:19 AM, Christian Lamparter wrote:
> Hello,
>
> I've been holding on to this devices dts' for a while now.
> But since the HW has been running with versions of these
> patches for more than a year, I do think I should make it
> available in upstream in order to move on.
>
> Hardware-Info of the Meraki MR32:
>
> This is a dual-band enterprise class 802.11ac access point.
> The unit was donated by Chris Blake. Thank you!
>
> SoC: Broadcom BCM53016A1 (1 GHz, 2 cores)
> RAM: 128 MiB
> NAND: 128 MiB Spansion S34ML01G2 (~114 MiB useable)
> ETH: 1GBit Ethernet Port - PoE
> WIFI1: Broadcom BCM43520 an+ac (2x2:2 - id: 0x4352)
> WIFI2: Broadcom BCM43520 bgn (2x2:2 - id: 0x4352)
> WIFI3: Broadcom BCM43428 abgn (1x1:1 - id: 43428)
>
> So far, the remaining TODOs center around the pinctrl,
> i2c and WIFI. The I2C is implemented with the bit-banged
> i2c-gpio driver as the SoC's I2C didn't budge after
> many hours of trying.
>
> A patch that included the "meraki" vendor-prefix has
> been broken out of the series as recommended by
> Florian Fainelli. Here's the link:
> <https://lists.ozlabs.org/pipermail/linuxppc-dev/2020-August/216949.html>
Series applied, thanks Christian, let's work separately on the pinctrl
driver and using the hardware i2c controller. Thanks
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-08-27 0:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 16:19 [PATCH v2 0/6] ARM: BCM5301X: add Meraki MR32 series Christian Lamparter
2020-08-22 16:19 ` [PATCH v2 1/6] dt-bindings: ARM: add bindings for the Meraki MR32 Christian Lamparter
2020-08-27 0:02 ` Florian Fainelli
2020-08-22 16:19 ` [PATCH v2 2/6] ARM: dts: BCM5301X: Specify PWM in the DT Christian Lamparter
2020-08-27 0:02 ` Florian Fainelli
2020-08-22 16:19 ` [PATCH v2 3/6] ARM: dts: BCM5301X: Specify uart2 " Christian Lamparter
2020-08-27 0:02 ` Florian Fainelli
2020-08-22 16:19 ` [PATCH v2 4/6] ARM: dts: BCM5301X: Specify pcie2 " Christian Lamparter
2020-08-27 0:03 ` Florian Fainelli
2020-08-22 16:19 ` [PATCH v2 5/6] MAINTAINERS: extend BCM5301X ARM ARCHITECTURE files Christian Lamparter
2020-08-27 0:03 ` Florian Fainelli
2020-08-22 16:19 ` [PATCH v2 6/6] ARM: BCM5301X: Add DT for Meraki MR32 Christian Lamparter
2020-08-27 0:03 ` Florian Fainelli
2020-09-10 20:38 ` Florian Fainelli
2020-09-11 17:27 ` Christian Lamparter
2020-09-11 17:30 ` Florian Fainelli
2020-08-27 0:04 ` Florian Fainelli [this message]
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=c3587ab9-eb92-a036-df26-4ed36a19cc7d@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=chrisrblake93@gmail.com \
--cc=chunkeey@gmail.com \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=ray.jui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=scott.branden@broadcom.com \
--cc=zajec5@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).