public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: xx777 <zenmchen@gmail.com>
To: zenmchen@gmail.com
Cc: Jes.Sorensen@gmail.com, kvalo@kernel.org,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	pkshih@realtek.com, rtl8821cerfe2@gmail.com
Subject: Re: [PATCH] wifi: rtl8xxxu: fix LED control code of RTL8192FU
Date: Mon, 11 Sep 2023 22:41:45 +0800	[thread overview]
Message-ID: <20230911144155.5871-1-zenmchen@gmail.com> (raw)
In-Reply-To: <20230910002038.56362-1-zenmchen@gmail.com>

Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
>
> Can you explain in the commit message why you changed the
> LED_ON and LED_OFF branches? It's not obvious to me and they
> don't have anything to do with the hardware-controlled blinking.
>

Hi,

Sorry that I didn't explain this clearly.
After some researches these days, I came to some conclusions:

1. The LED of MERCURY MW310UH and COMFAST CF-826F seems to be controlled by
   REG_LEDCFG1, and currently rtl8xxxu controls the LED through writing
   some suitable values to this register, so MW310UH and CF-826F work fine
   with rtl8xxxu.

2. The LED of ASUS USB-N13 C1 seems to be controlled by another register 
   "REG_LEDCFG0" for unknown reason, so when I write 1 or 2 to 
   /sys/class/leds/rtl8xxxu-usbX-Y/brightness, the LED doesn't turn on 
   or blink because the register "REG_LEDCFG0" is not filled with a suitable 
   value, This is why I changed the LED_ON and LED_OFF branches.

I will modify the commit message in the next version of patch, thanks.

  parent reply	other threads:[~2023-09-11 20:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10  0:20 [PATCH] wifi: rtl8xxxu: fix LED control code of RTL8192FU Zenm Chen
2023-09-11  3:45 ` Ping-Ke Shih
2023-09-11 12:41 ` Bitterblue Smith
2023-09-11 14:41 ` xx777 [this message]
2023-09-12  4:54 ` Zenm Chen

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=20230911144155.5871-1-zenmchen@gmail.com \
    --to=zenmchen@gmail.com \
    --cc=Jes.Sorensen@gmail.com \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=rtl8821cerfe2@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox