From: Bjorn Helgaas <helgaas@kernel.org>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com, krzk@kernel.org,
linux-kernel@vger.kernel.org, jingoohan1@gmail.com,
javier@osg.samsung.com, kgene@kernel.org,
linux-samsung-soc@vger.kernel.org, cpgs@samsung.com,
niyas.ahmed@samsung.com, alim.akhtar@samsung.com,
pankaj.dubey@samsung.com, kishon@ti.com,
devicetree@vger.kernel.org, mark.rutland@arm.com,
vivek.gautam@codeaurora.org, robh+dt@kernel.org
Subject: Re: [PATCH V3 0/4] PCI: exynos: use the PHY generic framework
Date: Fri, 17 Feb 2017 13:51:46 -0600 [thread overview]
Message-ID: <20170217195146.GA17762@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <04b568d2-d85e-9cbd-1379-d657f574f279@samsung.com>
On Thu, Feb 16, 2017 at 07:33:15AM +0900, Jaehoon Chung wrote:
> Dear Bjorn,
>
> On 02/16/2017 06:11 AM, Bjorn Helgaas wrote:
> > On Mon, Feb 13, 2017 at 05:26:09PM +0900, Jaehoon Chung wrote:
> >> This patcheset is for using PHY generic framework.
> >> Current pci-exyns doesn't use the phy framework since there haven't been on
> >> PHY subsystem when Exynos5440 had bean upstreamed.
> >> It's making a difficult to upstream the other Exynos variants because of different
> >> PHY registers.
> >>
> >> This patcheset has the below modifications:
> >> 1) Introduces the phy-exynos-pcie
> >> 2) Handles PHY register from PHY framework for pci-exynos
> >> 3) Modifies the dt-binding of pci-exynos
> >> 4) Maintains the backward compatibility
> >>
> >> Changelog on V3:
> >> - Drops "ARM: dts: exynos5440: support the phy-pcie node of pcie"
> >> : Will send this patch after applying this patchset.
> >> - Fixes typo
> >> - Based on latest PCI git repository (host-exynos branch)
> >> - Changes commit message
> >> - Removes the dependency
> >>
> >> Changelog on V2:
> >> - Keep current codes for backward compatibility
> >> - Fixes some typos
> >> - Split the patches for removing the dependency
> >> - Removes the unnecessary codes
> >> - Change the patch's sequence
> >> - Based on latest PCI git repository.(next branch)
> >>
> >> Jaehoon Chung (4):
> >> Documetation: samsung-phy: add the exynos-pcie-phy binding
> >> phy: phy-exynos-pcie: Add support for Exynos PCIe phy
> >> Documetation: binding: modify the exynos5440 pcie binding
> >> PCI: exynos: support the using PHY generic framework
> >>
> >> .../bindings/pci/samsung,exynos5440-pcie.txt | 29 +++
> >> .../devicetree/bindings/phy/samsung-phy.txt | 17 ++
> >> drivers/pci/host/pci-exynos.c | 54 +++-
> >> drivers/phy/Kconfig | 8 +
> >> drivers/phy/Makefile | 1 +
> >> drivers/phy/phy-exynos-pcie.c | 285 +++++++++++++++++++++
> >> 6 files changed, 390 insertions(+), 4 deletions(-)
> >> create mode 100644 drivers/phy/phy-exynos-pcie.c
> >
> > I made the updates Vivek suggested and provisionally added these to my
> > pci/host-exynos branch to get some build testing.
>
> Thanks!
>
> >
> > Kishon, I guess it probably makes more sense for me to apply this
> > because even though the drivers/pci changes are small, I think they
> > depend on other pci-exynos.c changes that are on my branch but not in
> > Linus' tree yet.
I haven't heard from Kishon, but I merged these to my -next branch for
v4.11.
Bjorn
next prev parent reply other threads:[~2017-02-17 19:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170213082615epcas5p2f5ecabbd5853a8e27da5f88fcae85158@epcas5p2.samsung.com>
2017-02-13 8:26 ` [PATCH V3 0/4] PCI: exynos: use the PHY generic framework Jaehoon Chung
[not found] ` <CGME20170213082615epcas5p21fa62201d4d610608e286fcfce97118d@epcas5p2.samsung.com>
2017-02-13 8:26 ` [PATCH V3 1/4] Documetation: samsung-phy: add the exynos-pcie-phy binding Jaehoon Chung
[not found] ` <CGME20170213082615epcas5p2d6bc5521e68adf71bb64d9eb8262274d@epcas5p2.samsung.com>
2017-02-13 8:26 ` [PATCH V3 2/4] phy: phy-exynos-pcie: Add support for Exynos PCIe phy Jaehoon Chung
2017-02-15 5:24 ` Vivek Gautam
2017-02-15 22:29 ` Jaehoon Chung
[not found] ` <CGME20170213082615epcas5p24028ab4bd4fabbbcdf37ff36f0ee27a2@epcas5p2.samsung.com>
2017-02-13 8:26 ` [PATCH V3 3/4] Documetation: binding: modify the exynos5440 pcie binding Jaehoon Chung
[not found] ` <CGME20170213082616epcas5p2a20cca498e9ddde7c5d3f7664fb8606e@epcas5p2.samsung.com>
2017-02-13 8:26 ` [PATCH V3 4/4] PCI: exynos: support the using PHY generic framework Jaehoon Chung
2017-02-15 21:03 ` Bjorn Helgaas
2017-02-15 21:04 ` [PATCH V3 0/4] PCI: exynos: use the " Bjorn Helgaas
2017-02-15 21:11 ` Bjorn Helgaas
2017-02-15 22:33 ` Jaehoon Chung
2017-02-17 19:51 ` Bjorn Helgaas [this message]
2017-03-01 4:38 ` Kishon Vijay Abraham I
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=20170217195146.GA17762@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=bhelgaas@google.com \
--cc=cpgs@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=javier@osg.samsung.com \
--cc=jh80.chung@samsung.com \
--cc=jingoohan1@gmail.com \
--cc=kgene@kernel.org \
--cc=kishon@ti.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=niyas.ahmed@samsung.com \
--cc=pankaj.dubey@samsung.com \
--cc=robh+dt@kernel.org \
--cc=vivek.gautam@codeaurora.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).