From: Jakob Hauser <jahau@rocketmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Sebastian Reichel <sre@kernel.org>, Lee Jones <lee@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Beomho Seo <beomho.seo@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Stephan Gerhold <stephan@gerhold.net>,
Raymond Hackley <raymondhackley@protonmail.com>,
Pavel Machek <pavel@ucw.cz>, Axel Lin <axel.lin@ingics.com>,
ChiYuan Huang <cy_huang@richtek.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v3 8/8] dt-bindings: Add rt5033 mfd, regulator and charger
Date: Wed, 3 May 2023 21:33:49 +0200 [thread overview]
Message-ID: <73c02d98-c306-5e9d-2737-ff2d4a7393d1@rocketmail.com> (raw)
In-Reply-To: <a0f4252d-7f27-6dd9-dea0-f8d242011f70@linaro.org>
Hi Krzysztof, Hi all,
On 02.05.23 12:59, Krzysztof Kozlowski wrote:
...
> Apologies for this, just very busy times. :)
>
Thanks for letting me know. Take the time you need.
Writing towards the list:
I think there is a misunderstanding here.
The connector node provides information about the installed USB
hardware. E.g. property "usb-role-switch" means "Indicates that the
device is capable of assigning the USB data role (USB host or USB
device) for a given USB connector [...]" [5]. To my understanding, in
relation with a port node this actually says that this port has this
capability. This is not relevant to the rt5033-charger driver.
The rt5033-charger driver needs to pair with the extcon chip because it
needs the information about *external* connectors being attached [6].
Extcon devices like SM5502 or SM5504 are real hardware. I'm not adding
new properties. The way of getting an excton device from the devicetree
by phandle is part of the extcon subsystem:
- function to get the excton device by phandle: [7]
- line that's looking for the property "extcon": [8]
The connector node is the wrong approach, as far as I can tell on my
current state of knowledge. It doesn't provide the information needed by
the rt5033-charger driver.
[5]
https://github.com/torvalds/linux/blob/v6.3/Documentation/devicetree/bindings/usb/usb-drd.yaml#L51-L55
[6]
https://github.com/torvalds/linux/blob/v6.3/include/linux/extcon.h#L32-L60
[7]
https://github.com/torvalds/linux/blob/v6.3/drivers/extcon/extcon.c#L1361-L1392
[8]
https://github.com/torvalds/linux/blob/v6.3/drivers/extcon/extcon.c#L1381
Kind regards,
Jakob
next prev parent reply other threads:[~2023-05-03 19:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1682636929.git.jahau.ref@rocketmail.com>
2023-04-27 23:30 ` [PATCH v3 0/8] Add RT5033 charger device driver Jakob Hauser
2023-04-27 23:30 ` [PATCH v3 1/8] mfd: rt5033: Drop rt5033-battery sub-device Jakob Hauser
2023-04-27 23:30 ` [PATCH v3 2/8] mfd: rt5033: Fix chip revision readout Jakob Hauser
2023-04-27 23:30 ` [PATCH v3 3/8] mfd: rt5033: Fix STAT_MASK, HZ_MASK and AICR defines Jakob Hauser
2023-04-27 23:30 ` [PATCH v3 4/8] mfd: rt5033: Apply preparatory changes before adding rt5033-charger driver Jakob Hauser
2023-04-27 23:30 ` [PATCH v3 5/8] power: supply: rt5033_charger: Add RT5033 charger device driver Jakob Hauser
2023-05-05 11:51 ` Linus Walleij
2023-04-27 23:30 ` [PATCH v3 6/8] power: supply: rt5033_charger: Add cable detection and USB OTG supply Jakob Hauser
2023-04-27 23:30 ` [PATCH v3 7/8] power: supply: rt5033_battery: Adopt status property from charger Jakob Hauser
2023-04-27 23:30 ` [PATCH v3 8/8] dt-bindings: Add rt5033 mfd, regulator and charger Jakob Hauser
2023-04-28 14:39 ` Henrik Grimler
2023-04-28 15:42 ` Jakob Hauser
2023-05-01 7:21 ` Krzysztof Kozlowski
2023-05-01 17:35 ` Jakob Hauser
2023-05-01 21:16 ` Jakob Hauser
2023-05-02 10:59 ` Krzysztof Kozlowski
2023-05-03 19:33 ` Jakob Hauser [this message]
2023-05-05 20:13 ` Rob Herring
2023-05-06 10:48 ` Jakob Hauser
2023-05-01 9:13 ` Linus Walleij
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=73c02d98-c306-5e9d-2737-ff2d4a7393d1@rocketmail.com \
--to=jahau@rocketmail.com \
--cc=axel.lin@ingics.com \
--cc=beomho.seo@samsung.com \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=phone-devel@vger.kernel.org \
--cc=raymondhackley@protonmail.com \
--cc=robh+dt@kernel.org \
--cc=sre@kernel.org \
--cc=stephan@gerhold.net \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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
all inboxes | Powered by JetHome®