From: Brian Norris <briannorris@chromium.org>
To: Lin Huang <hl@rock-chips.com>
Cc: emil.l.velikov@gmail.com, thierry.reding@gmail.com,
robh+dt@kernel.org, zyw@rock-chips.com, seanpaul@chromium.org,
airlied@linux.ie, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, nickey.yang@rock-chips.com,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [RESEND PATCH v3 1/3] drm/panel: refactor INNOLUX P079ZCA panel driver
Date: Wed, 13 Dec 2017 12:46:29 -0800 [thread overview]
Message-ID: <20171213204628.GA237314@google.com> (raw)
In-Reply-To: <1512371870-15350-1-git-send-email-hl@rock-chips.com>
Hi HL,
On Mon, Dec 04, 2017 at 03:17:48PM +0800, Lin Huang wrote:
> Refactor Innolux P079ZCA panel driver, let it support
> multi panel.
>
> Signed-off-by: Lin Huang <hl@rock-chips.com>
> ---
> Changes in v2:
> - Change regulator property name to meet the panel datasheet
> Changes in v3:
> - this patch only refactor P079ZCA panel to support multi panel, support P097PFG panel in another patch
>
> drivers/gpu/drm/panel/panel-innolux-p079zca.c | 147 ++++++++++++++++++--------
> 1 file changed, 105 insertions(+), 42 deletions(-)
>
> diff --git a/drivers/gpu/drm/panel/panel-innolux-p079zca.c b/drivers/gpu/drm/panel/panel-innolux-p079zca.c
> index 6ba9344..1597744 100644
> --- a/drivers/gpu/drm/panel/panel-innolux-p079zca.c
> +++ b/drivers/gpu/drm/panel/panel-innolux-p079zca.c
...
> @@ -134,12 +162,13 @@ static int innolux_panel_prepare(struct drm_panel *panel)
> return 0;
>
> poweroff:
> - regulator_err = regulator_disable(innolux->supply);
I think 'regulator_err' is unused after this patch. Please remove it.
> - if (regulator_err)
> - DRM_DEV_ERROR(panel->dev, "failed to disable regulator: %d\n",
> - regulator_err);
> -
> gpiod_set_value_cansleep(innolux->enable_gpio, 0);
> + regulator_disable(innolux->avee);
> +disable_avdd:
> + regulator_disable(innolux->avdd);
> +disable_vddi:
> + regulator_disable(innolux->vddi);
> +
> return err;
> }
>
...
> @@ -209,20 +256,36 @@ static const struct drm_panel_funcs innolux_panel_funcs = {
> };
>
> static const struct of_device_id innolux_of_match[] = {
> - { .compatible = "innolux,p079zca", },
> - { }
You're deleting this terminator. Please don't.
> + { .compatible = "innolux,p079zca",
> + .data = &innolux_p079zca_panel_desc
> + },
> };
> MODULE_DEVICE_TABLE(of, innolux_of_match);
>
...
Brian
next prev parent reply other threads:[~2017-12-13 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 7:17 [RESEND PATCH v3 1/3] drm/panel: refactor INNOLUX P079ZCA panel driver Lin Huang
2017-12-04 7:17 ` [RESEND PATCH v3 2/3] drm/panel: support Innolux P097PFG panel Lin Huang
2017-12-04 7:17 ` [RESEND PATCH v3 3/3] dt-bindings: Add INNOLUX P097PFG panel bindings Lin Huang
2017-12-13 20:46 ` Brian Norris [this message]
2018-03-12 9:21 ` [RESEND PATCH v3 1/3] drm/panel: refactor INNOLUX P079ZCA panel driver Thierry Reding
2018-03-13 3:41 ` hl
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=20171213204628.GA237314@google.com \
--to=briannorris@chromium.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=hl@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nickey.yang@rock-chips.com \
--cc=robh+dt@kernel.org \
--cc=seanpaul@chromium.org \
--cc=thierry.reding@gmail.com \
--cc=zyw@rock-chips.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: 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