From: Changhuang Liang <changhuang.liang@starfivetech.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Jack Zhu <jack.zhu@starfivetech.com>,
<linux-phy@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 2/2] phy: starfive: Add mipi dphy rx support
Date: Mon, 17 Jul 2023 09:34:50 +0800 [thread overview]
Message-ID: <ff879340-2371-6966-84fb-d59de1c15a0f@starfivetech.com> (raw)
In-Reply-To: <ZLFfkhnxZbRS7s9y@matsya>
On 2023/7/14 22:45, Vinod Koul wrote:
> On 30-06-23, 02:30, Changhuang Liang wrote:
>> Add mipi dphy rx support for the StarFive JH7110 SoC. It is used to
>> transfer CSI camera data.
>>
>> Signed-off-by: Changhuang Liang <changhuang.liang@starfivetech.com>
>> ---
>> MAINTAINERS | 7 +
>> drivers/phy/Kconfig | 1 +
>> drivers/phy/Makefile | 1 +
>> drivers/phy/starfive/Kconfig | 13 ++
>> drivers/phy/starfive/Makefile | 2 +
>> drivers/phy/starfive/phy-starfive-dphy-rx.c | 230 ++++++++++++++++++++
>> 6 files changed, 254 insertions(+)
>> create mode 100644 drivers/phy/starfive/Kconfig
>> create mode 100644 drivers/phy/starfive/Makefile
>
> This need rebase as files exist now
>
OK, I will rebase it.
Thanks,
Changhuang
next prev parent reply other threads:[~2023-07-17 2:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 9:30 [PATCH v6 0/2] Add JH7110 MIPI DPHY RX support Changhuang Liang
2023-06-30 9:30 ` [PATCH v6 1/2] dt-bindings: phy: Add starfive,jh7110-dphy-rx Changhuang Liang
2023-06-30 9:30 ` [PATCH v6 2/2] phy: starfive: Add mipi dphy rx support Changhuang Liang
2023-07-14 14:45 ` Vinod Koul
2023-07-17 1:34 ` Changhuang Liang [this message]
2023-07-24 10:55 ` [PATCH v6 0/2] Add JH7110 MIPI DPHY RX support 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=ff879340-2371-6966-84fb-d59de1c15a0f@starfivetech.com \
--to=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jack.zhu@starfivetech.com \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--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 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).