mbox series

[V3,0/6] ARM: dts: imx6ull: Add chargebyte Tarragon support

Message ID 20230331095715.5988-1-stefan.wahren@chargebyte.com
Headers show
Series ARM: dts: imx6ull: Add chargebyte Tarragon support | expand

Message

Stefan Wahren March 31, 2023, 9:57 a.m. UTC
This series adds the support for chargebyte Tarragon, which is an Electrical
Vehicle Supply Equipment (EVSE) for AC charging stations
(according to IEC 61851, ISO 15118).

The Tarragon board is based on an i.MX6ULL SoC and is available in
4 variants (Master, Slave, SlaveXT, Micro), which provide more or
less peripherals.

Supported features:
  * 512 MB DDR RAM
  * eMMC
  * Debug UART
  * 100 Mbit Ethernet
  * USB 2.0 Host interface
  * Powerline communication (QCA700x)
  * 2x RS485
  * Digital in- and outputs (12 V)
  * One-Wire master for external temp sensors
  * 2x relay outputs
  * 2x motor interfaces
  
The Tarragon hardware is bundled with a charging stack under the name Charge Control C: 
https://chargebyte.com/products/charging-station-communication/charge-control-c

This series is rebased on top of:
https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git?h=for-next

Changes in V3:
- dropped already applied iio patches
- renamed pinctrl_qca700x_mains_spi to pinctrl_ecspi4
- dropped Tarragon container nodes as suggested by Shawn
- sort the pinctrl groups alphabetically also suggested by Shawn

Changes in V2:
- after fixing technical problems send patches directly from chargebyte address
  and drop the related signed-off-by
- add Krzysztof's Acked-by
- improve commit messages (patch 3, 4, 5)
- make iis328dq fallback to lis331dl as suggested by Jonathan
- fix order of Tarragon entries in FSL schema
- improve Tarragon led node names and drop label as suggested by Krzysztof
- change Tarragon SVNS pinctrl settings after internal discussion
  with chargebyte hardware team
- drop broken-cd in Tarragon common DTSI which is not necessary for eMMC
- add no-sd and no-sdio for eMMC interface of Tarragon

Stefan Wahren (6):
  dt-bindings: vendor-prefixes: add chargebyte
  dt-bindings: Add DS2482/DS2484 as trivial device
  w1: ds2482: add i2c id for DS2484
  dt-bindings: ARM: fsl: Add chargebyte Tarragon
  ARM: dts: imx6ull: Add chargebyte Tarragon support
  ARM: imx_v6_v7_defconfig: Enable Tarragon peripheral drivers

 .../devicetree/bindings/arm/fsl.yaml          |   9 +
 .../devicetree/bindings/trivial-devices.yaml  |   4 +
 .../devicetree/bindings/vendor-prefixes.yaml  |   2 +
 arch/arm/boot/dts/Makefile                    |   4 +
 .../arm/boot/dts/imx6ull-tarragon-common.dtsi | 852 ++++++++++++++++++
 arch/arm/boot/dts/imx6ull-tarragon-master.dts |  82 ++
 arch/arm/boot/dts/imx6ull-tarragon-micro.dts  |  10 +
 arch/arm/boot/dts/imx6ull-tarragon-slave.dts  |  32 +
 .../arm/boot/dts/imx6ull-tarragon-slavext.dts |  64 ++
 arch/arm/configs/imx_v6_v7_defconfig          |   6 +
 drivers/w1/masters/ds2482.c                   |   1 +
 11 files changed, 1066 insertions(+)
 create mode 100644 arch/arm/boot/dts/imx6ull-tarragon-common.dtsi
 create mode 100644 arch/arm/boot/dts/imx6ull-tarragon-master.dts
 create mode 100644 arch/arm/boot/dts/imx6ull-tarragon-micro.dts
 create mode 100644 arch/arm/boot/dts/imx6ull-tarragon-slave.dts
 create mode 100644 arch/arm/boot/dts/imx6ull-tarragon-slavext.dts

