[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <706a8f30-847c-2641-aeee-6c4d4692e573@gmail.com>
Date: Tue, 3 Oct 2023 18:17:48 +0530
From: Ayush Singh <ayushdevel1325@...il.com>
To: Nishanth Menon <nm@...com>
Cc: greybus-dev@...ts.linaro.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org,
vaishnav@...gleboard.org, jkridner@...gleboard.org,
krzysztof.kozlowski+dt@...aro.org, vigneshr@...com,
kristo@...nel.org, robh+dt@...nel.org, conor+dt@...nel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v6 1/3] dt-bindings: Add beaglecc1352
>> +
>> + reset-gpios:
>> + maxItems: 1
>> +
>> + power-gpios:
>> + maxItems: 3
>> + description:
>> + The device has three power rails that are exposed on external pins VDDS,
>> + VDDR and DCOUPL.
> Shouldn't these be regulators? The power rails are input to the MCU,
> correct?
> The properties should be something like:
> vdds-supply
> vddr-supply
> dcoupl-supply ? (not sure what dcoupl is, but description should provide
> that info).
>
> the gpio controls for those can be modelled by regulator-gpio ?
I picked up power lines from "CC13xx/CC26xx Hardware Configuration and
PCB Design Considerations Application Report" present under "8.14
Network Processor" of CC1352P7 data sheet.
But now looking closer, it doesn't seem like DCOUPL can be supplied
externally for CC1352P7 and thus should probably be removed.
Also, it seems like for CC1352P7, VDDR must always be supplied
internally (The data sheet states: "Internal supply, must be powered
from the internal DC/DC converter or the internal LDO"). Thus, it should
be safe to remove VDDR as well.
That means only VDDS needs to be present for power line.
CC13xx/CC26xx Hardware Configuration and PCB Design Considerations
Application Report: https://www.ti.com/lit/pdf/swra640
CC1352P7 Data sheet: https://www.ti.com/lit/gpn/CC1352P7
Sincerely,
Ayush Singh
Powered by blists - more mailing lists