netdev - Re: [PATCH net-next 0/2] Document PolarFire SoC can controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4c5b43bd-a255-cbc1-c7a3-9a79e34d2e91@microchip.com>
Date:   Mon, 13 Jun 2022 12:52:00 +0000
From:   <Conor.Dooley@...rochip.com>
To:     <mkl@...gutronix.de>
CC:     <wg@...ndegger.com>, <davem@...emloft.net>, <edumazet@...gle.com>,
        <kuba@...nel.org>, <pabeni@...hat.com>, <robh+dt@...nel.org>,
        <krzysztof.kozlowski+dt@...aro.org>, <palmer@...belt.com>,
        <paul.walmsley@...ive.com>, <aou@...s.berkeley.edu>,
        <Daire.McNamara@...rochip.com>, <linux-can@...r.kernel.org>,
        <netdev@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <linux-riscv@...ts.infradead.org>,
        <Conor.Dooley@...rochip.com>
Subject: Re: [PATCH net-next 0/2] Document PolarFire SoC can controller


On 07/06/2022 09:54, Conor.Dooley@...rochip.com wrote:
> On 07/06/2022 09:28, Marc Kleine-Budde wrote:
>> On 07.06.2022 07:52:30, Conor.Dooley@...rochip.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...
>>>>
>>>> Nitpick:
>>>> Consider writing "CAN" in capital letters to avoid confusion for the not
>>>> informed reader.
>>>
>>> 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?
>>>
>>> There is a driver /but/ for now only a UIO one so I didn't send it.
>>
>> Brrrrr...
> 
> Yeah, I know..
> 
>>
>>> 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-9E1416A0A6E4-en-US-3/index.html?GUID-A362DC3C-83B7-4441-BECB-B19F9AD48B66
>>>
>>> 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?
> 
> Nope, that's all I've got...
> 
>> The register map cannot be downloaded directly anymore. For reference:
>>
>> http://web.archive.org/web/20220403030214/https://www.microsemi.com/document-portal/doc_download/1244581-polarfire-soc-register-map
> 
> Oh that sucks. I know we have had some website issues over the weekend
> which might be the problem there. I'll try to bring it up and find out.
> 

Hey Marc,
Doc is still not available but should be getting fixed.
What do I need to do for this binding? Are you happy to accept it without
a driver if I add links to the documentation and a working link to the
register map?
Thanks,
Conor.