as module if QCOM_RPROC_COMMON is built as module too.
Fixes: 747ff7d3d742 ("ath10k: Don't always treat modem stop events as crashes")
Cc: sta...@vger.kernel.org
Signed-off-by: Dmitry Baryshkov
---
drivers/net/wireless/ath/ath10k/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/d
On Fri, 5 Apr 2024 at 14:57, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > On Tue, 30 Jan 2024 at 08:47, Dmitry Baryshkov
> > wrote:
> >
> >>
> >> The ath10k driver fails to properly handle fallback from board-2.bin to
> >
On Fri, 5 Apr 2024 at 14:57, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > On Tue, 30 Jan 2024 at 08:47, Dmitry Baryshkov
> > wrote:
> >
> >>
> >> The ath10k driver fails to properly handle fallback from board-2.bin to
> >
On Fri, 5 Apr 2024 at 15:41, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > On Fri, 5 Apr 2024 at 15:01, Kalle Valo wrote:
> >
> >>
> >> Dmitry Baryshkov writes:
> >>
> >> > On Fri, 8 Mar 2024 at 17:19,
On Fri, 5 Apr 2024 at 15:01, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > On Fri, 8 Mar 2024 at 17:19, Kalle Valo wrote:
> >>
> >> Dmitry Baryshkov writes:
> >>
> >> >> To be on the safe side using 'qcom-rb1' makes sense but on
On Thu, 4 Apr 2024 at 15:30, Marc Gonzalez wrote:
>
> On 04/04/2024 13:57, Kalle Valo wrote:
>
> > Dmitry Baryshkov wrote:
> >
> >> I'd say, we should take a step back and actually verify how this was
> >> handled in the vendor kernel.
> >
> >
random
Signed-off-by: Dmitry Baryshkov
---
Note the device also uses updated wlanmdsp, so it will be updated with
firmware-name for WiFi once [1] is merged.
[ 68.236220] ath10k_snoc 1880.wifi: chan info: invalid frequency 0 (idx
41 out of bounds)
[ 69.426700] ath10k_snoc 1880.wifi
On Wed, 3 Apr 2024 at 16:05, Marc Gonzalez wrote:
>
> On 02/04/2024 17:55, Dmitry Baryshkov wrote:
>
> > On Tue, 2 Apr 2024 at 18:31, Marc Gonzalez wrote:
> >
> >> So, if I understand correctly, I take this to mean that I should:
> >>
> >> 1
On Tue, 2 Apr 2024 at 21:25, Alexey Minnekhanov
wrote:
>
>
>
> On 02.04.2024 18:55, Dmitry Baryshkov wrote:
> > I'd say, we should take a step back and actually verify how this was
> > handled in the vendor kernel.
>
>
> AFAIK there is no s
On Tue, 2 Apr 2024 at 21:22, Jeff Johnson wrote:
>
> On 4/2/2024 8:55 AM, Dmitry Baryshkov wrote:
> > I'd say, we should take a step back and actually verify how this was
> > handled in the vendor kernel.
>
> (error handling and other non-QMI code removed from the foll
On Tue, 2 Apr 2024 at 18:31, Marc Gonzalez wrote:
>
> On 02/04/2024 16:34, Konrad Dybcio wrote:
>
> > On 30.03.2024 7:25 PM, Krzysztof Kozlowski wrote:
> >
> >> On 28/03/2024 18:39, Marc Gonzalez wrote:
> >>
> >>> The ath10k driver waits for an "MSA_READY" indicator
> >>> to complete
On Tue, 30 Jan 2024 at 08:47, Dmitry Baryshkov
wrote:
>
> The ath10k driver fails to properly handle fallback from board-2.bin to
> board.bin for WCN3990 cards. This happens because the
> ath10k_hw_params_list doesn't include .fw.board* parameters for the
> WCN3990 platform.
>
On Wed, 6 Mar 2024 at 10:16, Dmitry Baryshkov
wrote:
>
> On WCN3990 platforms actual firmware, wlanmdsp.mbn, is sideloaded to the
> modem DSP via the TQFTPserv. These MBN files are signed by the device
> vendor, can only be used with the particular SoC or device.
>
> Unfor
On Tue, 26 Mar 2024 at 19:45, Marc Gonzalez wrote:
>
> [ It has been pointed out to me that the previous message was unclear. ]
> [ Below is my 2nd attempt at a clearer message. ]
>
> Problem: firmware-5.bin has not been parsed yet when we have to handle
> the ATH10K_QMI_EVENT_SERVER_ARRIVE case,
On Thu, 14 Mar 2024 at 14:31, Marc Gonzalez wrote:
>
> On 13/03/2024 16:53, Dmitry Baryshkov wrote:
>
> > On Wed, 13 Mar 2024 at 17:09, Marc Gonzalez wrote:
> >
> >> On 05/03/2024 20:20, Kalle Valo wrote:
> >>
> >>> Marc Gonzalez wrote:
> >
On Wed, 13 Mar 2024 at 17:09, Marc Gonzalez wrote:
>
> [ Dropping the DT fellows ]
>
> On 05/03/2024 20:20, Kalle Valo wrote:
>
> > Marc Gonzalez wrote:
> >
> >> I need to build a kernel + rootfs + FW to test the proposed solution,
> >> then I can spin a formal submission.
> >
> > Yeah, please do
On Fri, 8 Mar 2024 at 17:19, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> >> To be on the safe side using 'qcom-rb1' makes sense but on the other
> >> hand that means we need to update linux-firmware (basically add a new
> >> symlink) everytime a new p
On Thu, 7 Mar 2024 at 00:25, Jeff Johnson wrote:
>
> On 3/6/2024 6:23 AM, Dmitry Baryshkov wrote:
> > After some thought, I'd suggest to follow approach taken by the rest
> > of qcom firmware:
> > put a default (accepted by non-secured hardware) firmware to SoC dir
&
On Wed, 6 Mar 2024 at 13:15, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > On Wed, 6 Mar 2024 at 11:04, Kalle Valo wrote:
> >
> >>
> >> Dmitry Baryshkov writes:
> >>
> >> > On WCN3990 platforms actual firmware, wlanmdsp.
On Wed, 6 Mar 2024 at 11:04, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > On WCN3990 platforms actual firmware, wlanmdsp.mbn, is sideloaded to the
> > modem DSP via the TQFTPserv. These MBN files are signed by the device
> > vendor, can only be used with t
For WCN3990 platforms we need to look for the platform / board specific
firmware-N.mbn file which corresponds to the wlanmdsp.mbn loaded to the
modem DSP via the TQFTPserv. Add firmware-name property describing this
classifier.
Acked-by: Krzysztof Kozlowski
Signed-off-by: Dmitry Baryshkov
Add firmware-name property to the WiFi device tree node to specify
board-specific lookup directory.
Reviewed-by: Konrad Dybcio
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/qrb2210-rb1.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/qcom/qrb2210-rb1
= "qrb4210" property will make the
driver look for the firmware-N.bin first in ath10k/WCN3990/hw1.0/qrb4210
directory and then fallback to the default ath10k/WCN3990/hw1.0 dir.
Signed-off-by: Dmitry Baryshkov
---
Changes in v2:
- Fixed the comment about the default board name being NULL (Kalle)
Add firmware-name property to the WiFi device tree node to specify
board-specific lookup directory.
Reviewed-by: Konrad Dybcio
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/qrb4210-rb2.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/qcom/qrb4210-rb2
-specific data with finer granularity than DT overrides.
Signed-off-by: Dmitry Baryshkov
---
drivers/net/wireless/ath/ath10k/core.c | 11 ++-
drivers/net/wireless/ath/ath10k/core.h | 2 ++
drivers/net/wireless/ath/ath10k/snoc.c | 3 +++
3 files changed, 15 insertions(+), 1 deletion
On Mon, 4 Mar 2024 at 22:17, Conor Dooley wrote:
>
> On Mon, Mar 04, 2024 at 09:59:13PM +0200, Dmitry Baryshkov wrote:
> > On Mon, 4 Mar 2024 at 21:46, Conor Dooley wrote:
> > > On Mon, Mar 04, 2024 at 09:37:00PM +0200, Dmitry Baryshkov wrote:
> > > > On Mon,
On Mon, 4 Mar 2024 at 21:46, Conor Dooley wrote:
>
> On Mon, Mar 04, 2024 at 09:37:00PM +0200, Dmitry Baryshkov wrote:
> > On Mon, 4 Mar 2024 at 21:34, Conor Dooley wrote:
> > >
> > > On Mon, Mar 04, 2024 at 05:21:37PM +0100, Marc Gonzalez wrote:
> > > &g
On Mon, 4 Mar 2024 at 21:34, Conor Dooley wrote:
>
> On Mon, Mar 04, 2024 at 05:21:37PM +0100, Marc Gonzalez wrote:
> > On 29/02/2024 19:40, Conor Dooley wrote:
> >
> > > On Wed, Feb 28, 2024 at 06:37:08PM +0200, Kalle Valo wrote:
> > >
> > >> Marc Gonzalez wrote:
> > >>
> > >>> As mentioned in
On Mon, 12 Feb 2024 at 22:56, Jeff Johnson wrote:
>
> On 1/30/2024 8:38 AM, Dmitry Baryshkov wrote:
> > On WCN3990 platforms actual firmware, wlanmdsp.mbn, is sideloaded to the
> > modem DSP via the TQFTPserv. These MBN files are signed by the device
> >
On Mon, 12 Feb 2024 at 13:12, Konrad Dybcio wrote:
>
> On 30.01.2024 17:38, Dmitry Baryshkov wrote:
> > Different Qualcomm platforms using WCN3990 WiFI chip use SoC-specific
> > firmware versions with different features. For example firmware for
> > SDM845 doesn't use sing
of the fw dir used to lookup the firmware-N.bin file
decribing corresponding WiFi firmware.
Signed-off-by: Dmitry Baryshkov
---
drivers/net/wireless/ath/ath10k/core.c | 11 ++-
drivers/net/wireless/ath/ath10k/core.h | 2 ++
drivers/net/wireless/ath/ath10k/snoc.c | 3 +++
3 files
Add firmware-name property to the WiFi device tree node to specify
board-specific lookup directory.
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/qrb2210-rb1.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/qcom/qrb2210-rb1.dts
b/arch/arm64/boot/dts
= "qrb4210" property will make the
driver look for the firmware-N.bin first in ath10k/WCN3990/hw1.0/qrb4210
directory and then fallback to the default ath10k/WCN3990/hw1.0 dir.
Signed-off-by: Dmitry Baryshkov
---
Dmitry Baryshkov (4):
dt-bindings: net: wireless: ath10k: describe fir
For WCN3990 platforms we need to look for the platform / board specific
firmware-N.mbn file which corresponds to the wlanmdsp.mbn loaded to the
modem DSP via the TQFTPserv. Add firmware-name property describing this
classifier.
Signed-off-by: Dmitry Baryshkov
---
Documentation/devicetree
Add firmware-name property to the WiFi device tree node to specify
board-specific lookup directory.
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/qrb4210-rb2.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/qcom/qrb4210-rb2.dts
b/arch/arm64/boot/dts
The .fw.board parameter predates board-2.bin support. For all the
platforms, which define this parameter, it is equal to "board.bin".
Other platforms (like WCN3990) ommit it, limiting the ability to
provide board-specific data file.
Signed-off-by: Dmitry Baryshkov
---
drivers/net/wi
Specify board data size (and board.bin filename) for the WCN3990
platform.
Reported-by: Yongqin Liu
Fixes: 03a72288c546 ("ath10k: wmi: add hw params entry for wcn3990")
Signed-off-by: Dmitry Baryshkov
---
drivers/net/wireless/ath/ath10k/core.c | 3 +++
drivers/net/wireless/ath/a
of BDF support: drop .board and .eboard names from struct
ath10k_hw_params_fw and use the common name instead.
Signed-off-by: Dmitry Baryshkov
---
Dmitry Baryshkov (3):
wifi: ath10k: populate board data for WCN3990
wifi: ath10k: drop chip-specific board data file name
wifi: ath10k
Follow the example set up by previous commit and drop .fw.eboard
setting. Instead always use "eboard.bin" in this case. QCA9984 already
uses that file name, any (im)possible future users will just have to use
the same file name.
Signed-off-by: Dmitry Baryshkov
---
drivers/net/wi
On Wed, 13 Dec 2023 at 16:07, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > We'd like to ask for inclusion of the board file for the Qualcomm
> > SDM845 MTP board. It is a hardware development kit manufactured by
> > Qualcomm, using the Snapdragon SDM845 S
Hello Kalle,
We'd like to ask for inclusion of the board file for the Qualcomm
SDM845 MTP board. It is a hardware development kit manufactured by
Qualcomm, using the Snapdragon SDM845 SoC and a variant of wcn3990
BT/WiFi chip.
Following the questions from the ath10k wiki page:
* description for
On Thu, 7 Dec 2023 at 16:59, Kalle Valo wrote:
>
>
> I don't see any attachments, forgot to attach to it? Please resend the
> whole file.
Oops. Done.
--
With best wishes
Dmitry
On Tue, 5 Dec 2023 at 14:37, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > On Mon, 4 Dec 2023 at 18:14, Kalle Valo wrote:
> >
> >>
> >> Dmitry Baryshkov writes:
> >>
> >> > On Mon, 4 Dec 2023 at 14:56, Kalle Valo wrote:
> &
On Mon, 4 Dec 2023 at 18:14, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > On Mon, 4 Dec 2023 at 14:56, Kalle Valo wrote:
> >
> >>
> >> Hi Dmitry,
> >>
> >> Dmitry Baryshkov writes:
> >>
> >> > I
On Mon, 4 Dec 2023 at 16:49, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > I just wanted to check whether you have plans to update ath10k /
> > ath11k board data files. The last update was IIRC 9 months ago.
>
> It is very high on my todo list. I was s
Hello Kalle,
I just wanted to check whether you have plans to update ath10k /
ath11k board data files. The last update was IIRC 9 months ago.
--
With best wishes
Dmitry
On Mon, 4 Dec 2023 at 14:56, Kalle Valo wrote:
>
> Hi Dmitry,
>
> Dmitry Baryshkov writes:
>
> > I wanted to ask your opinion regarding one of the issues we stumbled
> > upon on the Qualcomm RB1 and RB2 platforms. These platforms use ath10k
> > snoc
Hello,
I wanted to ask your opinion regarding one of the issues we stumbled
upon on the Qualcomm RB1 and RB2 platforms. These platforms use ath10k
snoc (WCN3990) WiFi "card". We noticed the following messages being
spawned on the console, which I traced it to the
Hello Kalle,
We'd like to ask for inclusion of the board file for the Qualcomm
SDM845 MTP board. It is a hardware development kit manufactured by
Qualcomm, using the Snapdragon SDM845 SoC and a variant of wcn3990
BT/WiFi chip.
Following the questions from the ath10k wiki page:
* description for
On Sat, 26 Aug 2023 at 08:44, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > Default to 'board.bin' for the legacy board data file, in case the
> > hw_params array doesn't list hw-specific board data file name (e.g. for
> > WCN3990).
> >
> > Signed-
Default to 'board.bin' for the legacy board data file, in case the
hw_params array doesn't list hw-specific board data file name (e.g. for
WCN3990).
Signed-off-by: Dmitry Baryshkov
---
drivers/net/wireless/ath/ath10k/core.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff
Hello Kalle,
We'd like to ask for inclusion of the board file for the Qualcomm
Robotics RB2 platform. It is
an IOT platform manufactured by Thundercomm, using the Snapdragon QRB4210 SoC.
Following the questions from the ath10k wiki page:
* description for what hardware this is
- It is an
Hello Kalle,
We'd like to ask for inclusion of the board file for the Qualcomm
Robotics RB1 platform. It is
an IOT platform manufactured by Thundercomm, using the Snapdragon QRB2210 SoC.
Following the questions from the ath10k wiki page:
* description for what hardware this is
- It is an
On Wed, 2 Aug 2023 at 19:45, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > On 02/08/2023 13:28, Kalle Valo wrote:
> >
> >> Dmitry Baryshkov writes:
> >>
> >>> On 24/07/2023 22:38, Dmitry Baryshkov wrote:
> >>>> H
On 02/08/2023 13:28, Kalle Valo wrote:
Dmitry Baryshkov writes:
On 24/07/2023 22:38, Dmitry Baryshkov wrote:
Hello Kalle, colle
Yet-another firmware question (I remember the standard answer of not
using firmware not coming from your side). I see that for
wcn3990/hw1.0 we have wlanmdsp.mbn
On 24/07/2023 22:38, Dmitry Baryshkov wrote:
Hello Kalle, colle
Yet-another firmware question (I remember the standard answer of not
using firmware not coming from your side). I see that for wcn3990/hw1.0
we have wlanmdsp.mbn with the version WLAN.HL.2.0-01387-QCAHLSWMTPLZ-1
We have got
Hello Kalle, colle
Yet-another firmware question (I remember the standard answer of not
using firmware not coming from your side). I see that for wcn3990/hw1.0
we have wlanmdsp.mbn with the version WLAN.HL.2.0-01387-QCAHLSWMTPLZ-1
We have got the newer wlanmdsp.mbn released under
On Wed, 12 Apr 2023 at 12:36, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > Hi Kalle,
> >
> > On 05/04/2023 16:07, Kalle Valo wrote:
> >> Hi,
> >>
> >> Here's a pull request for ath10k and ath11k. For ath10k we have lots of
> >&g
Hi Kalle,
On 05/04/2023 16:07, Kalle Valo wrote:
Hi,
Here's a pull request for ath10k and ath11k. For ath10k we have lots of
board file updates in multiple hardware families. For ath11k we have new
firmware branches for QCN9074, IPQ6018 and IPQ8074. WCN6750 also got a
firmware update and
On Wed, 22 Mar 2023 at 07:54, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> >> ath11k/IPQ5018/hw1.0/Notice.txt | 4094
> >> ++
> >> ath11k/IPQ5018/hw1.0/board-2.bin | Bin 0 -> 524564 byte
Hello Kalle,
On 15/02/2023 11:17, Kalle Valo wrote:
Hi,
Here's a new pull request for ath10k and ath11k. We have new hardware
IPQ5018 and various updates for existing hardware. Especially many have
requested the firmware update for WCN6855 which seems to fix an
important suspend problem.
On Fri, 17 Mar 2023 at 13:55, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > We'd like to ask for inclusion of the board file for the Lenovo Yoga
> > C630 laptop. It is
> > a WfA laptop using the Snapdragon SDM850 SoC.
> > Following the qu
On Mon, 20 Feb 2023 at 07:59, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > On 07/10/2022 15:22, Dmitry Baryshkov wrote:
> >> We'd like to ask for inclusion of the board file for the Lenovo Yoga
> >> C630 laptop. It is
> >> a WfA laptop using th
Hello Kalle,
On 07/10/2022 15:22, Dmitry Baryshkov wrote:
We'd like to ask for inclusion of the board file for the Lenovo Yoga
C630 laptop. It is
a WfA laptop using the Snapdragon SDM850 SoC.
I noticed that you've updated the WCN3990's board-2.bin, but this file
was not included
e worth sending a refresh :)
Yes, I hope to return to it eventually. I just had no time for it lately.
> On Wed, Oct 06, 2021 at 06:53:52AM +0300, Dmitry Baryshkov wrote:
> > This is a proposed power sequencer subsystem. This is a
> > generification of the MMC pwrseq code. T
Hi,
We'd like to ask for inclusion of the board file for the Lenovo Yoga
C630 laptop. It is
a WfA laptop using the Snapdragon SDM850 SoC.
Following the questions from the ath10k wiki page:
* description for what hardware this is
- It is an SDM845-based platform (SDM850)
- It uses wcn3990 chip as
On Wed, 1 Jun 2022 at 09:44, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > On Fri, 29 Apr 2022 at 08:44, Kalle Valo wrote:
> >>
> >> Dmitry Baryshkov writes:
> >>
> >> > Hi Kalle,
> >> >
> >> > On 27/04/20
On Fri, 29 Apr 2022 at 08:44, Kalle Valo wrote:
>
> Dmitry Baryshkov writes:
>
> > Hi Kalle,
> >
> > On 27/04/2022 11:32, Kalle Valo wrote:
> >> Add support for QCN9074 and WCN6750 ath11k hardware families. Also
> >> there are several updates t
Hi Kalle,
On 27/04/2022 11:32, Kalle Valo wrote:
Add support for QCN9074 and WCN6750 ath11k hardware families. Also
there are several updates to existing firmwares and board files for both ath10k
and ath11k.
Please let me know if there are any problems.
I noticed that this pull request
Hi,
We'd like to ask for inclusion of the board file for the Qualcomm
Robotics RB3 Platform also known as Thunderomm Dragonboard 845c. It is
a development platform based on the Qualcomm SDM845 SoC.
Following the questions from the ath10k wiki page:
* description for what hardware this is
- It is
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/sdm845-db845c.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845-db845c.dts
b/arch/arm64/boot/dts/qcom/sdm845-db845c.dts
index 13f80a0b6faa..f49de3913dd5 100644
--- a/arch/arm64/boot/dts/qcom/sdm845-
On Sat, 2 Apr 2022 at 14:09, Dmitry Baryshkov
wrote:
> We'd like to ask for inclusion of the board file for the 96boards
> DragonBoard 820c. It is a development board is based on the Qualcomm®
> Snapdragon 820E embedded platform (APQ8096).
> Following the questions from the ath1
Hi,
We'd like to ask for inclusion of the board file for the 96boards
DragonBoard 820c. It is a development board is based on the Qualcomm®
Snapdragon 820E embedded platform (APQ8096).
Following the questions from the ath10k wiki page:
* description for what hardware this is
- It is an APQ8096
On 28/10/2021 00:53, Rob Herring wrote:
On Tue, Oct 26, 2021 at 9:42 AM Dmitry Baryshkov
wrote:
On 26/10/2021 15:53, Rob Herring wrote:
On Wed, Oct 06, 2021 at 06:53:53AM +0300, Dmitry Baryshkov wrote:
Add device tree bindings for the new power sequencer subsystem.
Consumers would reference
On 26/10/2021 15:53, Rob Herring wrote:
On Wed, Oct 06, 2021 at 06:53:53AM +0300, Dmitry Baryshkov wrote:
Add device tree bindings for the new power sequencer subsystem.
Consumers would reference pwrseq nodes using "foo-pwrseq" properties.
Providers would use '#pwrseq-cells' property
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/qrb5165-rb5.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/qcom/qrb5165-rb5.dts
b/arch/arm64/boot/dts/qcom/qrb5165-rb5.dts
index 326330f528fc..0c347cb6f8e0 100644
--- a/arch/arm64/boot/dts/qcom/qrb5165-rb5
Signed-off-by: Dmitry Baryshkov
---
drivers/bluetooth/hci_qca.c | 260 +---
1 file changed, 37 insertions(+), 223 deletions(-)
diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c
index 53deea2eb7b4..1e4416916533 100644
--- a/drivers/bluetooth
Use bus-pwrseq device tree node to power up the devices on the bus. This
is to be rewritten with the proper code parsing the device tree and
powering up individual devices.
Signed-off-by: Dmitry Baryshkov
---
drivers/pci/controller/dwc/pcie-qcom.c | 13 +
1 file changed, 13
On DB845c board WiFi/BT chip can use both RF channels/antennas, so add
vddch1-supply property.
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/sdm845-db845c.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845-db845c.dts
b/arch/arm64/boot
Switch sdm845-db845c device tree to use new power sequencer driver
rather than separate regulators.
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/sdm845-db845c.dts | 21 ++---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 6 ++
2 files changed, 20 insertions
Add support for the bluetooth part of the QCA6391 BT+WiFi chip present
on the RB5 board. WiFi is not supported yet, as it requires separate
handling of the PCIe device power.
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/qrb5165-rb5.dts | 50
1 file
Power sequencing for Qualcomm WiFi+BT chipsets are being reworked to use
pwrseq rather than individually handling all the regulators. Add support
for pwrseq to ath10k SNOC driver.
Signed-off-by: Dmitry Baryshkov
---
drivers/net/wireless/ath/ath10k/snoc.c | 45 +-
drivers
bindings.
Signed-off-by: Dmitry Baryshkov
---
drivers/power/pwrseq/pwrseq_qca.c | 155 +-
1 file changed, 154 insertions(+), 1 deletion(-)
diff --git a/drivers/power/pwrseq/pwrseq_qca.c
b/drivers/power/pwrseq/pwrseq_qca.c
index c15508cc80d2..f237cf2f1880 100644
Power sequencer support requires changing device tree. To ease migration
to pwrseq, add support for pwrseq 'fallback': let the power sequencer
driver register special handler that if matched will create pwrseq
instance basing on the consumer device tree data.
Signed-off-by: Dmitry Baryshkov
manage pins, different requirements, regulator types, move
this knowledge to the common power sequencer driver. Currently original
drivers are not stripped from the regulator code, this will be done
later (to keep compatibility with the old device trees).
Signed-off-by: Dmitry Baryshkov
---
drivers
Drop old MMC pwrseq code and use new pwrseq subsystem instead.
Individual drivers are already ported to new subsystem.
Signed-off-by: Dmitry Baryshkov
---
drivers/mmc/core/Makefile | 1 -
drivers/mmc/core/core.c | 9 ++-
drivers/mmc/core/host.c | 8 ++-
drivers/mmc/core/mmc.c
Port MMC's all pwrseq drivers to new pwrseq subsystem.
Signed-off-by: Dmitry Baryshkov
---
.../pwrseq}/mmc-pwrseq-emmc.yaml | 6 +-
.../pwrseq}/mmc-pwrseq-sd8787.yaml| 6 +-
.../pwrseq}/mmc-pwrseq-simple.yaml| 6 +-
drivers/mmc/core/Kconfig
Provide of_pwrseq_xlate_onecell() - a helper easing implementation of
power sequencers using one cell to determine pwrseq instance to return.
Signed-off-by: Dmitry Baryshkov
---
drivers/power/pwrseq/core.c | 26 ++
include/linux/pwrseq/driver.h | 12
2
Basing on MMC's pwrseq support code, add separate power sequencer
subsystem. It will be used by other drivers to handle device power up
requirements.
Signed-off-by: Dmitry Baryshkov
---
Documentation/driver-api/index.rst | 1 +
Documentation/driver-api/pwrseq.rst | 77 +
drivers/power
Add device tree bindings for the new power sequencer subsystem.
Consumers would reference pwrseq nodes using "foo-pwrseq" properties.
Providers would use '#pwrseq-cells' property to declare the amount of
cells in the pwrseq specifier.
Signed-off-by: Dmitry Baryshkov
---
.../bind
This is a proposed power sequencer subsystem. This is a
generification of the MMC pwrseq code. The subsystem tries to abstract
the idea of complex power-up/power-down/reset of the devices.
The primary set of devices that promted me to create this patchset is
the Qualcomm BT+WiFi family of chips.
Hi Steev,
On Tue, 14 Sept 2021 at 02:39, Steev Klimaszewski wrote:
>
>
> On 8/29/21 8:12 AM, Dmitry Baryshkov wrote:
> > This is the second RFC on the proposed power sequencer subsystem. This
> > is a generification of the MMC pwrseq code. The subsystem tries to
> > a
On 10/09/2021 13:02, Ulf Hansson wrote:
On Sun, 29 Aug 2021 at 15:13, Dmitry Baryshkov
wrote:
Basing on MMC's pwrseq support code, add separate power sequencer
subsystem. It will be used by other drivers to handle device power up
requirements.
This is far too vague. You are suggesting
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/qrb5165-rb5.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/qcom/qrb5165-rb5.dts
b/arch/arm64/boot/dts/qcom/qrb5165-rb5.dts
index 326330f528fc..0c347cb6f8e0 100644
--- a/arch/arm64/boot/dts/qcom/qrb5165-rb5
On DB845c board WiFi/BT chip can use both RF channels/antennas, so add
vddch1-supply property.
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/sdm845-db845c.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845-db845c.dts
b/arch/arm64/boot
Use bus-pwrseq device tree node to power up the devices on the bus. This
is to be rewritten with the proper code parsing the device tree and
powering up individual devices.
Signed-off-by: Dmitry Baryshkov
---
drivers/pci/controller/dwc/pcie-qcom.c | 13 +
1 file changed, 13
Power sequencing for Qualcomm WiFi+BT chipsets are being reworked to use
pwrseq rather than individually handling all the regulators. Add support
for pwrseq to ath10k SNOC driver.
Signed-off-by: Dmitry Baryshkov
---
drivers/net/wireless/ath/ath10k/snoc.c | 45 +-
drivers
Signed-off-by: Dmitry Baryshkov
---
drivers/bluetooth/hci_qca.c | 260 +---
1 file changed, 37 insertions(+), 223 deletions(-)
diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c
index 53deea2eb7b4..1e4416916533 100644
--- a/drivers/bluetooth
Port MMC's all pwrseq drivers to new pwrseq subsystem.
Signed-off-by: Dmitry Baryshkov
---
.../pwrseq}/mmc-pwrseq-emmc.yaml | 0
.../pwrseq}/mmc-pwrseq-sd8787.yaml| 0
.../pwrseq}/mmc-pwrseq-simple.yaml| 0
drivers/mmc/core/Kconfig
Add support for the bluetooth part of the QCA6391 BT+WiFi chip present
on the RB5 board. WiFi is not supported yet, as it requires separate
handling of the PCIe device power.
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/qrb5165-rb5.dts | 50
1 file
1 - 100 of 127 matches
Mail list logo
