devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Elad Nachman <enachman@marvell.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org"
	<krzysztof.kozlowski+dt@linaro.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [EXT] Re: [PATCH] dt-bindings: usb: Add Marvell ac5
Date: Mon, 8 Jan 2024 18:01:26 +0000	[thread overview]
Message-ID: <20240108-chariot-thinner-7a86808a0571@spud> (raw)
In-Reply-To: <BN9PR18MB425195C57E2FC24D5F331C19DB6B2@BN9PR18MB4251.namprd18.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2636 bytes --]

On Mon, Jan 08, 2024 at 05:47:24PM +0000, Elad Nachman wrote:
> 
> 
> > -----Original Message-----
> > From: Conor Dooley <conor@kernel.org>
> > Sent: Monday, January 8, 2024 7:15 PM
> > To: Elad Nachman <enachman@marvell.com>
> > Cc: gregkh@linuxfoundation.org; robh+dt@kernel.org;
> > krzysztof.kozlowski+dt@linaro.org; conor+dt@kernel.org;
> > devicetree@vger.kernel.org; linux-usb@vger.kernel.org; linux-
> > kernel@vger.kernel.org
> > Subject: [EXT] Re: [PATCH] dt-bindings: usb: Add Marvell ac5
> > 
> > External Email
> > 
> > ----------------------------------------------------------------------
> > On Sun, Jan 07, 2024 at 05:25:57PM +0200, Elad Nachman wrote:
> > > From: Elad Nachman <enachman@marvell.com>
> > >
> > > Add Marvell ac5 device tree bindings to generic EHCI.
> > > This compatible enables the Marvell Orion platform code to properly
> > > configure the DMA mask for the Marvell AC5 SOC.
> > >
> > > Signed-off-by: Elad Nachman <enachman@marvell.com>
> > 
> > Maybe I am dumb, but I don't understand how this does what the commit
> > message says. There's no fallback to generic-ehci or any other compatible
> > that is already understood by the driver.
> > 
> > What am I missing?
> 
> Following guidance by Andrew Lunn on my mmc patchset, I have split the patchset
> Into a single patch for dt-bindings review and another for USB driver review.

I don't understand that advice. dt-bindings should (almost) always be
with the driver. Otherwise you just confuse people like me.

Perhaps Andrew meant sending dt*s* patches separately from the driver &
bindings?

Cheers,
Conor.

> 
> The USB driver patch utilizing this new dt bindings compatible string is here:
> 
> https://patchwork.kernel.org/project/linux-usb/patch/20240107163307.3677347-1-enachman@marvell.com/
> 
> > 
> > > ---
> > >  Documentation/devicetree/bindings/usb/generic-ehci.yaml | 1 +
> > >  1 file changed, 1 insertion(+)
> > >
> > > diff --git a/Documentation/devicetree/bindings/usb/generic-ehci.yaml
> > > b/Documentation/devicetree/bindings/usb/generic-ehci.yaml
> > > index 87986c45be88..2ed178f16a78 100644
> > > --- a/Documentation/devicetree/bindings/usb/generic-ehci.yaml
> > > +++ b/Documentation/devicetree/bindings/usb/generic-ehci.yaml
> > > @@ -77,6 +77,7 @@ properties:
> > >            - const: usb-ehci
> > >        - enum:
> > >            - generic-ehci
> > > +          - marvell,ac5-ehci
> > >            - marvell,armada-3700-ehci
> > >            - marvell,orion-ehci
> > >            - nuvoton,npcm750-ehci
> > > --
> > > 2.25.1
> > >
> 
> Elad.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-01-08 18:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-07 15:25 [PATCH] dt-bindings: usb: Add Marvell ac5 Elad Nachman
2024-01-08 17:15 ` Conor Dooley
2024-01-08 17:47   ` [EXT] " Elad Nachman
2024-01-08 18:01     ` Conor Dooley [this message]
2024-01-08 18:15       ` Elad Nachman
2024-01-08 18:23         ` Conor Dooley
2024-01-09  9:32         ` Krzysztof Kozlowski

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=20240108-chariot-thinner-7a86808a0571@spud \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=enachman@marvell.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).