Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jayesh Choudhary <j-choudhary@ti.com>
To: Nishanth Menon <nm@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: Mon, 31 Jul 2023 16:34:03 +0530	[thread overview]
Message-ID: <bb60a183-8f05-34cb-d26e-15405a19da27@ti.com> (raw)
In-Reply-To: <20230728211217.mipwoira57g7dcc6@moody>

Hello Nishanth,

On 29/07/23 02:42, Nishanth Menon wrote:
> 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]
>>

[...]

>>
>> 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?
> 

Okay I will add support for AM69-SK too.

Thanks,
-Jayesh

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

      reply	other threads:[~2023-07-31 11:04 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 ` [PATCH v7 0/4] Add peripherals for J784S4 Nishanth Menon
2023-07-31 11:04   ` Jayesh Choudhary [this message]

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=bb60a183-8f05-34cb-d26e-15405a19da27@ti.com \
    --to=j-choudhary@ti.com \
    --cc=a-bhatia1@ti.com \
    --cc=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --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