mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: "Christian Marangi (Ansuel)" <ansuelsmth@gmail.com>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Lorenzo Bianconi <lorenzo@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v13 0/3] airoha: an7581: USB support
Date: Tue, 6 Oct 2026 11:18:11 +0200	[thread overview]
Message-ID: <asS805-vbum46Oji@parshuram> (raw)
In-Reply-To: <CA+_ehUx_B2K3WgLYkt2fz5jzDRB24LQRB3uX_VScZ2QSxCojPg@mail.gmail.com>

On 05-10-26, 17:31, Christian Marangi (Ansuel) wrote:
> Il giorno lun 5 ott 2026 alle ore 17:28 Vinod Koul <vkoul@kernel.org>
> ha scritto:
> >
> > On 05-10-26, 12:55, Christian Marangi wrote:
> > > This is a major rework of the old v2 series.
> > >
> > > The SoC always support USB 2.0 but for USB 3.0 it needs additional
> > > configuration for the Serdes port. Such port can be either configured
> > > for USB usage or for PCIe lines or HSGMII and these are configured
> > > in the SCU space.
> > >
> > > The previous implementation of a dedicated SSR driver was too
> > > complex and fragile for the simple task of configuring a register
> > > hence it was dropped and the handling is entirely in the PHY driver.
> > >
> > > Everything was reducted to the dt-bindings to describe the Serdes line.
> > >
> > > Also the property for the PHY are renamed to a more suitable name and
> > > everything is now mandatory to simplify the implementation.
> > > (the PHY are always present and active on the SoC)
> > >
> > > Also other unrelated patch are dropped from this series.
> > >
> > > Changes v13:
> > > - Rebase on top of phy next
> >
> > Pls fix the chechpatch issues. There is new blank line at EOF, SPDX
> > format mismatches and many more. Make sure you pass --strict flag to it
> >
> 
> My checkpatch doesn't report the blank line. Am I missing something?
> For SPDX, is it ok to change it? The commit just move file. I would
> like to fix that in a separate commit after. (I can include in this
> series if you
> want)

Yeah checkpatch wont. Git complains when i apply:

Applying: dt-bindings: phy: Add documentation for Airoha AN7581 USB PHY
.git/rebase-apply/patch:74: new blank line at EOF.
+

I think we should fix SPDX ones.

> The other warning are about Kconfig description where I can
> artificially make the help text longer (no idea if it's OK...)

That one is okay, I this description is fine

> And the line too long for the define but making the line shorter
> would result in a disaster for the register.
> 
> Up to you what I should fix but I guess the real important one
> is the blank line but my checkpatch script is not detecting that...

Yep, line and SPDX ones are important. long line splitting will make
code worse to read, i care more about readablity more..

-- 
~Vinod

      reply	other threads:[~2026-10-06  9:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 10:55 Christian Marangi
2026-10-05 10:55 ` [PATCH v13 1/3] dt-bindings: phy: Add documentation for Airoha AN7581 USB PHY Christian Marangi
2026-10-05 10:55 ` [PATCH v13 2/3] phy: move and rename Airoha PCIe PHY driver to dedicated directory Christian Marangi
2026-10-05 10:55 ` [PATCH v13 3/3] phy: airoha: Add support for Airoha AN7581 USB PHY Christian Marangi
2026-10-05 15:28 ` [PATCH v13 0/3] airoha: an7581: USB support Vinod Koul
2026-10-05 15:31   ` Christian Marangi (Ansuel)
2026-10-06  9:18     ` Vinod Koul [this message]

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=asS805-vbum46Oji@parshuram \
    --to=vkoul@kernel.org \
    --cc=ansuelsmth@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=lorenzo@kernel.org \
    --cc=mani@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@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

all inboxes | Powered by JetHome®