From: Mark Brown <broonie@kernel.org> To: Andrzej Hajda <a.hajda@samsung.com> Cc: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>, Laurent.pinchart@ideasonboard.com, airlied@linux.ie, daniel@ffwll.ch, robdclark@gmail.com, bjorn.andersson@linaro.org, dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] regmap: Add DSI bus support Date: Thu, 11 Jul 2019 15:50:45 +0100 [thread overview] Message-ID: <20190711145045.GI14859@sirena.co.uk> (raw) In-Reply-To: <64ca3a74-374f-d4f3-bee6-a607cc5c0fc5@samsung.com> [-- Attachment #1: Type: text/plain, Size: 902 bytes --] 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. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org> To: Andrzej Hajda <a.hajda@samsung.com> Cc: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>, airlied@linux.ie, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, bjorn.andersson@linaro.org, Laurent.pinchart@ideasonboard.com Subject: Re: [PATCH 1/2] regmap: Add DSI bus support Date: Thu, 11 Jul 2019 15:50:45 +0100 [thread overview] Message-ID: <20190711145045.GI14859@sirena.co.uk> (raw) In-Reply-To: <64ca3a74-374f-d4f3-bee6-a607cc5c0fc5@samsung.com> [-- Attachment #1.1: Type: text/plain, Size: 902 bytes --] 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. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --] [-- Attachment #2: Type: text/plain, Size: 159 bytes --] _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-07-11 14:50 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-03 21:43 [PATCH 0/2] ti-sn65dsi86 DSI configuration support Jeffrey Hugo 2019-07-03 21:43 ` Jeffrey Hugo 2019-07-03 21:45 ` [PATCH 1/2] regmap: Add DSI bus support Jeffrey Hugo 2019-07-06 1:06 ` Mark Brown 2019-07-06 1:06 ` Mark Brown 2019-07-10 18:08 ` Jeffrey Hugo 2019-07-11 14:41 ` Mark Brown 2019-07-11 13:11 ` Andrzej Hajda 2019-07-11 13:11 ` Andrzej Hajda 2019-07-11 13:56 ` Rob Clark 2019-07-12 13:01 ` Andrzej Hajda 2019-07-12 14:22 ` Jeffrey Hugo 2019-07-13 0:49 ` Rob Clark 2019-07-13 0:49 ` Rob Clark 2019-07-11 14:50 ` Mark Brown [this message] 2019-07-11 14:50 ` Mark Brown 2019-07-15 8:38 ` Andrzej Hajda 2019-07-03 21:45 ` [PATCH 2/2] drm/bridge: ti-sn65dsi86: Add support to be a DSI device Jeffrey Hugo
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190711145045.GI14859@sirena.co.uk \ --to=broonie@kernel.org \ --cc=Laurent.pinchart@ideasonboard.com \ --cc=a.hajda@samsung.com \ --cc=airlied@linux.ie \ --cc=bjorn.andersson@linaro.org \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=jeffrey.l.hugo@gmail.com \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=robdclark@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.