All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonard Lausen <leonard@lausen.nl>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	catalin.marinas@arm.com, will@kernel.org
Cc: robin.murphy@arm.com, amit.pundir@linaro.org,
	andersson@kernel.org, quic_sibis@quicinc.com,
	sumit.semwal@linaro.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: [PATCH] Revert "arm64: dma: Drop cache invalidation from arch_dma_prep_coherent()"
Date: Thu, 08 Dec 2022 04:59:16 +0000	[thread overview]
Message-ID: <868rjijxsr.fsf@lausen.nl> (raw)
In-Reply-To: <20221114110329.68413-1-manivannan.sadhasivam@linaro.org>

Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> writes:
> This reverts commit c44094eee32f32f175aadc0efcac449d99b1bbf7.
>
> As reported by Amit [1], dropping cache invalidation from
> arch_dma_prep_coherent() triggers a crash on the Qualcomm SM8250 platform
> (most probably on other Qcom platforms too).

On sc7180 with c44094ee applied, it does not trigger crash but makes
Wifi dysfunctional by preventing initialization of ath10k_snoc.

qcom-q6v5-mss 4080000.remoteproc: PBL returned unexpected status -284098560

With the revert of c44094ee, wifi works fine again.

Thank you
Leonard

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Leonard Lausen <leonard@lausen.nl>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	catalin.marinas@arm.com, will@kernel.org
Cc: robin.murphy@arm.com, amit.pundir@linaro.org,
	andersson@kernel.org, quic_sibis@quicinc.com,
	sumit.semwal@linaro.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: [PATCH] Revert "arm64: dma: Drop cache invalidation from arch_dma_prep_coherent()"
Date: Thu, 08 Dec 2022 04:59:16 +0000	[thread overview]
Message-ID: <868rjijxsr.fsf@lausen.nl> (raw)
In-Reply-To: <20221114110329.68413-1-manivannan.sadhasivam@linaro.org>

Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> writes:
> This reverts commit c44094eee32f32f175aadc0efcac449d99b1bbf7.
>
> As reported by Amit [1], dropping cache invalidation from
> arch_dma_prep_coherent() triggers a crash on the Qualcomm SM8250 platform
> (most probably on other Qcom platforms too).

On sc7180 with c44094ee applied, it does not trigger crash but makes
Wifi dysfunctional by preventing initialization of ath10k_snoc.

qcom-q6v5-mss 4080000.remoteproc: PBL returned unexpected status -284098560

With the revert of c44094ee, wifi works fine again.

Thank you
Leonard

  parent reply	other threads:[~2022-12-08  5:01 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 11:03 [PATCH] Revert "arm64: dma: Drop cache invalidation from arch_dma_prep_coherent()" Manivannan Sadhasivam
2022-11-14 11:03 ` Manivannan Sadhasivam
2022-11-14 11:29 ` Manivannan Sadhasivam
2022-11-14 11:29   ` Manivannan Sadhasivam
2022-11-14 14:11 ` Will Deacon
2022-11-14 14:11   ` Will Deacon
2022-11-14 15:14   ` Robin Murphy
2022-11-14 15:14     ` Robin Murphy
2022-11-14 17:38     ` Catalin Marinas
2022-11-14 17:38       ` Catalin Marinas
2022-11-18 10:54       ` Manivannan Sadhasivam
2022-11-18 10:54         ` Manivannan Sadhasivam
2022-11-18 12:33         ` Will Deacon
2022-11-18 12:33           ` Will Deacon
2022-11-21  6:42           ` Manivannan Sadhasivam
2022-11-21  6:42             ` Manivannan Sadhasivam
2022-11-21 10:12             ` Sibi Sankar
2022-11-21 10:12               ` Sibi Sankar
2022-11-24 11:55               ` Catalin Marinas
2022-11-24 11:55                 ` Catalin Marinas
2022-12-01  9:29                 ` Thorsten Leemhuis
2022-12-01  9:29                   ` Thorsten Leemhuis
2022-12-01 17:45                   ` Catalin Marinas
2022-12-01 17:45                     ` Catalin Marinas
2022-12-02  8:26                     ` Amit Pundir
2022-12-02  8:26                       ` Amit Pundir
2022-12-02  8:54                       ` Thorsten Leemhuis
2022-12-02  8:54                         ` Thorsten Leemhuis
2022-12-02 10:03                         ` Will Deacon
2022-12-02 10:03                           ` Will Deacon
2022-12-02 10:34                           ` Thorsten Leemhuis
2022-12-02 10:34                             ` Thorsten Leemhuis
2022-12-02 16:10                             ` Greg KH
2022-12-02 16:10                               ` Greg KH
2022-12-02 16:27                               ` Thorsten Leemhuis
2022-12-02 16:27                                 ` Thorsten Leemhuis
2022-12-02 16:32                                 ` Greg KH
2022-12-02 16:32                                   ` Greg KH
2022-12-02 17:14                                   ` Manivannan Sadhasivam
2022-12-02 17:14                                     ` Manivannan Sadhasivam
2022-12-05 14:24                                     ` Will Deacon
2022-12-05 14:24                                       ` Will Deacon
2022-12-06  9:21                                       ` Manivannan Sadhasivam
2022-12-06  9:21                                         ` Manivannan Sadhasivam
2022-12-06  9:58                                         ` Will Deacon
2022-12-06  9:58                                           ` Will Deacon
2022-12-02 10:54                           ` Manivannan Sadhasivam
2022-12-02 10:54                             ` Manivannan Sadhasivam
2022-11-28  5:44 ` Thorsten Leemhuis
2022-11-28  5:44   ` Thorsten Leemhuis
2022-11-28  8:15   ` Manivannan Sadhasivam
2022-11-28  8:15     ` Manivannan Sadhasivam
2022-12-08  4:59 ` Leonard Lausen [this message]
2022-12-08  4:59   ` Leonard Lausen
  -- strict thread matches above, loose matches on Subject: below --
2022-12-06 10:34 Will Deacon
2022-12-06 11:24 ` Manivannan Sadhasivam
2022-12-06 17:50 ` Catalin Marinas

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=868rjijxsr.fsf@lausen.nl \
    --to=leonard@lausen.nl \
    --cc=amit.pundir@linaro.org \
    --cc=andersson@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=quic_sibis@quicinc.com \
    --cc=robin.murphy@arm.com \
    --cc=sumit.semwal@linaro.org \
    --cc=will@kernel.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.