[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190711145045.GI14859@sirena.co.uk>
Date: Thu, 11 Jul 2019 15:50:45 +0100
From: Mark Brown <broonie@...nel.org>
To: Andrzej Hajda <a.hajda@...sung.com>
Cc: Jeffrey Hugo <jeffrey.l.hugo@...il.com>,
Laurent.pinchart@...asonboard.com, airlied@...ux.ie,
daniel@...ll.ch, robdclark@...il.com, bjorn.andersson@...aro.org,
dri-devel@...ts.freedesktop.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] regmap: Add DSI bus support
On Thu, Jul 11, 2019 at 03:11:56PM +0200, Andrzej Hajda wrote:
> 1. DSI protocol defines actually more than 30 types of transactions[1],
> but this patchset implements only few of them (dsi generic write/read
> family). Is it possible to implement multiple types of transactions in
> regmap?
You can, there's a couple of different ways depending on how
exactly things are done.
> 3. DSI devices are no MFDs so regmap abstraction has no big value added
> (correct me, if there are other significant benefits).
There's a few extra bits even if you're not using the marshalling
code to get things onto the bus - the main ones are the register
cache support (which people often use for simpler suspend/resume
support) and the debug and trace facilities (things like
tracepoints and debugfs for dumping the register map). There's
no real connection to MFDs, I'd say the majority of users are not
MFDs.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists