From: <Hari.PrasathGE@microchip.com>
To: <csokas.bence@prolan.hu>, <tudor.ambarus@linaro.org>,
<linux-spi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<Varshini.Rajendran@microchip.com>,
<alexandre.belloni@bootlin.com>, <broonie@kernel.org>,
<claudiu.beznea@tuxon.dev>, <Nicolas.Ferre@microchip.com>,
<Patrice.Vilchez@microchip.com>, <Cristian.Birsan@microchip.com>
Subject: Re: [PATCH v2] spi: atmel-quadspi: Create `atmel_qspi_ops` to support newer SoC families
Date: Tue, 5 Nov 2024 07:47:31 +0000 [thread overview]
Message-ID: <78f38031-1723-4474-9bea-1c23918a75f6@microchip.com> (raw)
In-Reply-To: <ad585127-9e3c-414a-84c2-c4ea3e6d3c7d@prolan.hu>
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:
>> Hi,
>>
>> Am Wed, Oct 30, 2024 at 01:37:52PM +0100 schrieb Csókás Bence:
>>> Hi,
>>>
>>> On 2024. 10. 30. 12:09, Tudor Ambarus wrote:
>>>> I think it's fine to split sama7g5 addition in smaller steps. But
>>>> please
>>>> add the sama7g5 support in the same patch set, otherwise this patch
>>>> doesn't make sense on its own.
>>>
>>> Well, actually, we're using SAMA5D2. My goal was just to somewhat
>>> harmonize
>>> upstream with the vendor kernel so that we may contribute other
>>> patches that
>>> we have made on top of the latter, or in the future, take patches from
>>> upstream and apply it to our vendor kernel-based tree. This patch was
>>> only
>>> meant to lay the groundworks for future SAMA7G5 support. I can of course
>>> send the "other half" of the original patch if needed, but I wouldn't
>>> want
>>> it to hold up this refactor.
>>
>> 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
>
> Bence
>
>
next prev parent reply other threads:[~2024-11-05 7:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 8:44 Csókás, Bence
2024-10-30 11:09 ` Tudor Ambarus
2024-10-30 12:37 ` Csókás Bence
2024-10-30 12:49 ` Tudor Ambarus
2024-11-04 12:48 ` Alexander Dahl
2024-11-04 12:56 ` Csókás Bence
2024-11-05 7:47 ` Hari.PrasathGE [this message]
2024-11-15 13:23 ` Csókás Bence
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=78f38031-1723-4474-9bea-1c23918a75f6@microchip.com \
--to=hari.prasathge@microchip.com \
--cc=Cristian.Birsan@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Patrice.Vilchez@microchip.com \
--cc=Varshini.Rajendran@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=csokas.bence@prolan.hu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=tudor.ambarus@linaro.org \
/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
all inboxes | Powered by JetHome®