Hi Caleb,

+CC: Philip and Utsav, it looks like git-email did not pick up the cc
output from get_maintainer.pl.

On Thu, Feb 5, 2026 at 11:58 AM Caleb Ethridge <[email protected]> wrote:
>
> From: Caleb Ethridge <[email protected]>
> Date: Tue, 3 Feb 2026 14:45:53 -0500
> Subject: [PATCH] arm: dts: sc594: Update sc594 EZKIT GPIO polarities
>
> Updates the polarities for the GPIOs on the sc594
> EZKIT, as the current version was still on an old
> revision of the hardware. The GPIOs now match the
> sc598 EZKIT as expected.
>
> Fixes: be79378 ("board: adi: Add support for SC594")
>
> Signed-off-by: Caleb Ethridge <[email protected]>

Can we add a bit more detail to the commit message? Were the GPIO
polarities incorrect before, or are the polarities different between
two revisions of the SOM? We want to make sure that if a customer with
an older SOM uses mainline and finds that they cannot access octal spi
flash, that they can find information saying specifically that their
version is not supported by default.

>   octal {
>   gpio-hog;
> - gpios = <8 GPIO_ACTIVE_HIGH>;
> + gpios = <8 GPIO_ACTIVE_LOW>;
>   output-low;
>   line-name = "octal-spi-cs-en";
>   bootph-pre-ram;
> --
> 2.34.1

I assume this will be similar to the corresponding change for the
SC598 that I mentioned caused all SPI flash to stop working for me on
Rev C/D. Luckily on the SC594 SOM the flash conflict is different, so
I don't anticipate it to prevent it from running entirely, but I do
want people to know why if they see strange behavior.

Thanks,
Greg

Reply via email to