linux-kernel - Re: [PATCH v2] spi: atmel-quadspi: Create `atmel_qspi

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] [day] [month] [year] [list]

Message-ID: <32a5c58c-f318-4c02-ae76-421b9cca0875@prolan.hu>
Date: Fri, 15 Nov 2024 14:23:08 +0100
From: Csókás Bence <csokas.bence@...lan.hu>
To: <Hari.PrasathGE@...rochip.com>, <tudor.ambarus@...aro.org>,
	<linux-spi@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>, <Varshini.Rajendran@...rochip.com>,
	<alexandre.belloni@...tlin.com>, <broonie@...nel.org>,
	<claudiu.beznea@...on.dev>, <Nicolas.Ferre@...rochip.com>,
	<Patrice.Vilchez@...rochip.com>, <Cristian.Birsan@...rochip.com>
Subject: Re: [PATCH v2] spi: atmel-quadspi: Create `atmel_qspi_ops` to support
 newer SoC families

Hi,

On 2024. 11. 05. 8:47, Hari.PrasathGE@...rochip.com wrote:
> Hello Bence,
> 
> On 11/4/24 6:26 PM, Csókás Bence wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know
>> the content is safe
>>
>> Hi!
>>
>> On 2024. 11. 04. 13:48, Alexander Dahl wrote:
>>> It would actually be better if vendor would bring their stuff
>>> upstream, so there's no need for a vendor kernel.  Did you talk to
>>> Microchip about their upstreaming efforts?  What was the answer?
>>>
>>> Greets
>>> Alex
>>
>> Agreed. Though in this case, the original patch *was* submitted by
>> Microchip (by Tudor, originally) for upstream inclusion, but it was not
>> merged. Hence this forward-port.
>> Link:
>> https://lore.kernel.org/linux-spi/20211214133404.121739-1-tudor.ambarus@microchip.com/
> 
> 
> Thanks for your patch. We are planning to revive this work at the
> earliest. While I don't have specific timeline for this, we at Microchip
> are fully aware of this gap and doing everything we could to keep the
> delta between the upstream kernel and vendor kernel as minimal as possible.
> 
> We will discuss internally and provide you the feedback. Thanks again
> for your efforts.
> 
> Regards,
> Hari

Did you reach a conclusion internally regarding whether to support this 
patch? Since then, I opened a ticket with Microchip, but haven't got a 
response yet. I have also been in face-to-face contact with some of the 
engineers from the Rousset office, and they have expressed their 
support, and even the possibility of lending us a SAMA7G5 to test with. 
So really, all I'm waiting for is this patch to be merged, and then I 
can submit the SAMA7G5 parts, at worst as an RFC, if we don't get the 
real hardware in time.

Bence