From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: sre@kernel.org, orsonzhai@gmail.com,
baolin.wang@linux.alibaba.com, zhang.lyra@gmail.com,
felipe.balbi@linux.intel.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@opensource.cirrus.com,
linux-usb@vger.kernel.org, tony@atomide.com
Subject: Re: [PATCH] usb: phy: add dedicated notifier for charger events
Date: Mon, 14 Nov 2022 18:46:06 +0200 [thread overview]
Message-ID: <ec4edd51-3915-a798-2310-8ceadcd8152f@gmail.com> (raw)
In-Reply-To: <Y3JpfDU7T2Ks/H4m@kroah.com>
Hi,
On 14.11.22 г. 18:14 ч., Greg KH wrote:
> On Mon, Nov 14, 2022 at 02:56:02PM +0200, Ivaylo Dimitrov wrote:
>> usb_phy::notifier is already used by various PHY drivers (including
>> phy_generic) to report VBUS status changes and its usage conflicts with
>> charger current limit changes reporting.
>
> How exactly does it conflict?
>
see below
>> Fix that by introducing a second notifier that is dedicated to usb charger
>> notifications. Add usb_charger_XXX_notifier functions. Fix charger drivers
>> that currently (ab)use usb_XXX_notifier() to use the new API.
>
> Why not just set the notifier type to be a new one instead of adding a
> whole new notifier list? Or use a real callback? notifier lists are
> really horrid and should be avoided whenever possible.
>
Not sure what you mean by "notifier type', but if that is that val
parameter of atomic_notifier_call_chain(), the way it is used by usb
charger FW:
https://elixir.bootlin.com/linux/latest/source/drivers/usb/phy/phy.c#L132
is not compatible with:
https://elixir.bootlin.com/linux/latest/source/drivers/usb/phy/phy-generic.c#L185
for example, IIUC.
The former wants to send max current as val, while latter sends event
type as val. Sure, I may create some kind of hack, like using the MSB to
denote charger events, but that doesn't feel right.
Or, shall I do something else and fix the usage all over the place?
Please elaborate.
In regards to callback - I didn't want to come-up with a whole new API,
but just fix the current one. Also, a single callback will not be enough
- imagine a case with 2 batteries that have to be charged by a single
USB port, so 2 separate charger devices, most-probably. We will have to
keep a list of callback functions somehow. I admit my lack of knowledge,
but, do we already have such API to use?
>> Fixes: a9081a008f84 ("usb: phy: Add USB charger support")
>>
>> Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
>
> You can't have a blank line between there, checkpatch.pl should have
> complained.
>
it didn't:
./scripts/checkpatch.pl
0001-usb-phy-add-dedicated-notifier-for-charger-events.patch
total: 0 errors, 0 warnings, 90 lines checked
0001-usb-phy-add-dedicated-notifier-for-charger-events.patch has no
obvious style problems and is ready for submission.
Will fix, if I am to send v2
Thanks,
Ivo
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2022-11-14 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 12:56 [PATCH] usb: phy: add dedicated notifier for charger events Ivaylo Dimitrov
2022-11-14 14:03 ` Charles Keepax
2022-11-14 16:14 ` Greg KH
2022-11-14 16:46 ` Ivaylo Dimitrov [this message]
2022-11-16 7:11 ` Ivaylo Dimitrov
2022-12-05 20:29 ` Ivaylo Dimitrov
2022-12-08 15:39 ` Greg KH
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=ec4edd51-3915-a798-2310-8ceadcd8152f@gmail.com \
--to=ivo.g.dimitrov.75@gmail.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=patches@opensource.cirrus.com \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
--cc=zhang.lyra@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;
as well as URLs for NNTP newsgroup(s).