From: "José Expósito" <jose.exposito89@gmail.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: benjamin.tissoires@redhat.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/5] HID: magicmouse: register power supply
Date: Wed, 28 Jul 2021 11:58:03 +0200 [thread overview]
Message-ID: <20210728095803.GA31924@elementary-os.localdomain> (raw)
In-Reply-To: <nycvar.YFH.7.76.2107281134430.8253@cbobk.fhfr.pm>
On Wed, Jul 28, 2021 at 11:35:20AM +0200, Jiri Kosina wrote:
> On Fri, 25 Jun 2021, José Expósito wrote:
>
> > > > [...]
> > > > v2: Add depends on USB_HID to Kconfig
> > >
> > > Hmm, why is this dependency needed in the first place, please? I think
> > > trying to keep the drivers independent on transport drivers (especially in
> > > cases like this, where more variants of physical transports actually
> > > really do exist) is worth trying.
> >
> > Sorry, that's something I should have explained in the changelog.
> >
> > Intel's test bot reported compilation errors on the first version of the patch
> > when USB support wasn't configured:
> > https://lore.kernel.org/patchwork/patch/1425313/
> >
> > I was kindly pointed to a similar error and its fix, but, maybe in this case this
> > is not the right fix?
> > Maybe there is a macro that I can use to wrap the USB related code in an #ifdef?
>
> It can certainly be wrapped, but looking into the code now, it probably
> wouldn't really bring more clarity. I will apply the series with adding
> the USB_HID dependency for now.
Hi Jiri,
I've been investigating a bit about this issue and I think this might not be the
righ solution for the problem.
John Chen's patch (9de07a4e8d4cb269f9876b2ffa282b5ffd09e05b):
https://lore.kernel.org/lkml/20210327130508.24849-5-johnchen902@gmail.com/
Already adds battery reporting over bluetooth, so my patch is redundant... And worse
than his, I should add.
I was investigating how to do something similar over USB, but I couldn't finish a patch yet.
So, if you don't mind, I'd prefer not to apply this patchset yet until I figure out
a better solution on v3.
Thanks,
Jose
next prev parent reply other threads:[~2021-07-28 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 18:06 [PATCH v2 1/5] HID: magicmouse: register power supply José Expósito
2021-05-22 18:06 ` [PATCH v2 2/5] HID: magicmouse: report battery capacity over bluetooth José Expósito
2021-05-22 18:06 ` [PATCH v2 3/5] HID: magicmouse: Magic Trackpad 2 USB battery capacity José Expósito
2021-05-22 18:06 ` [PATCH v2 4/5] HID: magicmouse: Magic Mouse " José Expósito
2021-05-22 18:06 ` [PATCH v2 5/5] HID: magicmouse: report battery status José Expósito
2021-06-24 13:33 ` [PATCH v2 1/5] HID: magicmouse: register power supply Jiri Kosina
2021-06-25 17:08 ` José Expósito
2021-07-28 9:35 ` Jiri Kosina
2021-07-28 9:58 ` José Expósito [this message]
2021-07-28 10:04 ` Jiri Kosina
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=20210728095803.GA31924@elementary-os.localdomain \
--to=jose.exposito89@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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