On Fri, 15 Mar 2024 at 20:43, Stephan Gerhold <stephan@xxxxxxxxxxx> wrote:
>
> On Fri, Mar 15, 2024 at 11:37:07AM +0530, Sumit Garg wrote:
> > Add Schneider Electric HMIBSC board DTS. The HMIBSC board is an IIoT Edge
> > Box Core board based on the Qualcomm APQ8016E SoC.
> >
> > Support for Schneider Electric HMIBSC. Features:
> > - Qualcomm Snapdragon 410C SoC - APQ8016 (4xCortex A53, Adreno 306)
> > - 1GiB RAM
> > - 8GiB eMMC, SD slot
> > - WiFi and Bluetooth
> > - 2x Host, 1x Device USB port
> > - HDMI
> > - Discrete TPM2 chip over SPI
> > - USB ethernet adaptors (soldered)
> >
> > Co-developed-by: Jagdish Gediya <jagdish.gediya@xxxxxxxxxx>
> > Signed-off-by: Jagdish Gediya <jagdish.gediya@xxxxxxxxxx>
> > Reviewed-by: Caleb Connolly <caleb.connolly@xxxxxxxxxx>
> > Signed-off-by: Sumit Garg <sumit.garg@xxxxxxxxxx>
> > ---
> > arch/arm64/boot/dts/qcom/Makefile | 1 +
> > .../dts/qcom/apq8016-schneider-hmibsc.dts | 510 ++++++++++++++++++
> > 2 files changed, 511 insertions(+)
> > create mode 100644 arch/arm64/boot/dts/qcom/apq8016-schneider-hmibsc.dts
> >
> > diff --git a/arch/arm64/boot/dts/qcom/Makefile b/arch/arm64/boot/dts/qcom/Makefile
> > index 39889d5f8e12..ad55e52e950b 100644
> > --- a/arch/arm64/boot/dts/qcom/Makefile
> > +++ b/arch/arm64/boot/dts/qcom/Makefile
> > @@ -5,6 +5,7 @@ apq8016-sbc-usb-host-dtbs := apq8016-sbc.dtb apq8016-sbc-usb-host.dtbo
> >
> > dtb-$(CONFIG_ARCH_QCOM) += apq8016-sbc-usb-host.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += apq8016-sbc-d3-camera-mezzanine.dtb
> > +dtb-$(CONFIG_ARCH_QCOM) += apq8016-schneider-hmibsc.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += apq8039-t2.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += apq8094-sony-xperia-kitakami-karin_windy.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += apq8096-db820c.dtb
> > diff --git a/arch/arm64/boot/dts/qcom/apq8016-schneider-hmibsc.dts b/arch/arm64/boot/dts/qcom/apq8016-schneider-hmibsc.dts
> > new file mode 100644
> > index 000000000000..9c79a31a04db
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/qcom/apq8016-schneider-hmibsc.dts
> > @@ -0,0 +1,510 @@
> > [...]
> > +&blsp_uart1 {
> > + label = "UART0";
> > + status = "okay";
> > +};
> > +
> > +&blsp_uart2 {
> > + label = "UART1";
> > + status = "okay";
> > +};
> > +
> > +/* Enable CoreSight */
> > +&cti0 { status = "okay"; };
> > +&cti1 { status = "okay"; };
> > +&cti12 { status = "okay"; };
> > +&cti13 { status = "okay"; };
> > +&cti14 { status = "okay"; };
> > +&cti15 { status = "okay"; };
> > +&debug0 { status = "okay"; };
> > +&debug1 { status = "okay"; };
> > +&debug2 { status = "okay"; };
> > +&debug3 { status = "okay"; };
> > +&etf { status = "okay"; };
> > +&etm0 { status = "okay"; };
> > +&etm1 { status = "okay"; };
> > +&etm2 { status = "okay"; };
> > +&etm3 { status = "okay"; };
> > +&etr { status = "okay"; };
> > +&funnel0 { status = "okay"; };
> > +&funnel1 { status = "okay"; };
> > +&replicator { status = "okay"; };
> > +&stm { status = "okay"; };
> > +&tpiu { status = "okay"; };
>
> Nitpick: The &cti0 is in the correct alphabetically ordered place, but
> &replicator, &stm and &tpiu are not.
>
> I know you changed this based on the review comments but I personally
> think it was clearer having this separated as condensed block towards
> the end of the file (where it was before).
>
> The other option would be to put each element individually at the
> correctly ordered position in the file. However, having a single "Enable
> CoreSight" comment for the entire block would then not work anymore
> since all the lines would be interspersed throughout the file.
IMO, having it as a condensed block is a bit more clear such that
people are able to locate overrides easily given their function.
However, there aren't any guidelines for such block orders. So let me
wait to hear back from platform maintainers if they would like
anything to be changed here.
>
> > [...]
> > +&pm8916_codec {
> > + qcom,mbhc-vthreshold-low = <75 150 237 450 500>;
> > + qcom,mbhc-vthreshold-high = <75 150 237 450 500>;
> > + status = "okay";
> > +};
> > +
> > +&pm8916_gpios {
> > + gpio-line-names =
> > + "USB_HUB_RESET_N_PM",
> > + "USB_SW_SEL_PM",
> > + "NC",
> > + "NC";
> > +
> > + usb_hub_reset_pm: usb-hub-reset-pm-state {
> > + pins = "gpio1";
> > + function = PMIC_GPIO_FUNC_NORMAL;
> > +
> > + input-disable;
> > + output-high;
> > + };
> > +
> > + usb_hub_reset_pm_device: usb-hub-reset-pm-device-state {
> > + pins = "gpio1";
> > + function = PMIC_GPIO_FUNC_NORMAL;
> > +
> > + output-low;
> > + };
> > +
> > + usb_sw_sel_pm: usb-sw-sel-pm-state {
> > + pins = "gpio2";
> > + function = PMIC_GPIO_FUNC_NORMAL;
> > +
> > + power-source = <PM8916_GPIO_VPH>;
> > + input-disable;
> > + output-high;
> > + };
> > +
> > + usb_sw_sel_pm_device: usb-sw-sel-pm-device-state {
> > + pins = "gpio2";
> > + function = PMIC_GPIO_FUNC_NORMAL;
> > +
> > + power-source = <PM8916_GPIO_VPH>;
> > + input-disable;
> > + output-low;
> > + };
> > +};
> > +
> > +&pm8916_mpps {
> > + gpio-line-names =
> > + "NC",
> > + "WLAN_LED_CTRL",
> > + "BT_LED_CTRL",
> > + "NC";
> > +
> > + pm8916_mpps_leds: pm8916-mpps-state {
> > + pins = "mpp2", "mpp3";
> > + function = "digital";
> > +
> > + output-low;
> > + };
> > +};
> > +
> > +&pm8916_resin {
> > + interrupts = <0x0 0x8 1 IRQ_TYPE_EDGE_FALLING>;
>
> What is the goal of overriding the interrupt here? It looks like you are
> changing the interrupt type from IRQ_TYPE_EDGE_BOTH to FALLING. This
> sounds a bit like you want the driver to receive just button release
> events (or just press events, not sure about the polarity). I'm not sure
> if the driver will handle this correctly.
The use-case here is to just act upon button release events and the
driver handles this appropriately. Final use-case of the reset button:
- Short press and release leads to normal Linux reboot.
- Long press for more than 10 sec or so leads to a hard reset.
With IRQ_TYPE_EDGE_BOTH, that's not achievable because just a simple
press leads to Linux reboot.
>
> > + linux,code = <KEY_POWER>;
> > + status = "okay";
> > +};
> > +
> > +&pm8916_rpm_regulators {
> > + pm8916_l17: l17 {
> > + regulator-min-microvolt = <3300000>;
> > + regulator-max-microvolt = <3300000>;
> > + };
> > +};
> > +
> > +&sdhc_1 {
> > + status = "okay";
> > +};
> > +
> > +&sdhc_2 {
> > + pinctrl-0 = <&sdc2_default &sdc2_cd_default>;
> > + pinctrl-1 = <&sdc2_sleep &sdc2_cd_default>;
> > + pinctrl-names = "default", "sleep";
> > +
> > + cd-gpios = <&tlmm 38 GPIO_ACTIVE_LOW>;
> > + status = "okay";
> > +};
> > +
> > +&sound {
> > + pinctrl-0 = <&cdc_pdm_default &sec_mi2s_default>;
> > + pinctrl-1 = <&cdc_pdm_sleep &sec_mi2s_sleep>;
> > + pinctrl-names = "default", "sleep";
> > + model = "HMIBSC";
> > + audio-routing =
> > + "AMIC2", "MIC BIAS Internal2",
> > + "AMIC3", "MIC BIAS External1";
> > + status = "okay";
> > +
> > + quaternary-dai-link {
> > + link-name = "ADV7533";
> > + cpu {
> > + sound-dai = <&lpass MI2S_QUATERNARY>;
> > + };
> > + codec {
> > + sound-dai = <&adv_bridge 0>;
> > + };
> > + };
> > +
> > + primary-dai-link {
> > + link-name = "WCD";
> > + cpu {
> > + sound-dai = <&lpass MI2S_PRIMARY>;
> > + };
> > + codec {
> > + sound-dai = <&lpass_codec 0>, <&pm8916_codec 0>;
> > + };
> > + };
> > +
> > + tertiary-dai-link {
> > + link-name = "WCD-Capture";
> > + cpu {
> > + sound-dai = <&lpass MI2S_TERTIARY>;
> > + };
> > + codec {
> > + sound-dai = <&lpass_codec 1>, <&pm8916_codec 1>;
> > + };
> > + };
> > +};
> > +
> > +&tlmm {
> > + pinctrl-0 = <&uart1_mux0_rs232_high &uart1_mux1_rs232_low>;
> > + pinctrl-names = "default";
> > +
> > + adv7533_int_active: adv533-int-active-state {
> > + pins = "gpio31";
> > + function = "gpio";
> > +
> > + drive-strength = <16>;
> > + bias-disable;
> > + };
> > +
> > + adv7533_int_suspend: adv7533-int-suspend-state {
> > + pins = "gpio31";
> > + function = "gpio";
> > +
> > + drive-strength = <2>;
> > + bias-disable;
> > + };
> > +
> > + adv7533_switch_active: adv7533-switch-active-state {
> > + pins = "gpio32";
> > + function = "gpio";
> > +
> > + drive-strength = <16>;
> > + bias-disable;
> > + };
> > +
> > + adv7533_switch_suspend: adv7533-switch-suspend-state {
> > + pins = "gpio32";
> > + function = "gpio";
> > +
> > + drive-strength = <2>;
> > + bias-disable;
> > + };
> > +
> > + msm_key_volp_n_default: msm-key-volp-n-default-state {
> > + pins = "gpio107";
> > + function = "gpio";
> > +
> > + drive-strength = <8>;
> > + bias-pull-up;
> > + };
> > +
> > + sdc2_cd_default: sdc2-cd-default-state {
> > + pins = "gpio38";
> > + function = "gpio";
> > + drive-strength = <2>;
> > + bias-disable;
> > + };
>
> Nitpick: It would look a bit cleaner to have the empty lines consistent
> in all pinctrl nodes, i.e. either always having an empty line between
> function and drive-strength or never. I think Konrad prefers the more
> compact version without empty line (sadly I'm not sure if this is
> clearly documented anywhere). Same for &pm8916_gpios and mpps.
>
Sure I can remove the empty lines to be consistent with msm8916.dtsi.
> > +
> > + /*
> > + * UART1 being the debug console supports various modes of
> > + * operation (RS-232/485/422) controlled via GPIOs configured
> > + * mux as follows:
> > + *
> > + * gpio100 gpio99 UART mode
> > + * 0 0 loopback
> > + * 0 1 RS-232
> > + * 1 0 RS-485
> > + * 1 1 RS-422
> > + *
> > + * The default mode configured here is RS-232 mode.
> > + */
>
> :D
>
> Thanks a lot for making this clear using the table. And also for all the
> other cleanup changes!
Thanks for your review.
-Sumit
>
> Stephan
