Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Jayesh Choudhary <j-choudhary@ti.com>
Cc: <vigneshr@ti.com>, <s-vadapalli@ti.com>, <afd@ti.com>,
	<kristo@kernel.org>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
	<rogerq@kernel.org>, <a-bhatia1@ti.com>, <r-ravikumar@ti.com>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v7 0/4] Add peripherals for J784S4
Date: Fri, 28 Jul 2023 16:12:17 -0500	[thread overview]
Message-ID: <20230728211217.mipwoira57g7dcc6@moody> (raw)
In-Reply-To: <20230728050859.7370-1-j-choudhary@ti.com>

On 10:38-20230728, Jayesh Choudhary wrote:
> This series adds support for:
> - SERDES, WIZ DT nodes, Serdes lane control mux
> - DSS and DisplayPort-0 nodes
> 
> This support DEPENDS upon another series which was introduced as part
> of discussion in v5. That series[1] moves the ti-serdes headers file
> from bindings to "arch/arm64/boot/dts/ti". (That series is merged in
> linux-next tree)
> 
> Changelog v6->v7:
> - change compatible for scm_conf to 'simple-bus'
> - drop main_cpsw node due to driver dependency on [2]
> 
> Changelog v5->v6:
> - Change header file according to [1].
> - Add idle-state property in serdes_ln_ctrl node.
> - Fix dtbs_check warning due to clock-frequency property in serdes_refclk
>   node by disabling the node in main.dtsi and enabling it in board file
>   when the clock-frequency node is actually added.
> 
> Changelog v4->v5:
> - rebased the patches on linux-next tip.
> 
> Changelog v3->v4:
> - add reg property to serdes_ln_ctrl and fix the node name again to
>   get rid of dtbs_check error.
> - reorder reg, reg-names and ranges property for main_cpsw1.
> - correct the order for clocks in serdes_wiz nodes to fix dtbs_check
>   warnings.
> - fix indentation in reg, reg-names and clock property for dss node.
> - add comments for the reg type in dss registers.
> 
> Changelog v3->v2:
> - fix dtc warnings for 'scm_conf' and 'serdes_ln_ctrl' nodes
>   (Checked all the changes of the series with W=12 option during build)
> - added clock-frequency for serdes_refclk along with other EVM changes
>   This refclk is being used by all the instances of serdes_wiz which
>   are disabled by default. So configuring refclk when the serdes nodes
>   are used for the first time is okay.
> 
> Changelog v1->v2:
> - Moved J784S4 EVM changes together to the last patch
>   (Suggested by Andrew)
> 
> v5 patch link:
> <https://lore.kernel.org/all/20230721132029.123881-1-j-choudhary@ti.com/>
> 
> [1]: <https://lore.kernel.org/all/20230721125732.122421-1-j-choudhary@ti.com/>
> [2]: <https://lore.kernel.org/all/20230605154153.24025-1-afd@ti.com/>
> 
> Rahul T R (2):
>   arm64: dts: ti: k3-j784s4-main: Add DSS and DP-bridge node
>   arm64: dts: ti: k3-j784s4-evm: Enable DisplayPort-0
> 

Could you enable AM69-SK as well? is there anything stopping it being part of the series?

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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2023-07-28 21:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  5:08 [PATCH v7 0/4] Add peripherals for J784S4 Jayesh Choudhary
2023-07-28  5:08 ` [PATCH v7 1/4] arm64: dts: ti: k3-j784s4-main: Add system controller and SERDES lane mux Jayesh Choudhary
2023-07-28  5:08 ` [PATCH v7 2/4] arm64: dts: ti: k3-j784s4: Add WIZ and SERDES PHY nodes Jayesh Choudhary
2023-07-28  5:08 ` [PATCH v7 3/4] arm64: dts: ti: k3-j784s4-main: Add DSS and DP-bridge node Jayesh Choudhary
2023-07-28  5:08 ` [PATCH v7 4/4] arm64: dts: ti: k3-j784s4-evm: Enable DisplayPort-0 Jayesh Choudhary
2023-07-28 21:12 ` Nishanth Menon [this message]
2023-07-31 11:04   ` [PATCH v7 0/4] Add peripherals for J784S4 Jayesh Choudhary

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=20230728211217.mipwoira57g7dcc6@moody \
    --to=nm@ti.com \
    --cc=a-bhatia1@ti.com \
    --cc=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=j-choudhary@ti.com \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=r-ravikumar@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=s-vadapalli@ti.com \
    --cc=vigneshr@ti.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