All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Oreoluwa Babatunde <oreoluwa.babatunde@oss.qualcomm.com>,
	Georgi Djakov <georgi.djakov@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org,
	abelvesa@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, minchan@kernel.org,
	senozhatsky@chromium.org, axboe@kernel.dk, rostedt@goodmis.org,
	mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org, djakov@kernel.org
Subject: Re: [PATCH 2/6] soc: qcom: qpace: Add Qualcomm Page Compression Engine driver
Date: Wed, 7 Oct 2026 09:51:37 +0200	[thread overview]
Message-ID: <b12214fc-2e06-4e52-8bda-6c6f9a76bd7a@kernel.org> (raw)
In-Reply-To: <fed665c5-3062-462b-928d-ab60976ce839@oss.qualcomm.com>

On 07/10/2026 01:51, Oreoluwa Babatunde wrote:
> On 10/1/2026 1:50 AM, Krzysztof Kozlowski wrote:
>> On Wed, Sep 30, 2026 at 07:52:11AM -0700, Georgi Djakov wrote:
>>> Add a platform driver for the Qualcomm Page Compression Engine (QPaCE), a
>>> hardware block that accelerates compression and decompression of memory
>>> pages.
>>>
>>> Provide the urgent command path for synchronous single-page compression and
>>> decompression. This exposes the low-latency operations needed by
>>> compressed-memory users such as zram, especially for page decompression on
>>> the read path.
>>>
>>> Signed-off-by: Georgi Djakov <georgi.djakov@oss.qualcomm.com>
>>> ---
>>>   drivers/soc/qcom/Kconfig          |  14 +
>>>   drivers/soc/qcom/Makefile         |   1 +
>>>   drivers/soc/qcom/qpace.c          | 764 ++++++++++++++++++++++++++++++
>>>   drivers/soc/qcom/qpace_internal.h |  84 ++++
>>>   include/linux/soc/qcom/qpace.h    | 154 ++++++
>>>   5 files changed, 1017 insertions(+)
>>>   create mode 100644 drivers/soc/qcom/qpace.c
>>>   create mode 100644 drivers/soc/qcom/qpace_internal.h
>>>   create mode 100644 include/linux/soc/qcom/qpace.h
>>>
>>> diff --git a/drivers/soc/qcom/Kconfig b/drivers/soc/qcom/Kconfig
>>> index 535c8619197b..6bcb86dcd726 100644
>>> --- a/drivers/soc/qcom/Kconfig
>>
>> Sorry, but no. Soc is not a dumping ground. This has clear function of
>> compression offload, so it should have some dedicated maintainers like
>> other offload engines.
> 
> The reason for putting this in soc/qcom is because this is a qcom HW 

Every qcom HW driver is a qcom HW driver and they DO NOT go to drivers/soc.

Again: soc is not a dumping ground.

Best regards,
Krzysztof

  reply	other threads:[~2026-10-07  7:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 14:52 [PATCH 0/6] soc: qcom: Add Qualcomm Page Compression Engine (QPaCE) driver Georgi Djakov
2026-09-30 14:52 ` [PATCH 1/6] dt-bindings: soc: qcom: Add QPaCE binding Georgi Djakov
2026-10-02  6:10   ` Krzysztof Kozlowski
2026-09-30 14:52 ` [PATCH 2/6] soc: qcom: qpace: Add Qualcomm Page Compression Engine driver Georgi Djakov
2026-09-30 15:04   ` sashiko-bot
2026-10-03  0:06     ` Oreoluwa Babatunde
2026-10-01  8:50   ` Krzysztof Kozlowski
2026-10-06 23:51     ` Oreoluwa Babatunde
2026-10-07  7:51       ` Krzysztof Kozlowski [this message]
2026-10-08  0:08         ` Oreoluwa Babatunde
2026-09-30 14:52 ` [PATCH 3/6] trace: qpace: Add tracepoints for QPaCE operations Georgi Djakov
2026-09-30 15:00   ` sashiko-bot
2026-09-30 14:52 ` [PATCH 4/6] zram: Add QPaCE zcomp backend Georgi Djakov
2026-09-30 15:08   ` sashiko-bot
2026-10-01  5:43   ` Sergey Senozhatsky
2026-10-06 23:53     ` Oreoluwa Babatunde
2026-10-08  3:52       ` Sergey Senozhatsky
2026-10-01  8:51   ` Krzysztof Kozlowski
2026-10-01 10:27     ` Sergey Senozhatsky
2026-10-07  0:04       ` Oreoluwa Babatunde
2026-10-07  0:03     ` Oreoluwa Babatunde
2026-09-30 14:52 ` [PATCH 5/6] soc: qcom: qpace: Add LLCC slice support Georgi Djakov
2026-09-30 15:08   ` sashiko-bot
2026-09-30 14:52 ` [PATCH 6/6] arm64: dts: qcom: hawi: Add QPaCE DT node Georgi Djakov
2026-09-30 14:59   ` sashiko-bot

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=b12214fc-2e06-4e52-8bda-6c6f9a76bd7a@kernel.org \
    --to=krzk@kernel.org \
    --cc=abelvesa@kernel.org \
    --cc=andersson@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=djakov@kernel.org \
    --cc=georgi.djakov@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=minchan@kernel.org \
    --cc=oreoluwa.babatunde@oss.qualcomm.com \
    --cc=robh@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.