From: Vinod Koul <vkoul@kernel.org>
To: Wangseok Lee <wangseok.lee@samsung.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
robh+dt <robh+dt@kernel.org>, krzk+dt <krzk+dt@kernel.org>,
kishon <kishon@ti.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"jesper.nilsson" <jesper.nilsson@axis.com>,
"lars.persson" <lars.persson@axis.com>,
bhelgaas <bhelgaas@google.com>,
linux-phy <linux-phy@lists.infradead.org>,
linux-pci <linux-pci@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
"lorenzo.pieralisi" <lorenzo.pieralisi@arm.com>,
kw <kw@linux.com>, linux-arm-kernel <linux-arm-kernel@axis.com>,
kernel <kernel@axis.com>, Moon-Ki Jun <moonki.jun@samsung.com>,
Dongjin Yang <dj76.yang@samsung.com>
Subject: Re: [PATCH 0/5] Add support for Axis, ARTPEC-8 PCIe driver
Date: Mon, 2 May 2022 15:44:15 +0530 [thread overview]
Message-ID: <Ym+u9yYrV9mxkyWX@matsya> (raw)
In-Reply-To: <20220421235725epcms2p1fc34c904f960cba958fa692c6d5dad9c@epcms2p1>
On 22-04-22, 08:57, Wangseok Lee wrote:
> > On 18/04/2022 09:20, Wangseok Lee wrote:
> > Maybe, quite probably. The reluctance to extend any existing code makes
> > me doubting this, but I admit that there are many differences.
> >
> >> For these reasons, my opinion is that better to create
> >> a phy, controller both driver with a new file.
> >> Please let me know your opinion.
> >
> > At the end it's mostly the decision of PCIe and phy subsystem
> > maintainers whether they want to have separate drivers for DWC PCIe
> > blocks in ARMv8 Samsung SoCs.
> >
> > In any case, the driver code looks like copied-pasted from some vendor
> > sources, so you need to bring it to shape.
I think havong a common driver helps everyone, many vendors do that
already. If you have a technical issue of adding and maintaining a
common driver upstream we would be eager to understand and help with
that...
--
~Vinod
next prev parent reply other threads:[~2022-05-02 10:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220418072049epcms2p463a9f01d8ae3e29f75b746a0dce934f1@epcms2p4>
2022-04-18 7:20 ` [PATCH 0/5] Add support for Axis, ARTPEC-8 PCIe driver Wangseok Lee
2022-04-18 16:52 ` Krzysztof Kozlowski
[not found] ` <CGME20220418072049epcms2p463a9f01d8ae3e29f75b746a0dce934f1@epcms2p1>
2022-04-21 23:57 ` Wangseok Lee
2022-05-02 10:14 ` Vinod Koul [this message]
[not found] <CGME20220328014430epcms2p7063834feb0abdf2f38a62723c96c9ff1@epcms2p7>
2022-03-28 1:44 ` 이왕석
2022-03-28 7:11 ` Krzysztof Kozlowski
[not found] ` <CGME20220328014430epcms2p7063834feb0abdf2f38a62723c96c9ff1@epcms2p8>
2022-03-28 9:02 ` 이왕석
2022-03-28 9:38 ` Krzysztof Kozlowski
[not found] ` <CGME20220328014430epcms2p7063834feb0abdf2f38a62723c96c9ff1@epcms2p4>
2022-03-28 11:29 ` 이왕석
2022-03-28 11:40 ` Krzysztof Kozlowski
2022-04-13 6:45 ` Vinod Koul
[not found] ` <CGME20220328014430epcms2p7063834feb0abdf2f38a62723c96c9ff1@epcms2p1>
2022-03-29 3:49 ` 이왕석
2022-03-29 6:41 ` Krzysztof Kozlowski
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=Ym+u9yYrV9mxkyWX@matsya \
--to=vkoul@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dj76.yang@samsung.com \
--cc=jesper.nilsson@axis.com \
--cc=kernel@axis.com \
--cc=kishon@ti.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kw@linux.com \
--cc=lars.persson@axis.com \
--cc=linux-arm-kernel@axis.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=moonki.jun@samsung.com \
--cc=robh+dt@kernel.org \
--cc=wangseok.lee@samsung.com \
/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).