From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Can Guo <quic_cang@quicinc.com>
Cc: bvanassche@acm.org, mani@kernel.org, adrian.hunter@intel.com,
vkoul@kernel.org, beanhuo@micron.com, avri.altman@wdc.com,
junwoo80.lee@samsung.com, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-kernel@vger.kernel.org (open list:ARM/Mediatek SoC
support:Keyword:mediatek),
linux-arm-kernel@lists.infradead.org (moderated
list:ARM/Mediatek SoC support:Keyword:mediatek),
linux-mediatek@lists.infradead.org (moderated list:ARM/Mediatek
SoC support:Keyword:mediatek)
Subject: Re: [PATCH v8 00/10] Enable HS-G5 support on SM8550
Date: Wed, 13 Dec 2023 22:44:36 -0500 [thread overview]
Message-ID: <yq1fs05h2j0.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <1701520577-31163-1-git-send-email-quic_cang@quicinc.com> (Can Guo's message of "Sat, 2 Dec 2023 04:36:06 -0800")
Can,
> This series enables HS-G5 support on SM8550.
Applied patches 1-8 to 6.8/scsi-staging, thanks!
The phy patches didn't apply. I assume they'll go through the phy tree.
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Can Guo <quic_cang@quicinc.com>
Cc: bvanassche@acm.org, mani@kernel.org, adrian.hunter@intel.com,
vkoul@kernel.org, beanhuo@micron.com, avri.altman@wdc.com,
junwoo80.lee@samsung.com, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-kernel@vger.kernel.org (open list:ARM/Mediatek SoC
support:Keyword:mediatek),
linux-arm-kernel@lists.infradead.org (moderated
list:ARM/Mediatek SoC support:Keyword:mediatek),
linux-mediatek@lists.infradead.org (moderated list:ARM/Mediatek
SoC support:Keyword:mediatek)
Subject: Re: [PATCH v8 00/10] Enable HS-G5 support on SM8550
Date: Wed, 13 Dec 2023 22:44:36 -0500 [thread overview]
Message-ID: <yq1fs05h2j0.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <1701520577-31163-1-git-send-email-quic_cang@quicinc.com> (Can Guo's message of "Sat, 2 Dec 2023 04:36:06 -0800")
Can,
> This series enables HS-G5 support on SM8550.
Applied patches 1-8 to 6.8/scsi-staging, thanks!
The phy patches didn't apply. I assume they'll go through the phy tree.
--
Martin K. Petersen Oracle Linux Engineering
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-12-14 3:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 12:36 [PATCH v8 00/10] Enable HS-G5 support on SM8550 Can Guo
2023-12-02 12:36 ` Can Guo
2023-12-02 12:36 ` [PATCH v8 01/10] scsi: ufs: host: Rename structure ufs_dev_params to ufs_host_params Can Guo
2023-12-02 12:36 ` Can Guo
2023-12-04 2:53 ` Peter Wang (王信友)
2023-12-04 2:53 ` Peter Wang (王信友)
2023-12-02 12:36 ` [PATCH v8 02/10] scsi: ufs: ufs-qcom: No need to set hs_rate after ufshcd_init_host_param() Can Guo
2023-12-02 12:36 ` [PATCH v8 03/10] scsi: ufs: ufs-qcom: Setup host power mode during init Can Guo
2023-12-02 12:36 ` [PATCH v8 04/10] scsi: ufs: ufs-qcom: Allow the first init start with the maximum supported gear Can Guo
2023-12-02 12:36 ` [PATCH v8 05/10] scsi: ufs: ufs-qcom: Limit HS-G5 Rate-A to hosts with HW version 5 Can Guo
2023-12-02 12:36 ` [PATCH v8 06/10] scsi: ufs: ufs-qcom: Set initial PHY gear to max HS gear for HW ver 4 and newer Can Guo
2023-12-02 12:36 ` [PATCH v8 07/10] scsi: ufs: ufs-qcom: Check return value of phy_set_mode_ext() Can Guo
2023-12-02 12:36 ` [PATCH v8 08/10] scsi: ufs: ufs-qcom: Add support for UFS device version detection Can Guo
2023-12-07 7:55 ` Manivannan Sadhasivam
2023-12-07 8:41 ` Nitin Rawat
2023-12-02 12:36 ` [PATCH v8 09/10] phy: qualcomm: phy-qcom-qmp-ufs: Rectify SM8550 UFS HS-G4 PHY Settings Can Guo
2023-12-02 12:36 ` Can Guo
2023-12-21 17:13 ` Vinod Koul
2023-12-21 17:13 ` Vinod Koul
2023-12-22 7:41 ` Can Guo
2023-12-22 7:41 ` Can Guo
2023-12-22 15:49 ` Vinod Koul
2023-12-22 15:49 ` Vinod Koul
2023-12-02 12:36 ` [PATCH v8 10/10] phy: qualcomm: phy-qcom-qmp-ufs: Add High Speed Gear 5 support for SM8550 Can Guo
2023-12-02 12:36 ` Can Guo
2023-12-02 20:27 ` Dmitry Baryshkov
2023-12-02 20:27 ` Dmitry Baryshkov
2023-12-07 8:22 ` [PATCH v8 00/10] Enable HS-G5 support on SM8550 neil.armstrong
2023-12-07 8:22 ` neil.armstrong
2023-12-07 8:26 ` Can Guo
2023-12-07 8:26 ` Can Guo
2023-12-14 3:44 ` Martin K. Petersen [this message]
2023-12-14 3:44 ` Martin K. Petersen
2023-12-19 2:18 ` Martin K. Petersen
2023-12-19 2:18 ` Martin K. Petersen
2023-12-21 17:15 ` (subset) " Vinod Koul
2023-12-21 17:15 ` Vinod Koul
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=yq1fs05h2j0.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=adrian.hunter@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=junwoo80.lee@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=quic_cang@quicinc.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.