From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Hyung Jin Jung <realbright@lgcns.com>
Cc: "airlied@linux.ie" <airlied@linux.ie>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: drm/atmel-hlcdc: connector type & fbdev mode settings
Date: Wed, 31 Aug 2016 09:34:29 +0200 [thread overview]
Message-ID: <20160831093429.164e5ddc@bbrezillon> (raw)
In-Reply-To: <61FA15C5AEE1ED4E827ADEB50820C1443EB181948F@MAIL03.corp.lgcns.com>
On Wed, 31 Aug 2016 11:29:53 +0900
Hyung Jin Jung <realbright@lgcns.com> wrote:
> According to Atmel's guideline... http://www.at91.com/linux4sam/bin/view/Linux4SAM/UsingAtmelDRMDriver
>
> the "fbdev emulation mode" could be set from kernel command line (LVDS-1:...)
> however, driver register it as DRM_MODE_CONNECTOR_Unknown connector.
Just adapt the command line with Unknown-1:...
>
> Actually we using sama5d3x with LVDS cable so that below patch would be correct.
No it wouldn't. The sama5 SoC is providing a raw RGB interface, so if
you really have an LVDS interface on your board this means you have a
bridge in the middle. This bridge should be represented in the DT, and
attached to a driver in the kernel.
> But I don't know the other case such as HDMI, composite...
>
> Do we need to consider using DT or auto-detection??
>
> Signed-off-by: HyungJin Jung <realbright@lgcns.com>
> ---
> drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c b/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c
> index 6119b50..da97efe
> --- a/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c
> +++ b/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c
> @@ -208,7 +208,7 @@ static int atmel_hlcdc_attach_endpoint(struct drm_device *dev,
> &atmel_hlcdc_panel_connector_helper_funcs);
> ret = drm_connector_init(dev, &output->connector,
> &atmel_hlcdc_panel_connector_funcs,
> - DRM_MODE_CONNECTOR_Unknown);
> + DRM_MODE_CONNECTOR_LVDS);
> if (ret)
> goto err_encoder_cleanup;
>
prev parent reply other threads:[~2016-08-31 7:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 2:29 Hyung Jin Jung
2016-08-31 7:34 ` Boris Brezillon [this message]
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=20160831093429.164e5ddc@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=realbright@lgcns.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
all inboxes | Powered by JetHome®