From: Sam Ravnborg <sam@ravnborg.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Claudiu Beznea <claudiu.beznea@microchip.com>,
boris.brezillon@bootlin.com, airlied@linux.ie,
nicolas.ferre@microchip.com, alexandre.belloni@bootlin.com,
peda@axentia.se, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] fixes for atmel-hlcdc
Date: Thu, 2 Jan 2020 17:21:34 +0100 [thread overview]
Message-ID: <20200102162134.GA13454@ravnborg.org> (raw)
In-Reply-To: <20200102160534.GJ22390@dell>
Hi Lee.
> > > ("drm/atmel-hlcdc: allow selecting a higher pixel-clock than requested")
> > >
> > > Claudiu Beznea (5):
> > > drm: atmel-hlcdc: use double rate for pixel clock only if supported
> > > drm: atmel-hlcdc: enable clock before configuring timing engine
> >
> > > mfd: atmel-hlcdc: add struct device member to struct
> > > atmel_hlcdc_regmap
> > > mfd: atmel-hlcdc: return in case of error
> >
> > Would it be OK to apply the to drm-misc-next, or shal they go in via
> > your mfd tree?
>
> How are they related to the other patches? Do they have build-time
> dependencies on any of the other patches, or vice versa?
No build time dependencies.
But from the description of "atmel-hlcdc: return in case of error":
"
For HLCDC timing engine configurations bit ATMEL_HLCDC_SIP of
ATMEL_HLCDC_SR needs to be polled before applying new config.
"
I get that changing timing for the HLCDC may fail if these
patches are not applied.
So it is only to have updated hlcdc support in drm-misc-next
for further testing.
Sam
next prev parent reply other threads:[~2020-01-02 16:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 12:28 [PATCH v3 0/6] fixes for atmel-hlcdc Claudiu Beznea
2019-12-18 12:28 ` [PATCH v3 1/6] drm: atmel-hlcdc: use double rate for pixel clock only if supported Claudiu Beznea
2019-12-18 12:28 ` [PATCH v3 2/6] drm: atmel-hlcdc: enable clock before configuring timing engine Claudiu Beznea
2019-12-18 12:28 ` [PATCH v3 3/6] mfd: atmel-hlcdc: add struct device member to struct atmel_hlcdc_regmap Claudiu Beznea
2019-12-18 12:28 ` [PATCH v3 4/6] mfd: atmel-hlcdc: return in case of error Claudiu Beznea
2020-01-07 10:18 ` Lee Jones
2019-12-18 12:28 ` [PATCH v3 5/6] drm: atmel-hlcdc: prefer a lower pixel-clock than requested Claudiu Beznea
2020-01-02 9:08 ` Sam Ravnborg
2020-01-04 17:12 ` Sam Ravnborg
2020-01-06 9:25 ` Claudiu.Beznea
2020-01-06 19:02 ` Sam Ravnborg
2020-01-06 9:24 ` Claudiu.Beznea
2020-01-07 9:19 ` Peter Rosin
2019-12-18 12:28 ` [PATCH v3 6/6] Revert "drm: atmel-hlcdc: enable sys_clk during initalization." Claudiu Beznea
2020-01-02 9:05 ` [PATCH v3 0/6] fixes for atmel-hlcdc Sam Ravnborg
2020-01-02 16:05 ` Lee Jones
2020-01-02 16:21 ` Sam Ravnborg [this message]
2020-01-06 19:37 ` Sam Ravnborg
2020-01-07 10:17 ` [GIT PULL] Immutable branch between MFD and DRM due for the v5.6 merge window Lee Jones
2020-01-07 18:21 ` Sam Ravnborg
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=20200102162134.GA13454@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=alexandre.belloni@bootlin.com \
--cc=boris.brezillon@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=peda@axentia.se \
/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;
as well as URLs for NNTP newsgroup(s).