* arm64: dts: blaize-blzp1600: Enable GPIO support [not found] <20250327-kernel-upstreaming-add_gpio_support-v2-0-2c45a1acdc0c@blaize.com> @ 2025-05-05 14:14 ` Nikolaos Pasaloukos 2025-05-05 14:17 ` Krzysztof Kozlowski 0 siblings, 1 reply; 4+ messages in thread From: Nikolaos Pasaloukos @ 2025-05-05 14:14 UTC (permalink / raw) To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, James Cowgill, Matt Redfearn, Neil Jones, Matt Redfearn, soc@lists.linux.dev Cc: Nikolaos Pasaloukos, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Blaize BLZP1600 uses the custom silicon provided from VeriSilicon to add GPIO support. This interface is used to control signals on many other peripherals, such as Ethernet, USB, SD and eMMC. Signed-off-by: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com> --- I am re-sending the patch to include the soc list. The original patchset has already been applied but not this patch. Arnd, could you please apply or do I need someone to review? --- arch/arm64/boot/dts/blaize/blaize-blzp1600-cb2.dts | 36 ++++++++++++++++++++++ arch/arm64/boot/dts/blaize/blaize-blzp1600.dtsi | 12 ++++++++ 2 files changed, 48 insertions(+) diff --git a/arch/arm64/boot/dts/blaize/blaize-blzp1600-cb2.dts b/arch/arm64/boot/dts/blaize/blaize-blzp1600-cb2.dts index 7e3cef2ed3522e202487e799b2021cd45398e006..fb5415eb347a028fc65090027a4c4fc89c8280f5 100644 --- a/arch/arm64/boot/dts/blaize/blaize-blzp1600-cb2.dts +++ b/arch/arm64/boot/dts/blaize/blaize-blzp1600-cb2.dts @@ -81,3 +81,39 @@ gpio_expander_m2: gpio@75 { "UART1_TO_RSP"; /* GPIO_15 */ }; }; + +&gpio0 { + status = "okay"; + gpio-line-names = "PERST_N", /* GPIO_0 */ + "LM96063_ALERT_N", /* GPIO_1 */ + "INA3221_PV", /* GPIO_2 */ + "INA3221_CRIT", /* GPIO_3 */ + "INA3221_WARN", /* GPIO_4 */ + "INA3221_TC", /* GPIO_5 */ + "QSPI0_RST_N", /* GPIO_6 */ + "LM96063_TCRIT_N", /* GPIO_7 */ + "DSI_TCH_INT", /* GPIO_8 */ + "DSI_RST", /* GPIO_9 */ + "DSI_BL", /* GPIO_10 */ + "DSI_INT", /* GPIO_11 */ + "ETH_RST", /* GPIO_12 */ + "CSI0_RST", /* GPIO_13 */ + "CSI0_PWDN", /* GPIO_14 */ + "CSI1_RST", /* GPIO_15 */ + "CSI1_PWDN", /* GPIO_16 */ + "CSI2_RST", /* GPIO_17 */ + "CSI2_PWDN", /* GPIO_18 */ + "CSI3_RST", /* GPIO_19 */ + "CSI3_PWDN", /* GPIO_20 */ + "ADAC_RST", /* GPIO_21 */ + "SD_SW_VDD", /* GPIO_22 */ + "SD_PON_VDD", /* GPIO_23 */ + "GPIO_EXP_INT", /* GPIO_24 */ + "BOARD_ID_0", /* GPIO_25 */ + "SDIO1_SW_VDD", /* GPIO_26 */ + "SDIO1_PON_VDD", /* GPIO_27 */ + "SDIO2_SW_VDD", /* GPIO_28 */ + "SDIO2_PON_VDD", /* GPIO_29 */ + "BOARD_ID_1", /* GPIO_30 */ + "BOARD_ID_2"; /* GPIO_31 */ +}; diff --git a/arch/arm64/boot/dts/blaize/blaize-blzp1600.dtsi b/arch/arm64/boot/dts/blaize/blaize-blzp1600.dtsi index 7d399e6a532f5b24385dd837be965be771c7d24c..5a6c882b2f57d57d304869dee877c996cbabb712 100644 --- a/arch/arm64/boot/dts/blaize/blaize-blzp1600.dtsi +++ b/arch/arm64/boot/dts/blaize/blaize-blzp1600.dtsi @@ -120,6 +120,18 @@ gic: interrupt-controller@410000 { IRQ_TYPE_LEVEL_LOW)>; }; + gpio0: gpio@4c0000 { + compatible = "blaize,blzp1600-gpio"; + reg = <0x4c0000 0x1000>; + gpio-controller; + #gpio-cells = <2>; + ngpios = <32>; + interrupts = <GIC_SPI 3 IRQ_TYPE_LEVEL_HIGH>; + interrupt-controller; + #interrupt-cells = <2>; + status = "disabled"; + }; + uart0: serial@4d0000 { compatible = "ns16550a"; reg = <0x4d0000 0x1000>; -- 2.43.0 ^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: arm64: dts: blaize-blzp1600: Enable GPIO support 2025-05-05 14:14 ` arm64: dts: blaize-blzp1600: Enable GPIO support Nikolaos Pasaloukos @ 2025-05-05 14:17 ` Krzysztof Kozlowski 2025-05-05 14:43 ` Nikolaos Pasaloukos 0 siblings, 1 reply; 4+ messages in thread From: Krzysztof Kozlowski @ 2025-05-05 14:17 UTC (permalink / raw) To: Nikolaos Pasaloukos, Rob Herring, Krzysztof Kozlowski, Conor Dooley, James Cowgill, Matt Redfearn, Neil Jones, soc@lists.linux.dev Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org On 05/05/2025 16:14, Nikolaos Pasaloukos wrote: > Blaize BLZP1600 uses the custom silicon provided from > > VeriSilicon to add GPIO support. > > This interface is used to control signals on many other > > peripherals, such as Ethernet, USB, SD and eMMC. > > > Signed-off-by: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com> Entire patch is corrupted by your mail server. Please switch to b4 relay if your mail server is not capable of sending emails (like Microsoft Outlook). Please use standard email subjects, so with the PATCH keyword in the title. `git format-patch -vX` helps here to create proper versioned patches. Another useful tool is b4. Skipping the PATCH keyword makes filtering of emails more difficult thus making the review process less convenient. > > --- > > I am re-sending the patch to include the soc list. The original patchset > > has already been applied but not this patch. > > Arnd, could you please apply or do I need someone to review? Platform maintainers are responsible for the patches for their platform. Any reason why this is not working for blaize? Best regards, Krzysztof ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: arm64: dts: blaize-blzp1600: Enable GPIO support 2025-05-05 14:17 ` Krzysztof Kozlowski @ 2025-05-05 14:43 ` Nikolaos Pasaloukos 2025-05-05 14:48 ` Krzysztof Kozlowski 0 siblings, 1 reply; 4+ messages in thread From: Nikolaos Pasaloukos @ 2025-05-05 14:43 UTC (permalink / raw) To: Krzysztof Kozlowski, Rob Herring, Krzysztof Kozlowski, Conor Dooley, James Cowgill, Matt Redfearn, Neil Jones, soc@lists.linux.dev Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org On 05/05/2025 15:17, Krzysztof Kozlowski wrote: > On 05/05/2025 16:14, Nikolaos Pasaloukos wrote: >> Blaize BLZP1600 uses the custom silicon provided from >> >> VeriSilicon to add GPIO support. >> >> This interface is used to control signals on many other >> >> peripherals, such as Ethernet, USB, SD and eMMC. >> >> >> Signed-off-by: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com> > Entire patch is corrupted by your mail server. Please switch to b4 relay > if your mail server is not capable of sending emails (like Microsoft > Outlook). > > Please use standard email subjects, so with the PATCH keyword in the > title. `git format-patch -vX` helps here to create proper versioned > patches. Another useful tool is b4. Skipping the PATCH keyword makes > filtering of emails more difficult thus making the review process less > convenient. I was expecting b4 to be able to send a single patch without a cover letter but I couldn't find how to do it, so I decided to send the .eml file produced by b4 with git send-email which obviously didn't work. Apologies for that. > >> --- >> >> I am re-sending the patch to include the soc list. The original patchset >> >> has already been applied but not this patch. >> >> Arnd, could you please apply or do I need someone to review? > Platform maintainers are responsible for the patches for their platform. > Any reason why this is not working for blaize? > > Best regards, > Krzysztof I am the platform maintainer for blaize but I haven't created an account yet on the kernel.org and according to Arnd it should be OK to submit the patches for inclusion (until I get an account) by sending them to the soc@lists.linux.dev. So, what would be preferable? To send only this patch with b4 or resend the v2 patchset which have been accepted and add the soc list? Kind regards, Nikolaos Pasaloukos ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: arm64: dts: blaize-blzp1600: Enable GPIO support 2025-05-05 14:43 ` Nikolaos Pasaloukos @ 2025-05-05 14:48 ` Krzysztof Kozlowski 0 siblings, 0 replies; 4+ messages in thread From: Krzysztof Kozlowski @ 2025-05-05 14:48 UTC (permalink / raw) To: Nikolaos Pasaloukos, Rob Herring, Krzysztof Kozlowski, Conor Dooley, James Cowgill, Matt Redfearn, Neil Jones, soc@lists.linux.dev Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org On 05/05/2025 16:43, Nikolaos Pasaloukos wrote: >> >>> --- >>> >>> I am re-sending the patch to include the soc list. The original patchset >>> >>> has already been applied but not this patch. >>> >>> Arnd, could you please apply or do I need someone to review? >> Platform maintainers are responsible for the patches for their platform. >> Any reason why this is not working for blaize? >> >> Best regards, >> Krzysztof > > I am the platform maintainer for blaize but I haven't created an account > yet on the kernel.org and according to Arnd it should be OK to submit the > patches for inclusion (until I get an account) by sending them to the > soc@lists.linux.dev. > > So, what would be preferable? To send only this patch with b4 or resend > the v2 patchset which have been accepted and add the soc list? soc@ is for applying patches, but your Cc list here suggest you send something for review. These are two different processes, see soc maintainer profile. You need to handle the patches (collect them) after community review *and then* you send these to soc@, without ccing again entire community. See any other pull requests or patch-pull emails. Best regards, Krzysztof ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2025-05-05 14:48 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20250327-kernel-upstreaming-add_gpio_support-v2-0-2c45a1acdc0c@blaize.com>
2025-05-05 14:14 ` arm64: dts: blaize-blzp1600: Enable GPIO support Nikolaos Pasaloukos
2025-05-05 14:17 ` Krzysztof Kozlowski
2025-05-05 14:43 ` Nikolaos Pasaloukos
2025-05-05 14:48 ` Krzysztof Kozlowski
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox