linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "ap420073 ." <ap420073@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] rtlwifi: rtl8192cu: Add case in rtl92cu_get_hw_reg
Date: Wed, 25 Feb 2015 13:12:03 -0600	[thread overview]
Message-ID: <54EE1E83.3040603@lwfinger.net> (raw)
In-Reply-To: <CAMArcTW+UM62th3CZ-hhmPiH0-hzo4-f6qB2O9q7ktK4tLtuOQ@mail.gmail.com>

On 02/25/2015 12:59 PM, ap420073 . wrote:
> 2015-02-26 3:33 GMT+09:00 Larry Finger <Larry.Finger@lwfinger.net>:
>> On 02/25/2015 11:58 AM, Taehee Yoo wrote:
>>>
>>> rtl_op_stop get wowlan state but rtl92cu_get_hw_reg has not process.
>>>
>>> Signed-off-by: Taehee Yoo <ap420073@gmail.com>
>>
>>
>> Has this been tested? I am not aware that the RTL8192CU firmware could
>> handle WOWLAN.
>>
>> Larry
>>
>>
>>> ---
>>>    drivers/net/wireless/rtlwifi/rtl8192cu/hw.c | 6 ++++++
>>>    1 file changed, 6 insertions(+)
>>>
>>> diff --git a/drivers/net/wireless/rtlwifi/rtl8192cu/hw.c
>>> b/drivers/net/wireless/rtlwifi/rtl8192cu/hw.c
>>> index fe4b699..f6ad959 100644
>>> --- a/drivers/net/wireless/rtlwifi/rtl8192cu/hw.c
>>> +++ b/drivers/net/wireless/rtlwifi/rtl8192cu/hw.c
>>> @@ -1589,6 +1589,12 @@ void rtl92cu_get_hw_reg(struct ieee80211_hw *hw, u8
>>> variable, u8 *val)
>>>          case HW_VAR_DATA_FILTER:
>>>                  *((u16 *) (val)) = rtl_read_word(rtlpriv, REG_RXFLTMAP2);
>>>                  break;
>>> +       case HAL_DEF_WOWLAN:
>>> +               if (ppsc->wo_wlan_mode)
>>> +                       *((bool *)(val)) = true;
>>> +               else
>>> +                       *((bool *)(val)) = false;
>>> +               break;
>>>          default:
>>>                  RT_TRACE(rtlpriv, COMP_ERR, DBG_EMERG,
>>>                           "switch case not processed\n");
>>>
>>
>
> As far as i know, rtl8192cu is not support WOWLAN.
> in rtl8192cu, this code is no effect. so, It is care of unnecessary
> debug message.

That is what I thought. In that case, the new code should be

	case HAL_DEF_WOWLAN:
		break;

Larry


  reply	other threads:[~2015-02-25 19:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25 17:58 [PATCH] rtlwifi: rtl8192cu: Add case in rtl92cu_get_hw_reg Taehee Yoo
2015-02-25 18:33 ` Larry Finger
2015-02-25 18:59   ` ap420073 .
2015-02-25 19:12     ` Larry Finger [this message]
2015-02-25 19:24       ` ap420073 .
  -- strict thread matches above, loose matches on Subject: below --
2015-02-25 19:34 Taehee Yoo
2015-02-25 20:23 ` Larry Finger

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=54EE1E83.3040603@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=ap420073@gmail.com \
    --cc=linux-wireless@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).