linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Barnabás Pőcze" <pobrn@protonmail.com>
To: Roderick Colenbrander <roderick@gaikai.com>
Cc: Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	Chris Ye <lzye@google.com>,
	Roderick Colenbrander <roderick.colenbrander@sony.com>
Subject: Re: [PATCH v2 03/13] HID: playstation: add DualSense battery support.
Date: Thu, 07 Jan 2021 17:50:54 +0000	[thread overview]
Message-ID: <0GfoA1O6YLM6fbSthjBgou-1KitOVn9gI7Y-wDy4ca5qlnQzO2LFknPu25GCB5RlbQcpzt7YUdU_Sf8o_4kHlWkrHmPvF3uFSwImvSe-AA8=@protonmail.com> (raw)
In-Reply-To: <20210102223109.996781-4-roderick@gaikai.com>

Hi


2021. január 2., szombat 23:30 keltezéssel, Roderick Colenbrander írta:

> From: Roderick Colenbrander <roderick.colenbrander@sony.com>
>
> Report DualSense battery status information through power_supply class.
>
> Signed-off-by: Roderick Colenbrander <roderick.colenbrander@sony.com>
> [...]
> @@ -21,6 +21,13 @@
>  /* Base class for playstation devices. */
>  struct ps_device {
>  	struct hid_device *hdev;
> +	spinlock_t lock;

I'm not sure, but isn't a spin_lock_init() missing from the code?


> +
> +	struct power_supply_desc battery_desc;
> +	struct power_supply *battery;
> +	uint8_t battery_capacity;
> +	int battery_status;
> +
>  	uint8_t mac_address[6];
>
>  	int (*parse_report)(struct ps_device *dev, struct hid_report *report, u8 *data, int size);
> [...]
> @@ -136,6 +148,71 @@  static struct input_dev *ps_allocate_input_dev(struct hid_device *hdev, const ch
>  	return input_dev;
>  }
>
> +static enum power_supply_property ps_power_supply_props[] = {
> +	POWER_SUPPLY_PROP_STATUS,
> +	POWER_SUPPLY_PROP_PRESENT,
> +	POWER_SUPPLY_PROP_CAPACITY,
> +	POWER_SUPPLY_PROP_SCOPE

I believe the preferred way is to have a comma after each array/enum/etc. element
unless it is a terminating entry.


> +};
> [...]
> @@ -201,7 +278,9 @@  static int dualsense_parse_report(struct ps_device *ps_dev, struct hid_report *r
>  	struct hid_device *hdev = ps_dev->hdev;
>  	struct dualsense *ds = container_of(ps_dev, struct dualsense, base);
>  	struct dualsense_input_report *ds_report;
> -	uint8_t value;
> +	uint8_t battery_data, battery_capacity, charging_status, value;
> +	int battery_status;
> +	unsigned long flags;
>
>  	/* DualSense in USB uses the full HID report for reportID 1, but
>  	 * Bluetooth uses a minimal HID report for reportID 1 and reports
> @@ -242,12 +321,48 @@  static int dualsense_parse_report(struct ps_device *ps_dev, struct hid_report *r
>  	input_report_key(ds->gamepad, BTN_MODE,   ds_report->buttons[2] & DS_BUTTONS2_PS_HOME);
>  	input_sync(ds->gamepad);
>
> +	battery_data = ds_report->status & DS_STATUS_BATTERY_CAPACITY;
> +	charging_status = (ds_report->status & DS_STATUS_CHARGING) >> DS_STATUS_CHARGING_SHIFT;
> +
> +	switch (charging_status) {
> +	case 0x0:
> +		/* Each unit of battery data corresponds to 10%
> +		 * 0 = 0-9%, 1 = 10-19%, .. and 10 = 100%
> +		 */
> +		battery_capacity = battery_data == 10 ? 100 : battery_data * 10 + 5;

In my opinion `min(battery_data * 10 + 5, 100)` seems cleaner, what do you think?


> +		battery_status = POWER_SUPPLY_STATUS_DISCHARGING;
> +		break;
> +	case 0x1:
> +		battery_capacity = battery_data == 10 ? 100 : battery_data * 10 + 5;
> +		battery_status = POWER_SUPPLY_STATUS_CHARGING;
> +		break;
> +	case 0x2:
> +		battery_capacity = 100;
> +		battery_status = POWER_SUPPLY_STATUS_FULL;
> +		break;
> +	case 0xa: /* voltage or temperature out of range */
> +	case 0xb: /* temperature error */
> +		battery_capacity = 0;
> +		battery_status = POWER_SUPPLY_STATUS_NOT_CHARGING;
> +		break;
> +	case 0xf: /* charging error */
> +	default:
> +		battery_capacity = 0;
> +		battery_status = POWER_SUPPLY_STATUS_UNKNOWN;
> +	}
> +
> +	spin_lock_irqsave(&ps_dev->lock, flags);
> +	ps_dev->battery_capacity = battery_capacity;
> +	ps_dev->battery_status = battery_status;
> +	spin_unlock_irqrestore(&ps_dev->lock, flags);
> +
>  	return 0;
>  }
>
>  static struct ps_device *dualsense_create(struct hid_device *hdev)
>  {
>  	struct dualsense *ds;
> +	struct ps_device *ps_dev;
>  	int ret;
>
>  	ds = devm_kzalloc(&hdev->dev, sizeof(*ds), GFP_KERNEL);
> @@ -259,8 +374,11 @@  static struct ps_device *dualsense_create(struct hid_device *hdev)
>  	 */
>  	hdev->version |= HID_PLAYSTATION_VERSION_PATCH;
>
> -	ds->base.hdev = hdev;
> -	ds->base.parse_report = dualsense_parse_report;
> +	ps_dev = &ds->base;
> +	ps_dev->hdev = hdev;
> +	ps_dev->battery_capacity = 100; /* initial value until parse_report. */
> +	ps_dev->battery_status = POWER_SUPPLY_STATUS_UNKNOWN;
> +	ps_dev->parse_report = dualsense_parse_report;
>  	hid_set_drvdata(hdev, ds);
>
>  	ret = dualsense_get_mac_address(ds);
> @@ -276,6 +394,10 @@  static struct ps_device *dualsense_create(struct hid_device *hdev)
>  		goto err;
>  	}
>
> +	ret = ps_device_register_battery(ps_dev);
> +	if (ret < 0)

