Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
	"Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com>
Cc: <srinivas.kandagatla@oss.qualcomm.com>, <srini@kernel.org>,
	<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<linux-arm-msm@vger.kernel.org>, <linux-sound@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] slimbus: qcom: remove unused qcom controller driver
Date: Mon, 28 Jul 2025 11:24:49 +0200	[thread overview]
Message-ID: <DBNKVU7OQHNL.12Z6O3PI6SHGU@fairphone.com> (raw)
In-Reply-To: <mwhxikivaxtz5px5e7jkqtuuk2iz457fy5drsnaj32j4o5qqk6@hwkcjso4jpsp>

Hi all,

On Thu Jul 24, 2025 at 4:24 PM CEST, Dmitry Baryshkov wrote:
> On Thu, Jul 24, 2025 at 03:31:50PM +0200, Konrad Dybcio wrote:
>> On 7/24/25 3:28 PM, srinivas.kandagatla@oss.qualcomm.com wrote:
>> > From: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
>> > 
>> > Qcom Slimbus controller driver is totally unused and dead code, there is
>> > no point in keeping this driver in the kernel without users.
>> > 
>> > This patch removes the driver along with device tree bindings.
>> > 
>> > Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
>> > ---
>> 
>> I *thiiink* this is apq806x code, with 8974 adopting the new hw.
>> 
>> +Dmitry, does you computer history museum require this driver?
>
> I never had time to try enabling audio on IFC6410 nor Nexus 7. But if
> the driver would be actually useable there, I'd prefer to keep it.

FWIW on the WIP msm8974 audio branch (from years ago, unfortunately), I
don't see "qcom,slim" compatible being used, also with no change to
drivers/slimbus/qcom-ctrl.c.

That branch is using the compatible "qcom,slim-ngd-v1.5.0" for MSM8974.

So at least for my museum collection, it's not needed.

Regards
Luca

  parent reply	other threads:[~2025-07-28  9:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24 13:28 [PATCH] slimbus: qcom: remove unused qcom controller driver srinivas.kandagatla
2025-07-24 13:31 ` Konrad Dybcio
2025-07-24 14:24   ` Dmitry Baryshkov
2025-07-27 11:25     ` Srinivas Kandagatla
2025-07-27 16:12       ` Dmitry Baryshkov
2025-07-28  9:24     ` Luca Weiss [this message]
2025-07-25 23:23 ` Rob Herring (Arm)
2025-08-18  6:48 ` Srinivas Kandagatla
2025-08-19 13:35 ` Rob Herring
2025-08-19 13:44   ` Srinivas Kandagatla
2025-09-04 23:08     ` Rob Herring
2025-09-05  5:30       ` Srinivas Kandagatla
2025-09-19 17:25         ` Rob Herring
2025-10-01 14:19           ` Rob Herring
2025-10-01 14:21             ` Srinivas Kandagatla
2025-10-01 15:03               ` Srinivas Kandagatla
2025-10-01 15:31                 ` Rob Herring

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=DBNKVU7OQHNL.12Z6O3PI6SHGU@fairphone.com \
    --to=luca.weiss@fairphone.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=srini@kernel.org \
    --cc=srinivas.kandagatla@oss.qualcomm.com \
    /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