[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <164341363054.694916.12375594292083230045.b4-ty@kernel.org>
Date: Fri, 28 Jan 2022 23:47:10 +0000
From: Mark Brown <broonie@...nel.org>
To: Detlev Casanova <detlev.casanova@...labora.com>,
linux-kernel@...r.kernel.org
Cc: Liam Girdwood <lgirdwood@...il.com>,
Dave Stevenson <dave.stevenson@...pberrypi.com>
Subject: Re: [PATCH v3 0/9] regulator: rpi-panel: Support official Raspberry Pi 7 inches touchscreen
On Mon, 24 Jan 2022 17:01:20 -0500, Detlev Casanova wrote:
> This patchset provides different fixes to the rpi-panel-attiny-regulator driver.
>
> This is a preparation patchset for supporting the official Raspberry Pi 7
> inches touchscreen.
>
> It has been tested with a Raspberry Pi 4 B and the official Raspberry Pi 7
> inches touchscreen.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/9] regulator: rpi-panel: Register with a unique backlight name
commit: 7291e7d686308b4a77f43225eaf1753cb20cc692
[2/9] regulator: rpi-panel: Handle I2C errors/timing to the Atmel
commit: 5665eee7a3800430e7dc3ef6f25722476b603186
[3/9] regulator: rpi-panel: Serialise operations.
commit: 00440bcd211a3cac686b730447c4efa3d4c84c2a
[4/9] regulator: rpi-panel: Ensure the backlight is off during probe.
commit: 89339a2ae7608138dbcccda8db67a87870550cbe
[5/9] regulator: rpi-panel: Convert to drive lines directly
commit: 4866e35e48e6bd2bef1c567b05105e7fb3493ff9
[6/9] regulator: rpi-panel: Add GPIO control for panel and touch resets
commit: 8c518eb4039102445b1b7bd6626aba0fef65b753
[7/9] regulator: rpi-panel: Remove get_brightness hook
commit: 1d746d448f421094a71ba634399d2ee61669513f
[8/9] regulator/rpi-panel-attiny: Use the regmap cache
commit: 5fa4e8ea649009566a1b080f836ce23d4ce0c416
[9/9] regulator/rpi-panel-attiny: Use two transactions for I2C read
commit: e4a7e3f741f797d93d97a153b0f6a862d19a1304
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
Powered by blists - more mailing lists