From: Tony Lindgren <tony@atomide.com>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: Enric Balletbo i Serra <eballetbo@gmail.com>,
linux-omap@vger.kernel.org,
Enric Balletbo i Serra <eballetbo@iseebcn.com>
Subject: Re: [PATCH 1/1] ARM: OMAP3: igep0020: Set DSS pins in correct mux mode.
Date: Thu, 4 Jul 2013 04:47:15 -0700 [thread overview]
Message-ID: <20130704114714.GB5523@atomide.com> (raw)
In-Reply-To: <1371659083-14536-1-git-send-email-javier.martinez@collabora.co.uk>
* Javier Martinez Canillas <javier.martinez@collabora.co.uk> [130619 09:31]:
> From: Enric Balletbo i Serra <eballetbo@iseebcn.com>
>
> Platform code used to depend on bootloadres for correctly setting the mux
> pin modes. But bootloaders should only set the minimum required mux pins.
> So, DSS mux pins are not set in U-Boot anymore and video display is broken
> on IGEPv2 when booting with newer U-Boot versions.
>
> Setup the DSS pin muxes to enable display functionality.
>
> Signed-off-by: Enric Balletbo i Serra <eballetbo@iseebcn.com>
> Reviewed-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> ---
>
> Tony,
>
> Can you please take this until we have finished the OMAP3 migration to DT?
>
> I think it falls under the critical fix category that you were talking about.
Thanks, yes I'll apply it into omap-for-v3.11/fixes. Other than DSS and the
pending pinctrl-single patches, we have off-idle working for omap3 with DT,
so there really are no reasons to not make omap3 DT only very soon.
Regards,
Tony
prev parent reply other threads:[~2013-07-04 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 16:24 [PATCH 1/1] ARM: OMAP3: igep0020: Set DSS pins in correct mux mode Javier Martinez Canillas
2013-07-04 11:47 ` Tony Lindgren [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=20130704114714.GB5523@atomide.com \
--to=tony@atomide.com \
--cc=eballetbo@gmail.com \
--cc=eballetbo@iseebcn.com \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-omap@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 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.