From: Lee Jones <lee.jones@linaro.org>
To: Sam Ravnborg <sam@ravnborg.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 16:05:34 +0000 [thread overview]
Message-ID: <20200102160534.GJ22390@dell> (raw)
In-Reply-To: <20200102090554.GB29446@ravnborg.org>
On Thu, 02 Jan 2020, Sam Ravnborg wrote:
> Hi Lee.
>
> How do de handle the two mfd related patches?
>
> > I have few fixes for atmel-hlcdc driver in this series as well
> > as two reverts.
> > Revert "drm: atmel-hlcdc: enable sys_clk during initalization." is
> > due to the fix in in patch 2/5.
> >
> > Thank you,
> > Claudiu Beznea
> >
> > Changes in v3:
> > - changes dev_err() message in patch 4/6
> > - collect Acked-by tags
> >
> > Changes in v2:
> > - introduce patch 3/6
> > - use dev_err() inpatch 4/6
> > - introduce patch 5/6 instead of reverting commit f6f7ad323461
> > ("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?
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: alexandre.belloni@bootlin.com, airlied@linux.ie,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
peda@axentia.se, boris.brezillon@bootlin.com,
Claudiu Beznea <claudiu.beznea@microchip.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/6] fixes for atmel-hlcdc
Date: Thu, 2 Jan 2020 16:05:34 +0000 [thread overview]
Message-ID: <20200102160534.GJ22390@dell> (raw)
In-Reply-To: <20200102090554.GB29446@ravnborg.org>
On Thu, 02 Jan 2020, Sam Ravnborg wrote:
> Hi Lee.
>
> How do de handle the two mfd related patches?
>
> > I have few fixes for atmel-hlcdc driver in this series as well
> > as two reverts.
> > Revert "drm: atmel-hlcdc: enable sys_clk during initalization." is
> > due to the fix in in patch 2/5.
> >
> > Thank you,
> > Claudiu Beznea
> >
> > Changes in v3:
> > - changes dev_err() message in patch 4/6
> > - collect Acked-by tags
> >
> > Changes in v2:
> > - introduce patch 3/6
> > - use dev_err() inpatch 4/6
> > - introduce patch 5/6 instead of reverting commit f6f7ad323461
> > ("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?
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: alexandre.belloni@bootlin.com, airlied@linux.ie,
linux-kernel@vger.kernel.org, nicolas.ferre@microchip.com,
dri-devel@lists.freedesktop.org, peda@axentia.se,
boris.brezillon@bootlin.com,
Claudiu Beznea <claudiu.beznea@microchip.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/6] fixes for atmel-hlcdc
Date: Thu, 2 Jan 2020 16:05:34 +0000 [thread overview]
Message-ID: <20200102160534.GJ22390@dell> (raw)
In-Reply-To: <20200102090554.GB29446@ravnborg.org>
On Thu, 02 Jan 2020, Sam Ravnborg wrote:
> Hi Lee.
>
> How do de handle the two mfd related patches?
>
> > I have few fixes for atmel-hlcdc driver in this series as well
> > as two reverts.
> > Revert "drm: atmel-hlcdc: enable sys_clk during initalization." is
> > due to the fix in in patch 2/5.
> >
> > Thank you,
> > Claudiu Beznea
> >
> > Changes in v3:
> > - changes dev_err() message in patch 4/6
> > - collect Acked-by tags
> >
> > Changes in v2:
> > - introduce patch 3/6
> > - use dev_err() inpatch 4/6
> > - introduce patch 5/6 instead of reverting commit f6f7ad323461
> > ("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?
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-01-02 16:05 UTC|newest]
Thread overview: 60+ 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 ` Claudiu Beznea
2019-12-18 12:28 ` 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 ` Claudiu Beznea
2019-12-18 12:28 ` 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 ` Claudiu Beznea
2019-12-18 12:28 ` 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 ` Claudiu Beznea
2019-12-18 12:28 ` Claudiu Beznea
2019-12-18 12:28 ` [PATCH v3 4/6] mfd: atmel-hlcdc: return in case of error Claudiu Beznea
2019-12-18 12:28 ` Claudiu Beznea
2019-12-18 12:28 ` Claudiu Beznea
2020-01-07 10:18 ` Lee Jones
2020-01-07 10:18 ` Lee Jones
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
2019-12-18 12:28 ` Claudiu Beznea
2019-12-18 12:28 ` Claudiu Beznea
2020-01-02 9:08 ` Sam Ravnborg
2020-01-02 9:08 ` Sam Ravnborg
2020-01-02 9:08 ` Sam Ravnborg
2020-01-04 17:12 ` Sam Ravnborg
2020-01-04 17:12 ` Sam Ravnborg
2020-01-04 17:12 ` Sam Ravnborg
2020-01-06 9:25 ` Claudiu.Beznea
2020-01-06 9:25 ` Claudiu.Beznea
2020-01-06 9:25 ` Claudiu.Beznea
2020-01-06 19:02 ` Sam Ravnborg
2020-01-06 19:02 ` Sam Ravnborg
2020-01-06 19:02 ` Sam Ravnborg
2020-01-06 9:24 ` Claudiu.Beznea
2020-01-06 9:24 ` Claudiu.Beznea
2020-01-06 9:24 ` Claudiu.Beznea
2020-01-07 9:19 ` Peter Rosin
2020-01-07 9:19 ` Peter Rosin
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
2019-12-18 12:28 ` Claudiu Beznea
2019-12-18 12:28 ` Claudiu Beznea
2020-01-02 9:05 ` [PATCH v3 0/6] fixes for atmel-hlcdc Sam Ravnborg
2020-01-02 9:05 ` Sam Ravnborg
2020-01-02 9:05 ` Sam Ravnborg
2020-01-02 16:05 ` Lee Jones [this message]
2020-01-02 16:05 ` Lee Jones
2020-01-02 16:05 ` Lee Jones
2020-01-02 16:21 ` Sam Ravnborg
2020-01-02 16:21 ` Sam Ravnborg
2020-01-02 16:21 ` Sam Ravnborg
2020-01-06 19:37 ` Sam Ravnborg
2020-01-06 19:37 ` Sam Ravnborg
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 10:17 ` Lee Jones
2020-01-07 10:17 ` Lee Jones
2020-01-07 18:21 ` Sam Ravnborg
2020-01-07 18:21 ` Sam Ravnborg
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=20200102160534.GJ22390@dell \
--to=lee.jones@linaro.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=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=peda@axentia.se \
--cc=sam@ravnborg.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.