Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <f1e54167-15bd-8a0b-454d-53b90b18a343@ti.com>
Date:   Mon, 5 Jun 2023 22:31:17 +0530
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.10.1
Subject: Re: [PATCH 03/12] arm64: dts: ti: k3-j721e-beagleboneai64: Fixup
 reference to phandles array
Content-Language: en-US
To:     Nishanth Menon <nm@ti.com>, Conor Dooley <conor+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Rob Herring <robh+dt@kernel.org>
CC:     <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
        <linux-arm-kernel@lists.infradead.org>,
        Tero Kristo <kristo@kernel.org>,
        Vignesh Raghavendra <vigneshr@ti.com>,
        Robert Nelson <robertcnelson@gmail.com>
References: <20230601152636.858553-1-nm@ti.com>
 <20230601152636.858553-4-nm@ti.com>
From:   "Kumar, Udit" <u-kumar1@ti.com>
In-Reply-To: <20230601152636.858553-4-nm@ti.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi Nishanth

On 6/1/2023 8:56 PM, Nishanth Menon wrote:
> When referring to array of phandles, using <> to separate the array
> entries is better notation as it makes potential errors with phandle and
> cell arguments easier to catch. Fix the outliers to be consistent with
> the rest of the usage.
>
> Cc: Robert Nelson <robertcnelson@gmail.com>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
>   .../boot/dts/ti/k3-j721e-beagleboneai64.dts   | 29 ++++++++++---------
>   1 file changed, 15 insertions(+), 14 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dts b/arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dts
> index 37c24b077b6a..c13246a9ed8f 100644
> --- a/arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dts
> +++ b/arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dts
> @@ -593,7 +593,7 @@ &main_i2c0 {
>   &main_i2c1 {
>   	status = "okay";
>   	pinctrl-names = "default";
> -	pinctrl-0 = <&main_i2c1_pins_default &csi1_gpio_pins_default>;
> +	pinctrl-0 = <&main_i2c1_pins_default>, <&csi1_gpio_pins_default>;
>   	clock-frequency = <400000>;
>   };
>   
> @@ -623,7 +623,7 @@ &main_i2c4 {
>   &main_i2c5 {
>   	status = "okay";
>   	pinctrl-names = "default";
> -	pinctrl-0 = <&main_i2c5_pins_default &csi0_gpio_pins_default>;
> +	pinctrl-0 = <&main_i2c5_pins_default>, <&csi0_gpio_pins_default>;
>   	clock-frequency = <400000>;
>   };
>   
> @@ -639,7 +639,7 @@ &main_i2c6 {
>   &wkup_i2c0 {
>   	status = "okay";
>   	pinctrl-names = "default";
> -	pinctrl-0 = <&wkup_i2c0_pins_default &eeprom_wp_pins_default>;
> +	pinctrl-0 = <&wkup_i2c0_pins_default>, <&eeprom_wp_pins_default>;
>   	clock-frequency = <400000>;

Why we need more than 2 pio lines for i2c node ,


> [...]
>