From: Mark Brown <broonie@kernel.org>
To: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
Cc: 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: Sat, 6 Jul 2019 02:06:04 +0100 [thread overview]
Message-ID: <20190706010604.GG20625@sirena.org.uk> (raw)
In-Reply-To: <20190703214512.41319-1-jeffrey.l.hugo@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1184 bytes --]
On Wed, Jul 03, 2019 at 02:45:12PM -0700, Jeffrey Hugo wrote:
> Add basic support with a simple implementation that utilizes the generic
> read/write commands to allow device registers to be configured.
This looks good to me but I really don't know anything about DSI,
I'd appreciate some review from other people who do. I take it
there's some spec thing in DSI that says registers and bytes must
both be 8 bit?
A couple of minor comments, no need to resend just for these:
> + payload[0] = (char)reg;
> + payload[1] = (char)val;
Do you need the casts?
> + ret = mipi_dsi_generic_write(dsi, payload, 2);
> + return ret < 0 ? ret : 0;
Please just write an if statement, it helps with legibility.
> +struct regmap *__regmap_init_dsi(struct mipi_dsi_device *dsi,
> + const struct regmap_config *config,
> + struct lock_class_key *lock_key,
> + const char *lock_name)
> +{
> + return __regmap_init(&dsi->dev, &dsi_bus, &dsi->dev, config,
> + lock_key, lock_name);
> +}
> +EXPORT_SYMBOL_GPL(__regmap_init_dsi);
Perhaps validate that the config is OK (mainly the register/value
sizes)? Though I'm not sure it's worth it so perhaps not - up to
you.
[-- 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-06 1:06 UTC|newest]
Thread overview: 13+ 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:45 ` [PATCH 1/2] regmap: Add DSI bus support Jeffrey Hugo
2019-07-06 1:06 ` Mark Brown [this message]
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: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-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=20190706010604.GG20625@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--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 \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox