From: Govind Singh <govinds@qti.qualcomm.com> To: Kalle Valo <kvalo@codeaurora.org>, Erik Stromdahl <erik.stromdahl@gmail.com> Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>, "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>, Rakesh Pillai <pillair@qti.qualcomm.com> Subject: RE: [RFC v3 03/11] ath10k: per target configurablity of various items Date: Mon, 8 Jan 2018 14:03:40 +0000 [thread overview] Message-ID: <ab162551fa9949daadc870edc9bfe792@aphydexm01b.ap.qualcomm.com> (raw) In-Reply-To: <87wp0s31sw.fsf@kamboji.qca.qualcomm.com> >> A good point, I didn't thought of that during review. No time to investi= gate this right now, but maybe Rakesh and Govind (CCed) can comment? Yes, ar->max_num_peers needs to be assigned with ar->hw_param->num_peers. T= his can create mismatch for wcn3990 target if we=20 create multiple peers( TARGET_HL_10_TLV_NUM_PEERS vs TARGET_TLV_NUM_PEERS).= We will fix this and raise this as separate change. >>> Btw, what the heck is SNOC anyway? SNOC is system NOC(network on chip). WCN3990 is integrated chipset connecte= d over SNOC and only RF part is discrete to the SoC. BR, Govind -----Original Message----- From: Kalle Valo [mailto:kvalo@codeaurora.org]=20 Sent: Monday, January 8, 2018 7:12 PM To: Erik Stromdahl <erik.stromdahl@gmail.com> Cc: linux-wireless@vger.kernel.org; ath10k@lists.infradead.org; Rakesh Pill= ai <pillair@qti.qualcomm.com>; Govind Singh <govinds@qti.qualcomm.com> Subject: Re: [RFC v3 03/11] ath10k: per target configurablity of various it= ems Erik Stromdahl <erik.stromdahl@gmail.com> writes: > On 2017-12-22 16:19, Kalle Valo wrote: > >> I was a bit torn about this, I definitely see the need for this but=20 >> on the other hand it creates duplicate data (for example two entries=20 >> for >> QCA9377 chip). I guess this is the right approach, at least I cannot=20 >> come up anything better. >> >> But this patch should be split into two: >> >> 1) add bus field to struct ath10k_hw_params >> >> 2) add max_num_peers field to struct ath10k_hw_params >> >> And it seems 2) is already implemented in commit 9f2992fea580 ("ath10k: >> wmi: get wmi init parameter values from hw params"), so hopefully we=20 >> only need 1) anymore. >> > > Before commit 9f2992fea580a48135591873e5e3ac7e01444207, > TARGET_TLV_NUM_PEERS was used both in the WMI TLV init command and as=20 > the value of *max_num_peers* in *struct ath10k* (ar->max_num_peers). > > commit 9f2992fea580a48135591873e5e3ac7e01444207 does not set > *ar->max_num_peers* to the value of *ar->hw_param->num_peers*. > > Is this correct? > > As I see it, there is a possible mismatch between what is written to=20 > the device in the WMI init message and the value of *ar->max_num_peers*. > > Do we still need *max_num_peers* in *struct ath10k* now that we have=20 > the > *num_peers* member in *struct ath10k_hw_params*? A good point, I didn't thought of that during review. No time to investigat= e this right now, but maybe Rakesh and Govind (CCed) can comment? > I am currently rewriting my HL patches and I was thinking about adding=20 > a separate patch related to this. Yeah, a separate patch to sort that out is a good idea. >>> --- a/drivers/net/wireless/ath/ath10k/core.c >>> +++ b/drivers/net/wireless/ath/ath10k/core.c >>> @@ -1663,9 +1663,19 @@ static int ath10k_init_hw_params(struct ath10k *= ar) >>> for (i =3D 0; i < ARRAY_SIZE(ath10k_hw_params_list); i++) { >>> hw_params =3D &ath10k_hw_params_list[i]; >>> - if (hw_params->id =3D=3D ar->target_version && >>> - hw_params->dev_id =3D=3D ar->dev_id) >>> - break; >>> + if (ar->is_high_latency) { >>> + /* High latency devices will use different fw depending >>> + * on if it is a USB or SDIO device. >>> + */ >>> + if (hw_params->bus =3D=3D ar->hif.bus && >>> + hw_params->id =3D=3D ar->target_version && >>> + hw_params->dev_id =3D=3D ar->dev_id) >>> + break; >>> + } else { >>> + if (hw_params->id =3D=3D ar->target_version && >>> + hw_params->dev_id =3D=3D ar->dev_id) >>> + break; >>> + } >> >> I don't like the is_high_latency test here at all. The bus field=20 >> should be checked with all entries, not just high latency ones. And=20 >> because of this even most of the hw_param bus field entries were not ini= tialised. >> >> So only thing to do is to initialise the bus field for all the=20 >> entries and the ugly test here can be removed. Just remember that=20 >> QCA4019 uses AHB, I think all the rest is PCI. Or do we have AHB devices= supported? > > I noticed that there has been introduced a new bus type (SNOC). > Do you know which devices are SNOC devices? SNOC is for wcn3990. > Btw, what the heck is SNOC anyway? I have forgetten already what the acronym meant but it's basically some sor= t of shared memory communication method with the firmware. -- Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Govind Singh <govinds@qti.qualcomm.com> To: Kalle Valo <kvalo@codeaurora.org>, Erik Stromdahl <erik.stromdahl@gmail.com> Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>, "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>, Rakesh Pillai <pillair@qti.qualcomm.com> Subject: RE: [RFC v3 03/11] ath10k: per target configurablity of various items Date: Mon, 8 Jan 2018 14:03:40 +0000 [thread overview] Message-ID: <ab162551fa9949daadc870edc9bfe792@aphydexm01b.ap.qualcomm.com> (raw) In-Reply-To: <87wp0s31sw.fsf@kamboji.qca.qualcomm.com> >> A good point, I didn't thought of that during review. No time to investigate this right now, but maybe Rakesh and Govind (CCed) can comment? Yes, ar->max_num_peers needs to be assigned with ar->hw_param->num_peers. This can create mismatch for wcn3990 target if we create multiple peers( TARGET_HL_10_TLV_NUM_PEERS vs TARGET_TLV_NUM_PEERS). We will fix this and raise this as separate change. >>> Btw, what the heck is SNOC anyway? SNOC is system NOC(network on chip). WCN3990 is integrated chipset connected over SNOC and only RF part is discrete to the SoC. BR, Govind -----Original Message----- From: Kalle Valo [mailto:kvalo@codeaurora.org] Sent: Monday, January 8, 2018 7:12 PM To: Erik Stromdahl <erik.stromdahl@gmail.com> Cc: linux-wireless@vger.kernel.org; ath10k@lists.infradead.org; Rakesh Pillai <pillair@qti.qualcomm.com>; Govind Singh <govinds@qti.qualcomm.com> Subject: Re: [RFC v3 03/11] ath10k: per target configurablity of various items Erik Stromdahl <erik.stromdahl@gmail.com> writes: > On 2017-12-22 16:19, Kalle Valo wrote: > >> I was a bit torn about this, I definitely see the need for this but >> on the other hand it creates duplicate data (for example two entries >> for >> QCA9377 chip). I guess this is the right approach, at least I cannot >> come up anything better. >> >> But this patch should be split into two: >> >> 1) add bus field to struct ath10k_hw_params >> >> 2) add max_num_peers field to struct ath10k_hw_params >> >> And it seems 2) is already implemented in commit 9f2992fea580 ("ath10k: >> wmi: get wmi init parameter values from hw params"), so hopefully we >> only need 1) anymore. >> > > Before commit 9f2992fea580a48135591873e5e3ac7e01444207, > TARGET_TLV_NUM_PEERS was used both in the WMI TLV init command and as > the value of *max_num_peers* in *struct ath10k* (ar->max_num_peers). > > commit 9f2992fea580a48135591873e5e3ac7e01444207 does not set > *ar->max_num_peers* to the value of *ar->hw_param->num_peers*. > > Is this correct? > > As I see it, there is a possible mismatch between what is written to > the device in the WMI init message and the value of *ar->max_num_peers*. > > Do we still need *max_num_peers* in *struct ath10k* now that we have > the > *num_peers* member in *struct ath10k_hw_params*? A good point, I didn't thought of that during review. No time to investigate this right now, but maybe Rakesh and Govind (CCed) can comment? > I am currently rewriting my HL patches and I was thinking about adding > a separate patch related to this. Yeah, a separate patch to sort that out is a good idea. >>> --- a/drivers/net/wireless/ath/ath10k/core.c >>> +++ b/drivers/net/wireless/ath/ath10k/core.c >>> @@ -1663,9 +1663,19 @@ static int ath10k_init_hw_params(struct ath10k *ar) >>> for (i = 0; i < ARRAY_SIZE(ath10k_hw_params_list); i++) { >>> hw_params = &ath10k_hw_params_list[i]; >>> - if (hw_params->id == ar->target_version && >>> - hw_params->dev_id == ar->dev_id) >>> - break; >>> + if (ar->is_high_latency) { >>> + /* High latency devices will use different fw depending >>> + * on if it is a USB or SDIO device. >>> + */ >>> + if (hw_params->bus == ar->hif.bus && >>> + hw_params->id == ar->target_version && >>> + hw_params->dev_id == ar->dev_id) >>> + break; >>> + } else { >>> + if (hw_params->id == ar->target_version && >>> + hw_params->dev_id == ar->dev_id) >>> + break; >>> + } >> >> I don't like the is_high_latency test here at all. The bus field >> should be checked with all entries, not just high latency ones. And >> because of this even most of the hw_param bus field entries were not initialised. >> >> So only thing to do is to initialise the bus field for all the >> entries and the ugly test here can be removed. Just remember that >> QCA4019 uses AHB, I think all the rest is PCI. Or do we have AHB devices supported? > > I noticed that there has been introduced a new bus type (SNOC). > Do you know which devices are SNOC devices? SNOC is for wcn3990. > Btw, what the heck is SNOC anyway? I have forgetten already what the acronym meant but it's basically some sort of shared memory communication method with the firmware. -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-01-08 14:03 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-17 19:40 [RFC v3 00/11] ath10k high latency Erik Stromdahl 2017-09-17 19:40 ` Erik Stromdahl 2017-09-17 19:40 ` [RFC v3 01/11] ath10k: high_latency detection Erik Stromdahl 2017-09-17 19:40 ` Erik Stromdahl 2017-12-22 15:06 ` Kalle Valo 2017-12-22 15:06 ` Kalle Valo 2017-09-17 19:40 ` [RFC v3 02/11] ath10k: htt: RX ring config HL support Erik Stromdahl 2017-09-17 19:40 ` Erik Stromdahl 2017-09-17 19:40 ` [RFC v3 03/11] ath10k: per target configurablity of various items Erik Stromdahl 2017-09-17 19:40 ` Erik Stromdahl 2017-12-22 15:19 ` Kalle Valo 2017-12-22 15:19 ` Kalle Valo 2017-12-28 12:43 ` Erik Stromdahl 2017-12-28 12:43 ` Erik Stromdahl 2018-01-08 13:41 ` Kalle Valo 2018-01-08 13:41 ` Kalle Valo 2018-01-08 14:03 ` Govind Singh [this message] 2018-01-08 14:03 ` Govind Singh 2017-09-17 19:40 ` [RFC v3 04/11] ath10k: add start_once support Erik Stromdahl 2017-09-17 19:40 ` Erik Stromdahl 2017-12-22 15:25 ` Kalle Valo 2017-12-22 15:25 ` Kalle Valo 2017-09-17 19:40 ` [RFC v3 05/11] ath10k: htt: High latency TX support Erik Stromdahl 2017-09-17 19:40 ` Erik Stromdahl 2017-12-22 15:26 ` Kalle Valo 2017-12-22 15:26 ` Kalle Valo 2017-09-17 19:40 ` [RFC v3 06/11] ath10k: htt: High latency RX support Erik Stromdahl 2017-09-17 19:40 ` Erik Stromdahl 2017-12-22 15:32 ` Kalle Valo 2017-12-22 15:32 ` Kalle Valo 2017-09-17 19:40 ` [RFC v3 07/11] ath10k: various fixes for high latency devices Erik Stromdahl 2017-09-17 19:40 ` Erik Stromdahl 2017-12-22 15:43 ` Kalle Valo 2017-12-22 15:43 ` Kalle Valo 2017-09-17 19:40 ` [RFC v3 08/11] ath10k: add QCA9377 usb hw_param item Erik Stromdahl 2017-09-17 19:40 ` Erik Stromdahl 2017-12-22 15:46 ` Kalle Valo 2017-12-22 15:46 ` Kalle Valo 2017-12-22 15:49 ` Kalle Valo 2017-12-22 15:49 ` Kalle Valo 2017-09-17 19:40 ` [RFC v3 09/11] ath10k: add QCA9377 sdio " Erik Stromdahl 2017-09-17 19:40 ` Erik Stromdahl 2017-12-22 15:47 ` Kalle Valo 2017-12-22 15:47 ` Kalle Valo 2017-09-17 19:40 ` [RFC v3 10/11] ath10k: wmi: disable softirq's while calling ieee80211_rx Erik Stromdahl 2017-09-17 19:40 ` Erik Stromdahl 2017-12-22 15:47 ` Kalle Valo 2017-12-22 15:47 ` Kalle Valo 2017-09-17 19:40 ` [RFC v3 11/11] ath10k: remove htt pending TX count for high latency Erik Stromdahl 2017-09-17 19:40 ` Erik Stromdahl 2017-12-22 15:55 ` [RFC v3 00/11] ath10k " Kalle Valo 2017-12-22 15:55 ` Kalle Valo
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=ab162551fa9949daadc870edc9bfe792@aphydexm01b.ap.qualcomm.com \ --to=govinds@qti.qualcomm.com \ --cc=ath10k@lists.infradead.org \ --cc=erik.stromdahl@gmail.com \ --cc=kvalo@codeaurora.org \ --cc=linux-wireless@vger.kernel.org \ --cc=pillair@qti.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: linkBe 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.