Comments

Krzysztof Kozlowski March 31, 2023, 10:05 a.m. UTC | #1
On 31/03/2023 11:57, Stefan Wahren wrote:
> This adds the compatibles for the chargebyte Tarragon boards.
> 
> Signed-off-by: Stefan Wahren <stefan.wahren@chargebyte.com>
> ---


This is a friendly reminder during the review process.

It looks like you received a tag and forgot to add it.

If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new
versions. However, there's no need to repost patches *only* to add the
tags. The upstream maintainer will do that for acks received on the
version they apply.

https://elixir.bootlin.com/linux/v5.17/source/Documentation/process/submitting-patches.rst#L540

If a tag was not added on purpose, please state why and what changed.


Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>


Best regards,
Krzysztof
Rob Herring March 31, 2023, 3:49 p.m. UTC | #2
On Fri, Mar 31, 2023 at 4:58 AM Stefan Wahren
<stefan.wahren@chargebyte.com> wrote:
>
> Both chips are I2C to 1-wire bridges.
>
> Signed-off-by: Stefan Wahren <stefan.wahren@chargebyte.com>
> Cc: Steffen Trumtrar <s.trumtrar@pengutronix.de>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
>  Documentation/devicetree/bindings/trivial-devices.yaml | 4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml b/Documentation/devicetree/bindings/trivial-devices.yaml
> index 6f482a254a1d..9b7b24989359 100644
> --- a/Documentation/devicetree/bindings/trivial-devices.yaml
> +++ b/Documentation/devicetree/bindings/trivial-devices.yaml
> @@ -183,6 +183,10 @@ properties:
>            - maxim,ds1803-050
>              # 100 kOhm digital potentiometer with I2C interface
>            - maxim,ds1803-100
> +            # I2C to 1-wire bridge
> +          - maxim,ds2482
> +            # I2C to 1-wire bridge
> +          - maxim,ds2484

A 1-wire device isn't really trivial because it can have child nodes.
You're probably not the first here, but don't add more.

You could do a "trivial 1-wire devices" schema similar to trivial RTC
device schema.

Rob
Stefan Wahren March 31, 2023, 6:25 p.m. UTC | #3
Hi Rob,

Am 31.03.23 um 17:49 schrieb Rob Herring:
> On Fri, Mar 31, 2023 at 4:58 AM Stefan Wahren
> <stefan.wahren@chargebyte.com> wrote:
>>
>> Both chips are I2C to 1-wire bridges.
>>
>> Signed-off-by: Stefan Wahren <stefan.wahren@chargebyte.com>
>> Cc: Steffen Trumtrar <s.trumtrar@pengutronix.de>
>> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> ---
>>   Documentation/devicetree/bindings/trivial-devices.yaml | 4 ++++
>>   1 file changed, 4 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml b/Documentation/devicetree/bindings/trivial-devices.yaml
>> index 6f482a254a1d..9b7b24989359 100644
>> --- a/Documentation/devicetree/bindings/trivial-devices.yaml
>> +++ b/Documentation/devicetree/bindings/trivial-devices.yaml
>> @@ -183,6 +183,10 @@ properties:
>>             - maxim,ds1803-050
>>               # 100 kOhm digital potentiometer with I2C interface
>>             - maxim,ds1803-100
>> +            # I2C to 1-wire bridge
>> +          - maxim,ds2482
>> +            # I2C to 1-wire bridge
>> +          - maxim,ds2484
> 
> A 1-wire device isn't really trivial because it can have child nodes.
> You're probably not the first here, but don't add more.
> 
> You could do a "trivial 1-wire devices" schema similar to trivial RTC
> device schema.

okay. After thinking more about this, it isn't a trivial device at all. 
I will make a dedicated schema for this.

Best regards

> 
> Rob