[PATCH v3 10/10] ARM: dts: ti: omap: samsung-espresso10: Add initial support for Galaxy Tab 2 10.1
Andreas Kemnade
andreas at kemnade.info
Tue Nov 12 10:48:18 UTC 2024
Am Fri, 8 Nov 2024 20:04:39 +0000
schrieb Mithil Bavishi <bavishimithil at gmail.com>:
> Create a device tree for the 10 inch variants (P5100, P5110, P5113)
>
> Signed-off-by: Mithil Bavishi <bavishimithil at gmail.com>
> ---
> .../dts/ti/omap/omap4-samsung-espresso10.dts | 102 ++++++++++++++++++
> 1 file changed, 102 insertions(+)
> create mode 100644 arch/arm/boot/dts/ti/omap/omap4-samsung-espresso10.dts
>
> diff --git a/arch/arm/boot/dts/ti/omap/omap4-samsung-espresso10.dts b/arch/arm/boot/dts/ti/omap/omap4-samsung-espresso10.dts
> new file mode 100644
> index 000000000..70bbef468
> --- /dev/null
> +++ b/arch/arm/boot/dts/ti/omap/omap4-samsung-espresso10.dts
> @@ -0,0 +1,102 @@
> +// SPDX-License-Identifier: (GPL-2.0 OR MIT)
> +/dts-v1/;
> +
> +#include "omap4-samsung-espresso-common.dtsi"
> +#include <dt-bindings/power/summit,smb347-charger.h>
> +/ {
> + model = "Samsung Galaxy Tab 2 (10 inch)";
> + compatible = "samsung,espresso10", "ti,omap4430", "ti,omap4";
> +
> + i2c-gpio-5 {
> + smb347: charger at 6 {
> + compatible = "summit,smb347";
> + reg = <0x6>; // 0x0C >> 1
> + interrupt-parent = <&gpio2>;
> + interrupts = <0 IRQ_TYPE_EDGE_BOTH>;
> +
> + summit,enable-usb-charging;
> + summit,enable-charge-control = <SMB3XX_CHG_ENABLE_SW>;
> + summit,chip-temperature-threshold-celsius = <120>;
> + summit,usb-current-limit-microamp = <1800000>;
> + };
> + };
> +
> + backlight: backlight {
> + compatible = "pwm-backlight";
> + pinctrl-names = "default";
> + pinctrl-0 = <&backlight_pins>;
> + pwms = <&pwm10 0 1600 0>;
> + power-supply = <®_lcd>;
> + enable-gpios = <&gpio3 31 GPIO_ACTIVE_HIGH>;
> + brightness-levels = <0 4 8 16 32 64 128 255>;
> + default-brightness-level = <7>;
> + };
> +
> + panel {
> + compatible = "samsung,ltn101al03", "panel-lvds";
> + power-supply = <®_lcd>;
> + width-mm = <223>;
> + height-mm = <125>;
> + data-mapping = "vesa-24";
> + backlight = <&backlight>;
> +
> + panel-timing {
> + clock-frequency = <69818000>;
> +
> + hback-porch = <64>;
> + hactive = <1280>;
> + hfront-porch = <16>;
> + hsync-len = <48>;
> +
> + vback-porch = <11>;
> + vactive = <800>;
> + vfront-porch = <16>;
> + vsync-len = <3>;
> +
> + hsync-active = <0>;
> + vsync-active = <0>;
> + de-active = <1>;
> + pixelclk-active = <1>;
> + };
> +
> + port {
> + panel_in: endpoint {
> + remote-endpoint = <&bridge_out>;
> + };
> + };
> + };
> +};
> +
> +&i2c3 {
> + touchscreen: synaptics-rmi4-i2c at 20 {
touchscreen at 20
> + compatible = "syna,rmi4-i2c";
> + reg = <0x20>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + interrupt-parent = <&gpio2>;
> + interrupts = <14 IRQ_TYPE_EDGE_FALLING>;
> +
> + pinctrl-names = "default";
> + pinctrl-0 = <&touch_pins>;
> +
> + avdd-supply = <®_touch_ldo_en>;
not known in schema
> + vdd-supply = <&ldo6>;
> +
> + syna,reset-delay-ms = <200>;
> + syna,startup-delay-ms = <200>;
> +
> + touchscreen-size-x = <1279>;
Documentation/devicetree/bindings/input/touchscreen/touchscreen.yaml:
horizontal resolution of touchscreen (maximum x coordinate reported + 1)
So this touchscreen reports max 1278?
> + touchscreen-size-y = <799>;
same question.
And these things belong below rm4-f11 according to
Documentation/devicetree/bindings/input/syna,rmi4.yaml
Regards,
Andreas
More information about the dri-devel
mailing list