From: Conor Dooley <conor@kernel.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Jernej Skrabec <jernej.skrabec@gmail.com>,
Lee Jones <lee@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
"Jagielski, Jedrzej" <jedrzej.jagielski@intel.com>,
Andre Przywara <andre.przywara@arm.com>,
Chen-Yu Tsai <wens@kernel.org>,
linux-sunxi@lists.linux.dev, mfd@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11 1/2] dt-bindings: mfd: x-powers: Add AC200
Date: Tue, 8 Sep 2026 23:02:51 +0100 [thread overview]
Message-ID: <aqCGC9rRgjdi5E92@squawk> (raw)
In-Reply-To: <CADvTj4rZnsSWe2NOKxpmTE9inyUFU2Cz4AS-zwuBEXkM4hjkLQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2174 bytes --]
On Tue, Sep 08, 2026 at 03:38:00PM -0600, James Hilliard wrote:
> On Tue, Sep 8, 2026 at 12:05 PM Conor Dooley <conor@kernel.org> wrote:
> >
> > On Mon, Sep 07, 2026 at 03:03:14PM -0600, James Hilliard wrote:
> > > The AC200 is an I2C-controlled mixed-signal companion IC containing
> > > audio, video, RTC and Fast Ethernet PHY functions.
> > >
> > > Describe the shared input clock, audio DAI, TV encoder display graph and
> > > optional bandgap calibration in one parent node. The codec and TV encoder
> > > do not need separate firmware nodes.
> > >
> > > AC_LDOIN and TV_VCC are distinct 3.3 V supply inputs. Describe them
> > > separately without requiring different external regulators. Require the
> > > audio supply when the DAI is described and the video supply when the
> > > display graph is present, while allowing PHY-only configurations.
> > >
> > > Describe the optional shared INTB connection without an internal
> > > interrupt domain. Cable detection status remains readable over I2C when
> > > INTB is not connected. Include wired and unwired examples.
> > >
> > > The Ethernet PHY is represented by a PHY package on its MDIO bus, with a
> > > phandle back to this device for access to the package control registers.
> > > It therefore does not require an MFD child node. The input clock must run
> > > at 24 or 27 MHz when the Ethernet PHY is used, matching the rates encoded
> > > by its documented clock selector.
> > >
> > > Signed-off-by: Jernej Skrabec <jernej.skrabec@gmail.com>
> > > Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> >
> > btw, this is kinda odd. Jernej has a signoff, but no other attribution.
> > Are they a coauthor missing a Co-developed-by
>
> I had just retained the existing Signed-off-by from some of his patches
> that got incorporated into this one, is using Co-developed-by better
> practice for attribution? Should I use both a Co-developed-by and
> the Signed-off-by for this sort of thing?
Yes, both. Co-developed-by is how you signify that Jernej wrote some of
this. Right now, the code is attributed solely to you as the one in the
author field of the patch.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-09-08 22:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 21:03 [PATCH v11 0/2] mfd: add X-Powers AC200 support James Hilliard
2026-09-07 21:03 ` [PATCH v11 1/2] dt-bindings: mfd: x-powers: Add AC200 James Hilliard
2026-09-07 21:07 ` sashiko-bot
2026-09-08 18:05 ` Conor Dooley
2026-09-08 21:38 ` James Hilliard
2026-09-08 22:02 ` Conor Dooley [this message]
2026-09-07 21:03 ` [PATCH v11 2/2] mfd: ac200: Add X-Powers AC200 support James Hilliard
2026-09-07 21:09 ` 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=aqCGC9rRgjdi5E92@squawk \
--to=conor@kernel.org \
--cc=andre.przywara@arm.com \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=james.hilliard1@gmail.com \
--cc=jedrzej.jagielski@intel.com \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mfd@lists.linux.dev \
--cc=robh@kernel.org \
--cc=wens@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.