linux-kernel - Re: [PATCH] Input: add bu21029 touch driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <bf2aff8ab685473c836012bbed96c693@de.bosch.com>
Date:   Tue, 27 Mar 2018 06:52:31 +0000
From:   "Jonas Mark (BT-FIR/ENG1)" <Mark.Jonas@...bosch.com>
To:     Rob Herring <robh@...nel.org>
CC:     Dmitry Torokhov <dmitry.torokhov@...il.com>,
        Mark Rutland <mark.rutland@....com>,
        "linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "hs@...x.de" <hs@...x.de>,
        "ZHU Yi (BT-FIR/ENG1-Zhu)" <Yi.Zhu5@...bosch.com>,
        "Jonas Mark (BT-FIR/ENG1)" <Mark.Jonas@...bosch.com>
Subject: Re: [PATCH] Input: add bu21029 touch driver

Hello Rob,

> > +* Rohm BU21029 Touch Screen Controller
> > +
> > +Required properties:
> > + - compatible              : must be "rohm,bu21029"
> > + - reg                     : i2c device address of the chip
> 
> What the valid value(s)?

The chip itself can be wired to 0x40 or 0x41. The driver can work with
any valid I2C address.

Is this what you are looking for?

- reg                     : i2c device address of the chip (0x40 or 0x41)

> > + - interrupt-parent        : the phandle for the gpio controller
> > + - interrupts              : (gpio) interrupt to which the chip is connected
> > + - reset-gpios             : gpio pin to reset the chip
> 
> Active high or low?

The chip itself needs an active low reset. But depending on whether
there is an inverter between the touch screen controller and the CPU or
not, the CPU's GPIO might need to be active high or active low. This
shall be configured by the polarity given in the device tree. The
driver uses this information to drive the reset appropriately.

Are you looking for documenting the required polarity of the touch
controller itself?

- reset-gpios             : gpio pin to reset the chip (active low)

> > +Example:
> > +
> > +	&i2c1 {
> > +		/* ... */
> > +
> > +		bu21029: bu21029@40 {
> > +			compatible = "rohm,bu21029";
> > +			reg = <0x40>;
> > +			interrupt-parent = <&gpio1>;
> > +			interrupts = <4 IRQ_TYPE_EDGE_FALLING>;
> > +			reset-gpios = <&gpio6 16 GPIO_ACTIVE_LOW>;
> > +			rohm,x-plate-ohms = <600>;
> > +			touchscreen-max-pressure = <4095>;
> > +		};
> > +
> > +		/* ... */
> > +	};

Greetings,
Mark Jonas

Building Technologies, Panel Software Fire (BT-FIR/ENG1) 
Bosch Sicherheitssysteme GmbH | Postfach 11 11 | 85626 Grasbrunn | GERMANY | www.boschsecurity.com

Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart HRB 23118 
Aufsichtsratsvorsitzender: Stefan Hartung; Geschäftsführung: Gert van Iperen, Andreas Bartz, Thomas Quante, Bernhard Schuster