All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Richard Zhu <hongxing.zhu@nxp.com>
Cc: l.stach@pengutronix.de, bhelgaas@google.com,
	lorenzo.pieralisi@arm.com, vkoul@kernel.org,
	marcel.ziswiler@toradex.com, kishon@ti.com,
	linux-arm-kernel@lists.infradead.org, hongxing.zhu@nxp.com,
	linux-phy@lists.infradead.org, linux-pci@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel@pengutronix.de,
	linux-imx@nxp.com
Subject: Re: [PATCH v1 0/2] Fix the wrong order of phy callbacks
Date: Fri, 26 Aug 2022 08:26:05 +0200	[thread overview]
Message-ID: <4054884.5fSG56mABF@steina-w> (raw)
In-Reply-To: <1661173856-1192-1-git-send-email-hongxing.zhu@nxp.com>

Hello Richard,

Am Montag, 22. August 2022, 15:10:54 CEST schrieb Richard Zhu:
> Refer [1], phy_init() must be called before phy_power_on().
> This series used to fix the wrong order of the phy_init() and
> phy_power_on(), introduced by commit 1aa97b002258 ("phy: freescale: pcie:
> Initialize the imx8 pcie standalone phy driver") Tested on i.MX8MM EVK
> board when one NVME device is used.
> 
> [1]https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/d
> rivers/phy/phy-core.c?id=v5.19-rc1#n233
> 
> [PATCH v1 1/2] PCI: imx6: Fix the wrong order of phy_init() and
> [PATCH v1 2/2] phy: freescale: imx8m-pcie: Fix the wrong order of

Together with your imx8mp patch series on TQMa8MPxl + MBa8MPxL:
Tested-by: Alexander Stein <alexander.stein@ew.tq-group.com>

Thanks again!
Alexander




-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

WARNING: multiple messages have this Message-ID (diff)
From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Richard Zhu <hongxing.zhu@nxp.com>
Cc: l.stach@pengutronix.de, bhelgaas@google.com,
	lorenzo.pieralisi@arm.com, vkoul@kernel.org,
	marcel.ziswiler@toradex.com, kishon@ti.com,
	linux-arm-kernel@lists.infradead.org, hongxing.zhu@nxp.com,
	linux-phy@lists.infradead.org, linux-pci@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel@pengutronix.de,
	linux-imx@nxp.com
Subject: Re: [PATCH v1 0/2] Fix the wrong order of phy callbacks
Date: Fri, 26 Aug 2022 08:26:05 +0200	[thread overview]
Message-ID: <4054884.5fSG56mABF@steina-w> (raw)
In-Reply-To: <1661173856-1192-1-git-send-email-hongxing.zhu@nxp.com>

Hello Richard,

Am Montag, 22. August 2022, 15:10:54 CEST schrieb Richard Zhu:
> Refer [1], phy_init() must be called before phy_power_on().
> This series used to fix the wrong order of the phy_init() and
> phy_power_on(), introduced by commit 1aa97b002258 ("phy: freescale: pcie:
> Initialize the imx8 pcie standalone phy driver") Tested on i.MX8MM EVK
> board when one NVME device is used.
> 
> [1]https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/d
> rivers/phy/phy-core.c?id=v5.19-rc1#n233
> 
> [PATCH v1 1/2] PCI: imx6: Fix the wrong order of phy_init() and
> [PATCH v1 2/2] phy: freescale: imx8m-pcie: Fix the wrong order of

Together with your imx8mp patch series on TQMa8MPxl + MBa8MPxL:
Tested-by: Alexander Stein <alexander.stein@ew.tq-group.com>

Thanks again!
Alexander




WARNING: multiple messages have this Message-ID (diff)
From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Richard Zhu <hongxing.zhu@nxp.com>
Cc: l.stach@pengutronix.de, bhelgaas@google.com,
	lorenzo.pieralisi@arm.com, vkoul@kernel.org,
	marcel.ziswiler@toradex.com, kishon@ti.com,
	linux-arm-kernel@lists.infradead.org, hongxing.zhu@nxp.com,
	linux-phy@lists.infradead.org, linux-pci@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel@pengutronix.de,
	linux-imx@nxp.com
Subject: Re: [PATCH v1 0/2] Fix the wrong order of phy callbacks
Date: Fri, 26 Aug 2022 08:26:05 +0200	[thread overview]
Message-ID: <4054884.5fSG56mABF@steina-w> (raw)
In-Reply-To: <1661173856-1192-1-git-send-email-hongxing.zhu@nxp.com>

Hello Richard,

Am Montag, 22. August 2022, 15:10:54 CEST schrieb Richard Zhu:
> Refer [1], phy_init() must be called before phy_power_on().
> This series used to fix the wrong order of the phy_init() and
> phy_power_on(), introduced by commit 1aa97b002258 ("phy: freescale: pcie:
> Initialize the imx8 pcie standalone phy driver") Tested on i.MX8MM EVK
> board when one NVME device is used.
> 
> [1]https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/d
> rivers/phy/phy-core.c?id=v5.19-rc1#n233
> 
> [PATCH v1 1/2] PCI: imx6: Fix the wrong order of phy_init() and
> [PATCH v1 2/2] phy: freescale: imx8m-pcie: Fix the wrong order of

Together with your imx8mp patch series on TQMa8MPxl + MBa8MPxL:
Tested-by: Alexander Stein <alexander.stein@ew.tq-group.com>

Thanks again!
Alexander




_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-08-26  6:26 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 13:10 [PATCH v1 0/2] Fix the wrong order of phy callbacks Richard Zhu
2022-08-22 13:10 ` Richard Zhu
2022-08-22 13:10 ` Richard Zhu
2022-08-22 13:10 ` [PATCH v1 1/2] PCI: imx6: Fix the wrong order of phy_init() and phy_power_on() Richard Zhu
2022-08-22 13:10   ` Richard Zhu
2022-08-22 13:10   ` Richard Zhu
2022-08-22 13:10 ` [PATCH v1 2/2] phy: freescale: imx8m-pcie: " Richard Zhu
2022-08-22 13:10   ` Richard Zhu
2022-08-22 13:10   ` Richard Zhu
2022-08-26  6:26 ` Alexander Stein [this message]
2022-08-26  6:26   ` [PATCH v1 0/2] Fix the wrong order of phy callbacks Alexander Stein
2022-08-26  6:26   ` Alexander Stein
2022-08-26  6:56   ` Hongxing Zhu
2022-08-26  6:56     ` Hongxing Zhu
2022-08-26  6:56     ` Hongxing Zhu
2022-08-29  6:33 ` Ahmad Fatoum
2022-08-29  6:33   ` Ahmad Fatoum
2022-08-29  6:33   ` Ahmad Fatoum
2022-08-30  3:47   ` Hongxing Zhu
2022-08-30  3:47     ` Hongxing Zhu
2022-08-30  3:47     ` Hongxing Zhu
2022-08-30  7:15     ` Ahmad Fatoum
2022-08-30  7:15       ` Ahmad Fatoum
2022-08-30  7:15       ` Ahmad Fatoum
2022-08-30  7:50       ` Hongxing Zhu
2022-08-30  7:50         ` Hongxing Zhu
2022-08-30  7:50         ` Hongxing Zhu
2022-08-30 15:05         ` Bjorn Helgaas
2022-08-30 15:05           ` Bjorn Helgaas
2022-08-30 15:05           ` Bjorn Helgaas
2022-08-31  1:37           ` Hongxing Zhu
2022-08-31  1:37             ` Hongxing Zhu
2022-08-31  1:37             ` Hongxing Zhu
2022-09-27 10:40             ` Lorenzo Pieralisi
2022-09-27 10:40               ` Lorenzo Pieralisi
2022-09-27 10:40               ` Lorenzo Pieralisi
2022-09-29  0:51               ` Hongxing Zhu
2022-09-29  0:51                 ` Hongxing Zhu
2022-09-29  0:51                 ` Hongxing Zhu

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=4054884.5fSG56mABF@steina-w \
    --to=alexander.stein@ew.tq-group.com \
    --cc=bhelgaas@google.com \
    --cc=hongxing.zhu@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=kishon@ti.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=marcel.ziswiler@toradex.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 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.