Linux Input/HID development
 help / color / mirror / Atom feed
From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] HID: nvidia-shield: Select POWER_SUPPLY Kconfig option
Date: Mon, 18 Sep 2023 09:18:00 -0700	[thread overview]
Message-ID: <875y478ngn.fsf@nvidia.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.2309181656130.14216@cbobk.fhfr.pm> (Jiri Kosina's message of "Mon, 18 Sep 2023 16:56:49 +0200 (CEST)")

On Mon, 18 Sep, 2023 16:56:49 +0200 Jiri Kosina <jikos@kernel.org> wrote:
> On Sun, 17 Sep 2023, Rahul Rameshbabu wrote:
>
>> Battery information reported by the driver depends on the power supply 
>> subsystem. Select the required subsystem when the HID_NVIDIA_SHIELD 
>> Kconfig option is enabled.
>> 
>> Fixes: 3ab196f88237 ("HID: nvidia-shield: Add battery support for Thunderstrike")
>> Signed-off-by: Rahul Rameshbabu <rrameshbabu@nvidia.com>
>> ---
>>  drivers/hid/Kconfig | 1 +
>>  1 file changed, 1 insertion(+)
>> 
>> diff --git a/drivers/hid/Kconfig b/drivers/hid/Kconfig
>> index e11c1c803676..dc227f477601 100644
>> --- a/drivers/hid/Kconfig
>> +++ b/drivers/hid/Kconfig
>> @@ -792,6 +792,7 @@ config HID_NVIDIA_SHIELD
>>  	tristate "NVIDIA SHIELD devices"
>>  	depends on USB_HID
>>  	depends on BT_HIDP
>> +	select POWER_SUPPLY
>
> Is there a reason not to do it the standard way using 'depends on', and 
> not vice versa?

I originally used 'depends on' for POWER_SUPPLY. I took a look at
drivers/hid/Kconfig and saw that all modules that depended on
POWER_SUPPLY in the hid subsystem used 'select' instead. I figured I
should follow the trend.

--
Thanks,

Rahul Rameshbabu

  reply	other threads:[~2023-09-18 16:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17 15:18 [PATCH] HID: nvidia-shield: Select POWER_SUPPLY Kconfig option Rahul Rameshbabu
2023-09-18 14:56 ` Jiri Kosina
2023-09-18 16:18   ` Rahul Rameshbabu [this message]
2023-10-04 18:49     ` Jiri Kosina
2023-10-05 23:54       ` Rahul Rameshbabu

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=875y478ngn.fsf@nvidia.com \
    --to=rrameshbabu@nvidia.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@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