[PATCH v3] ath10k: add 'cryptmode' param to support raw tx injection and software crypto

[Liu CF/TW]

On Thu, Jun 11, 2015 at 7:03 AM, Kalle Valo <kvalo at qca.qualcomm.com> wrote:
> Liu CF/TW <cfliu.tw at gmail.com> writes:
>
>> This change supports hardware crypto engine bypass by enabling raw
>> Rx/Tx encap mode. This enables use cases such as software crypto and raw
>> tx injection. This change introduces a new module param 'cryptmode'.
>
> [...]
>
>> --- a/drivers/net/wireless/ath/ath10k/debug.c
>> +++ b/drivers/net/wireless/ath/ath10k/debug.c
>> @@ -124,7 +124,7 @@ EXPORT_SYMBOL(ath10k_info);
>>
>>  void ath10k_print_driver_info(struct ath10k *ar)
>>  {
>> -     ath10k_info(ar, "%s (0x%08x, 0x%08x%s%s%s) fw %s api %d htt %d.%d wmi %d cal %s max_sta %d\n",
>> +     ath10k_info(ar, "%s (0x%08x, 0x%08x%s%s%s) fw %s api %d htt %d.%d wmi %d cal %s max_sta %d flags 0x%lu\n",
>>                   ar->hw_params.name,
>>                   ar->target_version,
>>                   ar->chip_id,
>> @@ -138,7 +138,8 @@ void ath10k_print_driver_info(struct ath10k *ar)
>>                   ar->htt.target_version_minor,
>>                   ar->wmi.op_version,
>>                   ath10k_cal_mode_str(ar->cal_mode),
>> -                 ar->max_num_stations);
>> +                 ar->max_num_stations,
>> +                 ar->dev_flags);
>
> What's the goal here? Printing a bitmap in hex is just gibberish, people
> would always have to count the bits etc to get anything useful
> information out from that print.
>
> I would prefer the messages in more readable format. For example, if
> idea is to show if cryptmode is enabled or not can't we just directly
> print that like with format "cryptmode %d"?

Sure. will do in v4.

>
> --
> Kalle Valo