Devicetree
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/6] PCI: J7200/J721E PCIe bindings
Date: Mon, 4 Jan 2021 08:51:37 -0600	[thread overview]
Message-ID: <20210104145137.wmtppcvjzu374yly@kahuna> (raw)
In-Reply-To: <d50fa957-7371-090a-754c-816760b43a27@ti.com>

On 18:52-20210104, Kishon Vijay Abraham I wrote:
> Nishanth,
> 
> On 04/01/21 6:46 pm, Nishanth Menon wrote:
> > On 18:40-20210104, Kishon Vijay Abraham I wrote:
> >> Nishanth,
> >>
> >> On 04/01/21 6:29 pm, Nishanth Menon wrote:
> >>> On 17:52-20210104, Kishon Vijay Abraham I wrote:
> >>>> Patch series adds DT nodes in order to get PCIe working in J7200.
> >>>> Also includes couple of fixes for J721e.
> >>>>
> >>>> v1 of the patch series can be found @ [1]
> >>>> v2 of the patch series can be found @ [2]
> >>>>
> >>>> Changes from v2:
> >>>> 1) Moved serdes_refclk node out of interconnect node and also replaced
> >>>>    "_" with "-"
> >>>>
> >>>> Changes from v1:
> >>>> 1) Include only the device tree patches here (the binding patch is sent
> >>>> separately)
> >>>> 2) Include couple of patches that fixes J721E DTS.
> >>>>
> >>>> [1] -> http://lore.kernel.org/r/20201102101154.13598-1-kishon@ti.com
> >>>> [2] -> http://lore.kernel.org/r/20201210130747.25436-1-kishon@ti.com
> >>>>
> >>>> Kishon Vijay Abraham I (6):
> >>>>   arm64: dts: ti: k3-j721e-main: Fix supported max outbound regions
> >>>>   arm64: dts: ti: k3-j721e-main: Remove "syscon" nodes added for
> >>>>     pcieX_ctrl
> >>>>   arm64: dts: ti: k3-j7200-main: Add SERDES and WIZ device tree node
> >>>>   arm64: dts: ti: k3-j7200-main: Add PCIe device tree node
> >>>>   arm64: dts: ti: k3-j7200-common-proc-board: Enable SERDES0
> >>>>   arm64: dts: ti: k3-j7200-common-proc-board: Enable PCIe
> >>>>
> >>>>  .../dts/ti/k3-j7200-common-proc-board.dts     |  38 ++++++
> >>>>  arch/arm64/boot/dts/ti/k3-j7200-main.dtsi     | 111 ++++++++++++++++++
> >>>>  arch/arm64/boot/dts/ti/k3-j721e-main.dtsi     |  52 ++------
> >>>>  3 files changed, 157 insertions(+), 44 deletions(-)
> >>>
> >>>
> >>> A bit confused on the dependency here. is there something merged into
> >>> next-20210104 that makes this series ready for pickup? is there a way
> >>> I can get a immutable tag for driver fixups to pull so that my dts
> >>> next is not broken for PCIe (I am assuming looking at the series that
> >>> this is probably not a backward compatible series?)?
> >>
> >> There are no driver changes for the basic J7200 PCIe support and the DT
> >> bindings are already merged [1].
> >>
> >> There are few errata fixes applicable for J721E which has to be removed
> >> for J7200 but that depends on other patches to be merged [1] but that
> >> doesn't impact j7200 functionality.
> >>
> >> [1] ->
> >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/pci/ti,j721e-pci-host.yaml#n19
> >> [2] -> http://lore.kernel.org/r/20201230120515.2348-1-nadeem@cadence.com
> > 
> > So, Dropping stuff like "cdns,max-outbound-regions" (change from 16 to
> > 32) will work on older kernels? Could you do a quick sanity check on the
> > couple of "fixes" patches in this thread is not breaking functionality
> > introduced in the older stable kernels?
> 
> Okay, the driver changes are done such that it works with both old DT
> and new DT however the newer DT will not work with old kernel. So I
> think I should drop the "Fixes" tag in the DT patches.

If there is a specific stable kernel version you might like to use, you
could use that as well for those stable tags (see [1])


[1] https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

  reply	other threads:[~2021-01-04 14:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04 12:22 [PATCH v3 0/6] PCI: J7200/J721E PCIe bindings Kishon Vijay Abraham I
2021-01-04 12:22 ` [PATCH v3 1/6] arm64: dts: ti: k3-j721e-main: Fix supported max outbound regions Kishon Vijay Abraham I
2021-01-04 12:55   ` Nishanth Menon
2021-01-04 12:22 ` [PATCH v3 2/6] arm64: dts: ti: k3-j721e-main: Remove "syscon" nodes added for pcieX_ctrl Kishon Vijay Abraham I
2021-01-04 12:22 ` [PATCH v3 3/6] arm64: dts: ti: k3-j7200-main: Add SERDES and WIZ device tree node Kishon Vijay Abraham I
2021-01-04 12:22 ` [PATCH v3 4/6] arm64: dts: ti: k3-j7200-main: Add PCIe " Kishon Vijay Abraham I
2021-01-04 12:22 ` [PATCH v3 5/6] arm64: dts: ti: k3-j7200-common-proc-board: Enable SERDES0 Kishon Vijay Abraham I
2021-01-04 12:22 ` [PATCH v3 6/6] arm64: dts: ti: k3-j7200-common-proc-board: Enable PCIe Kishon Vijay Abraham I
2021-01-04 12:59 ` [PATCH v3 0/6] PCI: J7200/J721E PCIe bindings Nishanth Menon
2021-01-04 13:10   ` Kishon Vijay Abraham I
2021-01-04 13:16     ` Nishanth Menon
2021-01-04 13:22       ` Kishon Vijay Abraham I
2021-01-04 14:51         ` Nishanth Menon [this message]
2021-01-04 15:31           ` Kishon Vijay Abraham I
2021-01-04 15:52             ` Nishanth Menon

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=20210104145137.wmtppcvjzu374yly@kahuna \
    --to=nm@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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