From: Karel Balej
IST3032C is a touchscreen chip used for instance in the
samsung,coreprimevelte smartphone, with which this was tested. Add the
chip specific information to the driver.
Reviewed-by: Markuss Broks
Signed-off-by: Karel Balej
---
Notes:
v4:
* Change the WHOAMI
From: Markuss Broks
Imagis IST3038B is another variant of Imagis IST3038 IC, which has
a different register interface from IST3038C (possibly firmware defined).
This should also work for IST3044B (though untested), however other
variants using this interface/protocol(IST3026, IST3032, IST3026B,
From: Karel Balej
IST3032C is a touchscreen IC which seems mostly compatible with IST3038C
except that it reports a different chip ID value.
Signed-off-by: Karel Balej
---
Notes:
v4:
* Reword commit description to mention how this IC differs from the
already supported.
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt :
On Thu, 30 Nov 2023 13:15:27 +0100 you wrote:
> From: Björn Töpel
>
> NB! Song told me that he would not have the time work on this series,
> so I picked it up.
>
> This series includes a three ftrace improvements
From: Karel Balej
Hello,
this patch series generalizes the Imagis touchscreen driver to support
other Imagis chips, namely IST3038B and IST3032C, which use a slightly
different protocol.
It also adds necessary information to the driver so that the IST3032C
touchscreen can be used with it. The
From: Markuss Broks
As specified in downstream IST3038B driver and proved by testing,
the correct maximum reported value of touch area is 16.
Signed-off-by: Markuss Broks
Signed-off-by: Karel Balej
---
drivers/input/touchscreen/imagis.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Markuss Broks
Imagis IST3038B is a variant (firmware?) of Imagis IST3038 IC
differing from IST3038C in its register interface. Add the
compatible for it to the IST3038C bindings.
Signed-off-by: Markuss Broks
Acked-by: Conor Dooley
[bal...@matfyz.cz: elaborate chip differences in the
IST3032C (and possibly some other models) has touch keys. Document this.
Signed-off-by: Duje Mihanović
---
.../bindings/input/touchscreen/imagis,ist3038c.yaml | 11 +++
1 file changed, 11 insertions(+)
diff --git
IST3032C (and possibly some other models) has touch keys. Add support
for them to the imagis driver.
Signed-off-by: Duje Mihanović
---
drivers/input/touchscreen/imagis.c | 25 -
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git
Instead of manually extracting certain bits from registers with binary
ANDs and shifts, the FIELD_GET macro can be used. With this in mind, the
*_SHIFT macros can be dropped.
Signed-off-by: Duje Mihanović
---
drivers/input/touchscreen/imagis.c | 17 ++---
1 file changed, 6
: 553f2a83ae97246be401ca9b313063f5fa879f12
change-id: 20240120-b4-imagis-keys-a0a9f2b31740
Best regards,
--
Duje Mihanović
On Sat, 20 Jan 2024 08:47:13 -0500
Steven Rostedt wrote:
> > I would also consider reducing code complexity as a worthwhile metric
> > in addition to speed. It makes it easier to extend in the future,
> > easier to understand for reviewers, and subtle bugs are less likely
> > to creep in.
>
>
On Fri, Jan 19, 2024 at 06:37:26AM -0800, Paul E. McKenney wrote:
> On Thu, Jan 18, 2024 at 02:18:42AM +, Chen Zhongjin wrote:
> > There is a deadlock scenario in kprobe_optimizer():
> >
> > pid A pid B pid C
> > kprobe_optimizer()
On Fri, 19 Jan 2024 20:49:36 -0500
Mathieu Desnoyers wrote:
> >> Let's say we have the following ktime_get() values (monotonic timestamp
> >> value) for
> >> a sequence of events:
> >>
> >> Timestamp (Hex)Encoding in the
> >> trace
> >>
> >> Packet
14 matches
Mail list logo
