[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220726020952epcms1p59c06fabb55776e195dcbeac549c98ef7@epcms1p5>
Date: Tue, 26 Jul 2022 11:09:52 +0900
From: MyungJoo Ham <myungjoo.ham@...sung.com>
To: Oded Gabbay <ogabbay@...nel.org>
CC: Greg KH <gregkh@...uxfoundation.org>,
Jiho Chu <jiho.chu@...sung.com>, Arnd Bergmann <arnd@...db.de>,
"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
Yelin Jeong <yelini.jeong@...sung.com>,
"krzysztof.kozlowski@...aro.org" <krzysztof.kozlowski@...aro.org>,
ALIM AKHTAR <alim.akhtar@...sung.com>
Subject: RE: Re: [PATCH 0/9] Samsung Trinity NPU device driver
> Hi,
> Why isn't this submitted to soc/ subsystem ?
> Don't you think that would be more appropriate, given that this IP is
> integrated into application processors ?
>
> Thanks,
> Oded
This series (Trinity-V2.3, V2.4, A1, ..) is being integrated to multiple SoCs,
not limited to Samsung-designed chips (e.g., Exynos).
It's a bit weird to have them in /drivers/soc/samsung.
CC: Krzysztof and Alim (Samsung-SoC maintainers)
Cheers,
MyungJoo
Powered by blists - more mailing lists