All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jagan Teki <jagan@edgeble.ai>
Cc: Heiko Stuebner <heiko@sntech.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	Johan Jonker <jbx6244@gmail.com>,
	Jon Lin <jon.lin@rock-chips.com>,
	Sugar Zhang <sugar.zhang@rock-chips.com>
Subject: Re: [PATCH v7 06/10] ARM: dts: rockchip: Add Rockchip RV1126 SoC
Date: Thu, 24 Nov 2022 10:36:42 +0100	[thread overview]
Message-ID: <1f8eb33b-1979-ec28-e3cf-6e6552959b3a@linaro.org> (raw)
In-Reply-To: <CA+VMnFybPA=6-LvSDd=7EXk6fo4oY_hNBwCcDURgnFs4DP_hzA@mail.gmail.com>

On 23/11/2022 17:35, Jagan Teki wrote:

>>>>> +     aliases {
>>>>> +             i2c0 = &i2c0;
>>>>> +             serial0 = &uart0;
>>>>> +             serial1 = &uart1;
>>>>> +             serial2 = &uart2;
>>>>> +             serial3 = &uart3;
>>>>> +             serial4 = &uart4;
>>>>> +             serial5 = &uart5;
>>>>
>>>> These are not properties of a SoC but board. They depend on the
>>>> particular routing on the board... unless this SoC is an exception from
>>>> all others?
>>>
>>> Was this a new feature to follow, didn't see this before at least
>>> rockchip SoC's.
>>>
>>
>> It's not exactly new comment, but rather not always enforced/given.
> 
> It seems like i2c0 and serial aliases are required across SoC instead
> of the specific board. An example of which i2c0 connected via PMIC
> which indeed require aliases to get a probe, which is common across
> SoC.
> 
> [    1.778941] i2c_dev: i2c /dev entries driver
> [    1.780877] rk3x-i2c ff3f0000.i2c: rk3x-i2c needs i2cX alias
> [    1.781410] rk3x-i2c: probe of ff3f0000.i2c failed with error -22
> [    1.791312] Bluetooth: HCI UART driver ver 2.3

I2C driver indeed seems to require them, so then it's fine. That's not
the argument for serials though.

Best regards,
Krzysztof


WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jagan Teki <jagan@edgeble.ai>
Cc: Heiko Stuebner <heiko@sntech.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	Johan Jonker <jbx6244@gmail.com>,
	Jon Lin <jon.lin@rock-chips.com>,
	Sugar Zhang <sugar.zhang@rock-chips.com>
Subject: Re: [PATCH v7 06/10] ARM: dts: rockchip: Add Rockchip RV1126 SoC
Date: Thu, 24 Nov 2022 10:36:42 +0100	[thread overview]
Message-ID: <1f8eb33b-1979-ec28-e3cf-6e6552959b3a@linaro.org> (raw)
In-Reply-To: <CA+VMnFybPA=6-LvSDd=7EXk6fo4oY_hNBwCcDURgnFs4DP_hzA@mail.gmail.com>

On 23/11/2022 17:35, Jagan Teki wrote:

>>>>> +     aliases {
>>>>> +             i2c0 = &i2c0;
>>>>> +             serial0 = &uart0;
>>>>> +             serial1 = &uart1;
>>>>> +             serial2 = &uart2;
>>>>> +             serial3 = &uart3;
>>>>> +             serial4 = &uart4;
>>>>> +             serial5 = &uart5;
>>>>
>>>> These are not properties of a SoC but board. They depend on the
>>>> particular routing on the board... unless this SoC is an exception from
>>>> all others?
>>>
>>> Was this a new feature to follow, didn't see this before at least
>>> rockchip SoC's.
>>>
>>
>> It's not exactly new comment, but rather not always enforced/given.
> 
> It seems like i2c0 and serial aliases are required across SoC instead
> of the specific board. An example of which i2c0 connected via PMIC
> which indeed require aliases to get a probe, which is common across
> SoC.
> 
> [    1.778941] i2c_dev: i2c /dev entries driver
> [    1.780877] rk3x-i2c ff3f0000.i2c: rk3x-i2c needs i2cX alias
> [    1.781410] rk3x-i2c: probe of ff3f0000.i2c failed with error -22
> [    1.791312] Bluetooth: HCI UART driver ver 2.3

I2C driver indeed seems to require them, so then it's fine. That's not
the argument for serials though.

Best regards,
Krzysztof


_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jagan Teki <jagan@edgeble.ai>
Cc: Heiko Stuebner <heiko@sntech.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	Johan Jonker <jbx6244@gmail.com>,
	Jon Lin <jon.lin@rock-chips.com>,
	Sugar Zhang <sugar.zhang@rock-chips.com>
Subject: Re: [PATCH v7 06/10] ARM: dts: rockchip: Add Rockchip RV1126 SoC
Date: Thu, 24 Nov 2022 10:36:42 +0100	[thread overview]
Message-ID: <1f8eb33b-1979-ec28-e3cf-6e6552959b3a@linaro.org> (raw)
In-Reply-To: <CA+VMnFybPA=6-LvSDd=7EXk6fo4oY_hNBwCcDURgnFs4DP_hzA@mail.gmail.com>

On 23/11/2022 17:35, Jagan Teki wrote:

>>>>> +     aliases {
>>>>> +             i2c0 = &i2c0;
>>>>> +             serial0 = &uart0;
>>>>> +             serial1 = &uart1;
>>>>> +             serial2 = &uart2;
>>>>> +             serial3 = &uart3;
>>>>> +             serial4 = &uart4;
>>>>> +             serial5 = &uart5;
>>>>
>>>> These are not properties of a SoC but board. They depend on the
>>>> particular routing on the board... unless this SoC is an exception from
>>>> all others?
>>>
>>> Was this a new feature to follow, didn't see this before at least
>>> rockchip SoC's.
>>>
>>
>> It's not exactly new comment, but rather not always enforced/given.
> 
> It seems like i2c0 and serial aliases are required across SoC instead
> of the specific board. An example of which i2c0 connected via PMIC
> which indeed require aliases to get a probe, which is common across
> SoC.
> 
> [    1.778941] i2c_dev: i2c /dev entries driver
> [    1.780877] rk3x-i2c ff3f0000.i2c: rk3x-i2c needs i2cX alias
> [    1.781410] rk3x-i2c: probe of ff3f0000.i2c failed with error -22
> [    1.791312] Bluetooth: HCI UART driver ver 2.3

I2C driver indeed seems to require them, so then it's fine. That's not
the argument for serials though.

Best regards,
Krzysztof


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

  reply	other threads:[~2022-11-24  9:36 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08  4:13 [PATCH v7 00/10] ARM: Add Rockchip RV1126 support Jagan Teki
2022-11-08  4:13 ` Jagan Teki
2022-11-08  4:13 ` Jagan Teki
2022-11-08  4:13 ` [PATCH v7 01/10] dt-bindings: arm: rockchip: Add pmu compatible for rv1126 Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08 18:09   ` Krzysztof Kozlowski
2022-11-08 18:09     ` Krzysztof Kozlowski
2022-11-08 18:09     ` Krzysztof Kozlowski
2022-11-08  4:13 ` [PATCH v7 02/10] dt-bindings: mmc: rockchip-dw-mshc: Add power-domains property Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08 18:09   ` Krzysztof Kozlowski
2022-11-08 18:09     ` Krzysztof Kozlowski
2022-11-08 18:09     ` Krzysztof Kozlowski
2022-11-09 12:34   ` Ulf Hansson
2022-11-09 12:34     ` Ulf Hansson
2022-11-09 12:34     ` Ulf Hansson
2022-11-08  4:13 ` [PATCH v7 03/10] dt-bindings: iio: adc: rockchip-saradc: Add saradc for rv1126 Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08 18:09   ` Krzysztof Kozlowski
2022-11-08 18:09     ` Krzysztof Kozlowski
2022-11-08 18:09     ` Krzysztof Kozlowski
2022-11-12 17:41     ` Jonathan Cameron
2022-11-12 17:41       ` Jonathan Cameron
2022-11-12 17:41       ` Jonathan Cameron
2022-11-08  4:13 ` [PATCH v7 04/10] dt-bindings: timer: rk-timer: Add rktimer " Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08 18:10   ` Krzysztof Kozlowski
2022-11-08 18:10     ` Krzysztof Kozlowski
2022-11-08 18:10     ` Krzysztof Kozlowski
2022-11-08  4:13 ` [PATCH v7 05/10] ARM: dts: rockchip: Add Rockchip RV1126 pinctrl Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08  4:13 ` [PATCH v7 06/10] ARM: dts: rockchip: Add Rockchip RV1126 SoC Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08 18:13   ` Krzysztof Kozlowski
2022-11-08 18:13     ` Krzysztof Kozlowski
2022-11-08 18:13     ` Krzysztof Kozlowski
2022-11-15  6:38     ` Jagan Teki
2022-11-15  6:38       ` Jagan Teki
2022-11-15  6:38       ` Jagan Teki
2022-11-15  7:55       ` Krzysztof Kozlowski
2022-11-15  7:55         ` Krzysztof Kozlowski
2022-11-15  7:55         ` Krzysztof Kozlowski
2022-11-23 16:35         ` Jagan Teki
2022-11-23 16:35           ` Jagan Teki
2022-11-23 16:35           ` Jagan Teki
2022-11-24  9:36           ` Krzysztof Kozlowski [this message]
2022-11-24  9:36             ` Krzysztof Kozlowski
2022-11-24  9:36             ` Krzysztof Kozlowski
2022-11-27 13:55             ` Jagan Teki
2022-11-27 13:55               ` Jagan Teki
2022-11-27 13:55               ` Jagan Teki
2022-11-08 20:17   ` Johan Jonker
2022-11-08 20:17     ` Johan Jonker
2022-11-08 20:17     ` Johan Jonker
2022-11-14  9:35     ` Jagan Teki
2022-11-14  9:35       ` Jagan Teki
2022-11-14  9:35       ` Jagan Teki
2022-11-08  4:13 ` [PATCH v7 07/10] dt-bindings: vendor-prefixes: Add Edgeble AI Technologies Pvt. Ltd Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08  4:13 ` [PATCH v7 08/10] dt-bindings: arm: rockchip: Add Edgeble Neural Compute Module 2 Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08  4:13 ` [PATCH v7 09/10] ARM: dts: rockchip: rv1126: Add Edgeble Neural Compute Module 2(Neu2) Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08  4:13   ` Jagan Teki
2022-11-08  4:14 ` [PATCH v7 10/10] ARM: dts: rockchip: rv1126: Add Edgeble Neural Compute Module 2(Neu2) IO Jagan Teki
2022-11-08  4:14   ` Jagan Teki
2022-11-08  4:14   ` Jagan Teki

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=1f8eb33b-1979-ec28-e3cf-6e6552959b3a@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=jagan@edgeble.ai \
    --cc=jbx6244@gmail.com \
    --cc=jon.lin@rock-chips.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=sugar.zhang@rock-chips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.