Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 7 Jun 2022 10:28:27 +0200
From:   Marc Kleine-Budde <mkl@pengutronix.de>
To:     Conor.Dooley@microchip.com
Cc:     wg@grandegger.com, davem@davemloft.net, edumazet@google.com,
        kuba@kernel.org, pabeni@redhat.com, robh+dt@kernel.org,
        krzysztof.kozlowski+dt@linaro.org, palmer@dabbelt.com,
        paul.walmsley@sifive.com, aou@eecs.berkeley.edu,
        Daire.McNamara@microchip.com, linux-can@vger.kernel.org,
        netdev@vger.kernel.org, devicetree@vger.kernel.org,
        linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH net-next 0/2] Document PolarFire SoC can controller
Message-ID: <20220607082827.iuonhektfbuqtuqo@pengutronix.de>
References: <20220607065459.2035746-1-conor.dooley@microchip.com>
 <20220607071519.6m6swnl55na3vgwm@pengutronix.de>
 <51e8e297-0171-0c3f-ba86-e61add04830e@microchip.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="ajso5cyytlmmpn5k"
Content-Disposition: inline
In-Reply-To: <51e8e297-0171-0c3f-ba86-e61add04830e@microchip.com>
Precedence: bulk


--ajso5cyytlmmpn5k
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 07.06.2022 07:52:30, Conor.Dooley@microchip.com wrote:
> On 07/06/2022 08:15, Marc Kleine-Budde wrote:
> > On 07.06.2022 07:54:58, Conor Dooley wrote:
> >> When adding the dts for PolarFire SoC, the can controllers were
> >                                             ^^^
> >> omitted, so here they are...
> >=20
> > Nitpick:
> > Consider writing "CAN" in capital letters to avoid confusion for the not
> > informed reader.
>=20
> Yeah, sure. I'll try to get over my fear of capital letters ;)

:)

> > Is the documentation for the CAN controller openly available? Is there a
> > driver somewhere?
>=20
> There is a driver /but/ for now only a UIO one so I didn't send it.

Brrrrr...

> There's an online doc & if the horrible link doesn't drop you there
> directly, its section 6.12.3:
> https://onlinedocs.microchip.com/pr/GUID-0E320577-28E6-4365-9BB8-9E1416A0=
A6E4-en-US-3/index.html?GUID-A362DC3C-83B7-4441-BECB-B19F9AD48B66
>=20
> And a PDF direct download here, see section 4.12.3 (page 72):
> https://www.microsemi.com/document-portal/doc_download/1245725-polarfire-=
soc-fpga-mss-technical-reference-manual

Thanks. The documentation is quite sparse, is there a more detailed one?
The register map cannot be downloaded directly anymore. For reference:

http://web.archive.org/web/20220403030214/https://www.microsemi.com/documen=
t-portal/doc_download/1244581-polarfire-soc-register-map

regards,
Marc

--=20
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |

--ajso5cyytlmmpn5k
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEBsvAIBsPu6mG7thcrX5LkNig010FAmKfDCgACgkQrX5LkNig
010ixggAri8+zJpGE06Rm9LwkSy5IXbnAuXl+05ecMHijzwTZoXuxRjLi7FLgUt8
RMmHB1ehanHgnud3Ux9EMH2GIbigcx6EwV5iEcShe8ltxXfHATt7HI/L1x8dtS/Z
e6ic76cZ24PHhR/EAn5+uN9O17sTaoj+nCx13pVdLOe1iHUqZQf3RaVbABSibySZ
wt1j6nOt7Au4o2hJCHXO3uQ72fiNDQQAdKIFRRqvsDvMVukw+nrt1vL8Fw87AKXU
xfswszw4E2QowEV8gQeSduJwoYBlzCiya0hQJjTrlWPpxlLpYIN0VsNX+oliI0BN
bXRB2pUhMmd1nv1wnSnZOzNcCS91/A==
=PF1R
-----END PGP SIGNATURE-----

--ajso5cyytlmmpn5k--