From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH 4/5] ath10k: split ce irq/handler setup
Date: Tue, 19 Aug 2014 15:37:23 +0300 [thread overview]
Message-ID: <87a970ac58.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQmgcBKfNKrAH5jKsehemx7rTxHHXMr8Qf+ctgfZpVj0Dg@mail.gmail.com> (Michal Kazior's message of "Tue, 19 Aug 2014 14:30:39 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> On 14 August 2014 10:40, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Michal Kazior <michal.kazior@tieto.com> writes:
>>
>>> It doesn't make much sense to overwrite send_cb
>>> and recv_cb callbacks over and over again whenever
>>> transport starts. Just make sure to unmask copy
>>> engine interrupts when starting.
>>>
>>> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
>>
>> The patch looks, just a followup question for the future:
>>
>>> @@ -1674,7 +1639,9 @@ static int ath10k_pci_ce_init(struct ath10k *ar)
>>> pipe_info->hif_ce_state = ar;
>>> attr = &host_ce_config_wlan[pipe_num];
>>>
>>> - ret = ath10k_ce_init_pipe(ar, pipe_num, attr);
>>> + ret = ath10k_ce_init_pipe(ar, pipe_num, attr,
>>> + ath10k_pci_ce_send_done,
>>> + ath10k_pci_ce_recv_data);
>>
>> As we call ath10k_ce_init_pipe() only once and seem to have only one set
>> of functions, why even bother bother with function pointers? What if we
>> just call the functions directly?
>
> Yeah, we can remove this abstraction later. I don't there's anything
> depending on it anymore.
Good, again something for a rainy day :)
I added it to the TODO list (which we should cleanup as well):
http://wireless.kernel.org/en/users/Drivers/ath10k/todo
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 4/5] ath10k: split ce irq/handler setup
Date: Tue, 19 Aug 2014 15:37:23 +0300 [thread overview]
Message-ID: <87a970ac58.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQmgcBKfNKrAH5jKsehemx7rTxHHXMr8Qf+ctgfZpVj0Dg@mail.gmail.com> (Michal Kazior's message of "Tue, 19 Aug 2014 14:30:39 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> On 14 August 2014 10:40, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Michal Kazior <michal.kazior@tieto.com> writes:
>>
>>> It doesn't make much sense to overwrite send_cb
>>> and recv_cb callbacks over and over again whenever
>>> transport starts. Just make sure to unmask copy
>>> engine interrupts when starting.
>>>
>>> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
>>
>> The patch looks, just a followup question for the future:
>>
>>> @@ -1674,7 +1639,9 @@ static int ath10k_pci_ce_init(struct ath10k *ar)
>>> pipe_info->hif_ce_state = ar;
>>> attr = &host_ce_config_wlan[pipe_num];
>>>
>>> - ret = ath10k_ce_init_pipe(ar, pipe_num, attr);
>>> + ret = ath10k_ce_init_pipe(ar, pipe_num, attr,
>>> + ath10k_pci_ce_send_done,
>>> + ath10k_pci_ce_recv_data);
>>
>> As we call ath10k_ce_init_pipe() only once and seem to have only one set
>> of functions, why even bother bother with function pointers? What if we
>> just call the functions directly?
>
> Yeah, we can remove this abstraction later. I don't there's anything
> depending on it anymore.
Good, again something for a rainy day :)
I added it to the TODO list (which we should cleanup as well):
http://wireless.kernel.org/en/users/Drivers/ath10k/todo
--
Kalle Valo
next prev parent reply other threads:[~2014-08-19 12:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 9:04 [PATCH 0/5] ath10k: fixes 2014-08-07, part 2 Michal Kazior
2014-08-07 9:04 ` Michal Kazior
2014-08-07 9:04 ` [PATCH 1/5] ath10k: fix legacy irq workaround Michal Kazior
2014-08-07 9:04 ` Michal Kazior
2014-08-07 9:04 ` [PATCH 2/5] ath10k: setup irq method in probe Michal Kazior
2014-08-07 9:04 ` Michal Kazior
2014-08-13 13:48 ` Kalle Valo
2014-08-13 13:48 ` Kalle Valo
2014-08-18 13:47 ` Michal Kazior
2014-08-18 13:47 ` Michal Kazior
2014-08-19 11:47 ` Kalle Valo
2014-08-19 11:47 ` Kalle Valo
2014-08-07 9:04 ` [PATCH 3/5] ath10k: remove early irq handling Michal Kazior
2014-08-07 9:04 ` Michal Kazior
2014-08-13 14:09 ` Kalle Valo
2014-08-13 14:09 ` Kalle Valo
2014-08-18 13:51 ` Michal Kazior
2014-08-18 13:51 ` Michal Kazior
2014-08-07 9:04 ` [PATCH 4/5] ath10k: split ce irq/handler setup Michal Kazior
2014-08-07 9:04 ` Michal Kazior
2014-08-14 8:40 ` Kalle Valo
2014-08-14 8:40 ` Kalle Valo
2014-08-19 12:30 ` Michal Kazior
2014-08-19 12:30 ` Michal Kazior
2014-08-19 12:37 ` Kalle Valo [this message]
2014-08-19 12:37 ` Kalle Valo
2014-08-07 9:04 ` [PATCH 5/5] ath10k: unmask ce irqs after posting rx buffers Michal Kazior
2014-08-07 9:04 ` Michal Kazior
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=87a970ac58.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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 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.