Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) client-ip=2620:137:e000::3:5;
Date:   Wed, 29 Nov 2023 19:04:47 +0900
From:   Youngmin Nam <youngmin.nam@samsung.com>
To:     Krzysztof Kozlowski <krzk@kernel.org>
Cc:     tomasz.figa@gmail.com, s.nawrocki@samsung.com,
        alim.akhtar@samsung.com, linus.walleij@linaro.org,
        linux-arm-kernel@lists.infradead.org,
        linux-samsung-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
        linux-kernel@vger.kernel.org, semen.protsenko@linaro.org
Subject: Re: [PATCH v2] pinctrl: samsung: add irq_set_affinity() for non
 wake up external gpio interrupt
Message-ID: <ZWcMv8Bg12vqBCUm@perf>
MIME-Version: 1.0
In-Reply-To: <f814a1f4-2e3d-4946-949a-8ddac5e30d5f@kernel.org>
Content-Type: multipart/mixed;
        boundary="----beKDcrNeaD4oBIFRuchmvdVAwfnDGI5TYPt7fforSuRq9wgD=_37ba7_"
CMS-TYPE: 102P
DLP-Filter: Pass
References: <CGME20231126091120epcas2p4a1320e3b0f9be8f8a0f575a322981d38@epcas2p4.samsung.com>
        <20231126094618.2545116-1-youngmin.nam@samsung.com>
        <bb738a6b-815d-4fad-b73f-559f1ba8cd68@linaro.org> <ZWU75VtJ/mXpMyQr@perf>
        <1fd55b36-0837-4bf7-9fde-e573d6cb214a@linaro.org>
        <CAPLW+4n0SAOTb6wocY-WjkxgSFMbx+nVuqdaPcNYVDsbfg+EfA@mail.gmail.com>
        <ZWbjPIydJRrPnuDy@perf> <a0ac295b-ea96-475c-acde-5a61de8ca170@linaro.org>
        <ZWb6cyTgyEcee7DZ@perf> <f814a1f4-2e3d-4946-949a-8ddac5e30d5f@kernel.org>
Precedence: bulk

------beKDcrNeaD4oBIFRuchmvdVAwfnDGI5TYPt7fforSuRq9wgD=_37ba7_
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline

On Wed, Nov 29, 2023 at 09:39:45AM +0100, Krzysztof Kozlowski wrote:
> On 29/11/2023 09:46, Youngmin Nam wrote:
> >>> I couldn't find out a pin for the test on E850-96 board yet.
> >>> We can test if there is a usage of *Non" Wake up External Interrupt of GPIO
> >>> on E850-96 board.
> >>>
> >>> Do you have any idea ?
> >>
> >> Please test on any upstream platform or upstream your existing platform.
> >> I hesitate to take this change because I don't trust Samsung that this
> >> was tested on mainline kernel. OK, for sure 100% it was not tested on
> >> mainline, but I am afraid that differences were far beyond just missing
> >> platforms. Therefore the issue might or might not exist at all. Maybe
> >> issue is caused by other Samsung non-upstreamed code.
> >>
> >> Best regards,
> >> Krzysztof
> > 
> > Sure. Let me find how to test on upstreamed device like E850-96 board.
> 
> There are many reasons why companies using Linux for their products
> should be involved in upstreaming their devices.
> 
> The one visible from this conversation: Whatever technical debt you
> have, it will be only growing because upstream might not even take
> simple patches from you, until you start contributing with the rest.
> Samsung's out-of-tree kernels are so far away from the upstream, that
> basically we might feel that contributions from Samsung are not
> addressing real problems. This will affect your Android trees due to GKI.
> 
> That's one more argument to talk to with your managers why staying away
> from the upstream is not the best idea.
> 
> Second argument is look at your competitor: Qualcomm, one of the most
> active upstreamers of SoC code doing awesome job.
> 
> Best regards,
> Krzysztof

Thank you for your opinion.
By the way, this patch is not related with GKI and I just thought this work
would be helpful to all exynos platform.

But it seems that changing affinity of any irqs including gpio is not allowed
on exynos platform. So we need to debug by adding some logs.

> 
> 

------beKDcrNeaD4oBIFRuchmvdVAwfnDGI5TYPt7fforSuRq9wgD=_37ba7_
Content-Type: text/plain; charset="utf-8"


------beKDcrNeaD4oBIFRuchmvdVAwfnDGI5TYPt7fforSuRq9wgD=_37ba7_--