Re: [PATCH 0/2] arm64: dts: renesas: Add SD/OE pin properties

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Sep 26, 2024 at 1:24 PM Sean Anderson <sean.anderson@xxxxxxxxx> wrote:
>
> On 9/26/24 14:09, Sean Anderson wrote:
> > Linux can configure almost every part of this clock generator without
> > relying on the OTP settings. However, the correct configuration for the
> > SD/OE pin cannot be determined automatically. Therefore, add the
> > appropriate properties to configure this pin.
> >
> > I have CC'd some people who appear to have access to the following
> > boards which use the versaclock5:
> >
> > - Salvator-X
> > - HiHope RZ/G2[MN] Main Board
> > - Beacon Embedded Works RZ/G2N Development Kit
> >
> > as I could not find schematics for these boards. You can help me out by
> > (pick one):
> >
> > - Run the following command and send me the output:
> >
> >     $ grep 10: /sys/kernel/debug/regmap/*-006a/registers

Without any of the patches from this series, for the Beacon RZ/G2 Boards:

grep 10: /sys/kernel/debug/regmap/*-006a/registers
/sys/kernel/debug/regmap/2-006a/registers:10: a0
/sys/kernel/debug/regmap/4-006a/registers:10: a0

> >
> > - Measure the voltage on the SD/OE pin on a functioning board.
> > - Inspect (or send me) the schematic to determine the state of the SD/OE
> >   pin during normal operation.

The SD/OE pins on the Beacon boards are not tied high by default.
They have an optional pull-up resistor, but it is not populated by
default.

adam
> >
> > My suspicion is that all of these boards use the same configuration
> > (SD/OE pin tied high) owing to their common design heritage. Thanks in
> > advance.
>
> +CC the people I meant to CC in the first place





[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]


  Powered by Linux