Devicetree
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <ivo.g.dimitrov.75@gmail.com>, <conor@kernel.org>
Cc: <vkoul@kernel.org>, <neil.armstrong@linaro.org>,
	<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<aaro.koskinen@iki.fi>, <andreas@kemnade.info>,
	<khilman@baylibre.com>, <rogerq@kernel.org>, <tony@atomide.com>,
	<linusw@kernel.org>, <brgl@kernel.org>,
	<linux-phy@lists.infradead.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
	<linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] dt-bindings: phy: motorola,cpcap-usb: add chrg_det interrupt
Date: Tue, 7 Jul 2026 09:58:20 +0000	[thread overview]
Message-ID: <dad556ba-5965-42a0-b78a-2d417b2f6837@microchip.com> (raw)
In-Reply-To: <2b192691-54d8-4449-a18c-b87266c6c73c@gmail.com>

On 06/07/2026 22:25, Ivaylo Dimitrov wrote:
> 
> Hi,
> 
> On 6.07.26 г. 20:14 ч., Conor Dooley wrote:
>> On Sun, Jul 05, 2026 at 01:11:02PM +0300, Ivaylo Dimitrov wrote:
>>> The CPCAP USB PHY driver uses the CPCAP charger detection interrupt
>>> for DCP detection.
>>
>> This is not currently true, the driver does not look for this interrupt
>> at the time of this patch.
>>
> 
> Right, this is bad wording caused by the fact that initially the driver
> patch came before the binding patch.
> 
>>> Update the binding and example DTS to use the corresponding
>>> "chrg_det" interrupt name.
>>
>> Sounds to me like this new interrupt is optional, since until now it has
>> not been needed? The patch however makes it mandatory. I think your
>> driver patch also makes it mandatory, which will break older
>> devicetrees.
>>
> 
> Oh, it is indeed not needed for proper DCP/SDP detection, after some
> experiments I was able to teach the driver to do proper detection by
> using current interrupts only.
> 
>> What makes this ABI break okay?
>>
> 
> Will send new series with schema/DT patches dropped.

I think the devicetree patches are fine, provided you add
a minItems of N-1 so that the new interrupt is optional.
Dropping them would mean that the documentation for this device
remains incomplete since that interrupt does exist.

Cheers,
Conor.


  reply	other threads:[~2026-07-07  9:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05 10:11 [PATCH v3 0/4] phy: cpcap-usb: improve charger detection and export cable state Ivaylo Dimitrov
2026-07-05 10:11 ` [PATCH v3 1/4] dt-bindings: phy: motorola,cpcap-usb: add chrg_det interrupt Ivaylo Dimitrov
2026-07-05 10:19   ` sashiko-bot
2026-07-06 17:14   ` Conor Dooley
2026-07-06 21:25     ` Ivaylo Dimitrov
2026-07-07  9:58       ` Conor.Dooley [this message]
2026-07-07 19:01         ` Ivaylo Dimitrov
2026-07-05 10:11 ` [PATCH v3 2/4] ARM: dts: ti: cpcap-mapphone: use charger detection interrupt for CPCAP USB PHY Ivaylo Dimitrov
2026-07-05 10:11 ` [PATCH v3 3/4] phy: cpcap-usb: add DCP detection and make UART idle mode optional Ivaylo Dimitrov
2026-07-05 10:24   ` sashiko-bot
2026-07-05 10:11 ` [PATCH v3 4/4] phy: cpcap-usb: add extcon support Ivaylo Dimitrov
2026-07-05 10:25   ` sashiko-bot

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=dad556ba-5965-42a0-b78a-2d417b2f6837@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=andreas@kemnade.info \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=tony@atomide.com \
    --cc=vkoul@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