I believe if `ps_device_register_battery()` can only return 0 on success or
an errno, then `if (ret)` would be better.


> +		goto err;
> +
>  	return &ds->base;
>
>  err:


Regards,
Barnabás Pőcze

  reply	other threads:[~2021-01-07 17:51 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-02 22:30 [PATCH v2 00/13] HID: new driver for PS5 'DualSense' controller Roderick Colenbrander
2021-01-02 22:30 ` [PATCH v2 01/13] HID: playstation: initial DualSense USB support Roderick Colenbrander
2021-01-04 12:20   ` Jiri Kosina
2021-01-05  8:20   ` Benjamin Tissoires
2021-01-07 17:14   ` Barnabás Pőcze
2021-01-08  7:12     ` Roderick Colenbrander
2021-01-08 11:53       ` Barnabás Pőcze
2021-01-02 22:30 ` [PATCH v2 02/13] HID: playstation: use DualSense MAC address as unique identifier Roderick Colenbrander
2021-01-07 17:22   ` Barnabás Pőcze
2021-01-02 22:30 ` [PATCH v2 03/13] HID: playstation: add DualSense battery support Roderick Colenbrander
2021-01-07 17:50   ` Barnabás Pőcze [this message]
2021-01-02 22:31 ` [PATCH v2 04/13] HID: playstation: add DualSense touchpad support Roderick Colenbrander
2021-01-07 17:55   ` Barnabás Pőcze
2021-01-02 22:31 ` [PATCH v2 05/13] HID: playstation: add DualSense accelerometer and gyroscope support Roderick Colenbrander
2021-01-07 13:34   ` Florian Märkl
2021-01-08  5:51     ` Roderick Colenbrander
2021-01-07 18:51   ` Barnabás Pőcze
2021-01-08  6:06     ` Roderick Colenbrander
2021-01-08 12:01       ` Barnabás Pőcze
2021-01-08 17:15         ` Siarhei Vishniakou
2021-01-08 19:54           ` Roderick Colenbrander
2021-01-09  0:11             ` Siarhei Vishniakou
2021-01-11  0:06               ` Roderick Colenbrander
2021-01-02 22:31 ` [PATCH v2 06/13] HID: playstation: track devices in list Roderick Colenbrander
2021-01-07 20:13   ` Barnabás Pőcze
2021-01-02 22:31 ` [PATCH v2 07/13] HID: playstation: add DualSense Bluetooth support Roderick Colenbrander
2021-01-07 20:18   ` Barnabás Pőcze
2021-01-02 22:31 ` [PATCH v2 08/13] HID: playstation: add DualSense classic rumble support Roderick Colenbrander
2021-01-07 20:41   ` Barnabás Pőcze
2021-01-07 20:48     ` Barnabás Pőcze
2021-01-08 17:01     ` Roderick Colenbrander
2021-01-02 22:31 ` [PATCH v2 09/13] HID: playstation: add DualSense lightbar support Roderick Colenbrander
2021-01-07 21:01   ` Barnabás Pőcze
2021-01-02 22:31 ` [PATCH v2 10/13] HID: playstation: add microphone mute support for DualSense Roderick Colenbrander
2021-01-07 21:57   ` Barnabás Pőcze
2021-01-02 22:31 ` [PATCH v2 11/13] HID: playstation: add DualSense player LEDs support Roderick Colenbrander
2021-01-07 22:17   ` Barnabás Pőcze
2021-01-02 22:31 ` [PATCH v2 12/13] HID: playstation: DualSense set LEDs to default player id Roderick Colenbrander
2021-01-07 22:25   ` Barnabás Pőcze
2021-01-02 22:31 ` [PATCH v2 13/13] HID: playstation: report DualSense hardware and firmware version Roderick Colenbrander
2021-01-07 22:26   ` Barnabás Pőcze
2021-01-09  1:35     ` Roderick Colenbrander

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='0GfoA1O6YLM6fbSthjBgou-1KitOVn9gI7Y-wDy4ca5qlnQzO2LFknPu25GCB5RlbQcpzt7YUdU_Sf8o_4kHlWkrHmPvF3uFSwImvSe-AA8=@protonmail.com' \
    --to=pobrn@protonmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=lzye@google.com \
    --cc=roderick.colenbrander@sony.com \
    --cc=roderick@gaikai.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;
as well as URLs for NNTP newsgroup(s).