Hello there,
This RFC introduces support for the FS035VG158 LCD panel, cleaning up
the nv3052c driver on the way and documentating existing panel code.
This revision is mostly a resend and ask for more feedback.
I have tested that it works on next-20231208.
John.
v4 -> v5:
- Add Reviewed-By
SPI drivers needs their own list of compatible device IDs in order
for automatic module loading to work. Add those for this driver.
Signed-off-by: John Watts
Reviewed-by: Jessica Zhang
Reviewed-by: Linus Walleij
---
drivers/gpu/drm/panel/panel-newvision-nv3052c.c | 7 +++
1 file changed,
Fascontek manufactures LCD panels such as the FS035VG158.
Signed-off-by: John Watts
Acked-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
Many of these registers have a known name in the public datasheet.
Document them as comments for reference.
Signed-off-by: John Watts
Reviewed-by: Jessica Zhang
Reviewed-by: Linus Walleij
---
drivers/gpu/drm/panel/panel-newvision-nv3052c.c | 261
1 file changed, 132
This is a small 3.5" 640x480 IPS LCD panel.
Signed-off-by: John Watts
Reviewed-by: Rob Herring
---
.../display/panel/fascontek,fs035vg158.yaml| 56 ++
1 file changed, 56 insertions(+)
diff --git
Remove common properties listed in common yaml files.
Add required properties needed to describe the panel.
Signed-off-by: John Watts
Reviewed-by: Rob Herring
---
.../devicetree/bindings/display/panel/leadtek,ltk035c5444t.yaml | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
Panel initialization registers are per-display and not tied to the
controller itself. Different panels will specify their own registers.
Attach the sequences to the panel info struct so future panels
can specify their own sequences.
Signed-off-by: John Watts
Reviewed-by: Jessica Zhang
---
This display is extremely similar to the LTK035C5444T, but still has
some minor variations in panel initialization.
Signed-off-by: John Watts
Reviewed-by: Jessica Zhang
Reviewed-by: Linus Walleij
---
drivers/gpu/drm/panel/panel-newvision-nv3052c.c | 223
1 file
On Wed, Nov 22, 2023 at 07:06:50AM +0700, Bagas Sanjaya wrote:
> Hi,
>
> I notice a regression report on Bugzilla [1]. Quoting from it:
>
> > After upgrading from 6.5.9 to 6.6.1 on my Dell Latitude E6420 (Intel
> > i5-2520M) with EndeavourOS, the boot process would hang at "loading initial
> >
> On Dec 5, 2023, at 2:32, Boris Brezillon
> wrote:
>
> Hello,
>
> This is the 3rd version of the kernel driver for Mali CSF-based GPUs.
>
> With all the DRM dependencies being merged (drm-sched single entity and
> drm_gpuvm), I thought now was a good time to post a new version. Note
> that
On Wed, Nov 29, 2023 at 09:13:34AM +, Sean Young wrote:
> drivers/input/misc/da7280.c | 4 +--
> drivers/input/misc/pwm-beeper.c | 4 +--
> drivers/input/misc/pwm-vibra.c| 8 +++---
Acked-by: Dmitry Torokhov # for input
Thanks.
--
Dmitry
On Thu, Dec 07, 2023 at 04:52:32PM -0800, Mina Almasry wrote:
> From: Jakub Kicinski
>
> Releasing the DMA mapping will be useful for other types
> of pages, so factor it out. Make sure compiler inlines it,
> to avoid any regressions.
>
> Signed-off-by: Jakub Kicinski
> Signed-off-by: Mina
On Thu, Dec 07, 2023 at 04:52:31PM -0800, Mina Almasry wrote:
[...]
>
> Today, the majority of the Device-to-Device data transfers the network are
'the network' in above can be removed.
> implemented as the following low level operations: Device-to-Host copy,
> Host-to-Host network transfer,
On 12/8/23 23:25, Mina Almasry wrote:
On Fri, Dec 8, 2023 at 2:56 PM Pavel Begunkov wrote:
On 12/8/23 00:52, Mina Almasry wrote:
...
+ if (pool->p.queue)
+ binding = READ_ONCE(pool->p.queue->binding);
+
+ if (binding) {
+ pool->mp_ops = _devmem_ops;
+
Hi,
On 2023-12-05 14:02, Rob Clark wrote:
> From: Rob Clark
>
> Container fences have burner contexts, which makes the trick to store at
> most one fence per context somewhat useless if we don't unwrap array or
> chain fences.
>
> Signed-off-by: Rob Clark
Link:
On Fri, Dec 8, 2023 at 4:48 PM Chris Morgan wrote:
> From: Chris Morgan
>
> The RG-ARC panel is a panel specific to the Anbernic RG-ARC. It is 4
> inches in size (diagonally) with a resolution of 480x640.
>
> Signed-off-by: Chris Morgan
Reviewed-by: Linus Walleij
Yours,
Linus Walleij
On 12/8/23 12:22 PM, Mina Almasry wrote:
> On Fri, Dec 8, 2023 at 9:48 AM David Ahern wrote:
>>
>> On 12/7/23 5:52 PM, Mina Almasry wrote:
> ...
>>> +
>>> + xa_for_each(>bound_rxq_list, xa_idx, rxq) {
>>> + if (rxq->binding == binding) {
>>> + /* We hold the
The SM8150 platform doesn't support DDR sleep stats, so it needs
SoC-specific compat string for the RPMh stats data.
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/sm8150.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/qcom/sm8150.dtsi
Enable the USB-C related functionality for the USB-C port on this board.
This includes OTG, PowerDelivery and DP AltMode. Also enable the
DisplayPort itself.
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/sm8150-hdk.dts | 124 +++-
1 file changed, 123
Expand first USB host controller device node with the OF ports required
to support USB-C / DisplayPort switching.
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/sm8150.dtsi | 19 +++
1 file changed, 19 insertions(+)
diff --git
Expand Combo USB+DP QMP PHY device node with the OF ports required to
support USB-C / DisplayPort switching.
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/sm8150.dtsi | 23 +++
1 file changed, 23 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sm8150.dtsi
Add DSI outputs and link them to the onboard Lontium LT9611 DSI-to-HDMI
bridge, enabling HDMI output on this board. While adding the display
resources, also drop the headless ("amd,imageon") compat string from the
GPU node, since the board now has output.
Signed-off-by: Dmitry Baryshkov
---
Add device tree node for the DisplayPort controller and link it to the
display controller interface.
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/sm8150.dtsi | 87
1 file changed, 87 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sm8150.dtsi
The SM8150-HDK uses two different regulators to power up SuperSpeed USB
PHYs. The L5A regulator is used for the second USB host, while the first
(OTG) USB host uses different regulator, L18A. Fix the regulator for the
usb_1 QMPPHY and (to remove possible confusion) drop the
usb_ss_dp_core_1/_2
Add required-opps property to the display clock controller. This makes
it cast minimal vote on the MMCX lane and prevents further 'clock stuck'
errors when enabling the display.
Fixes: 2ef3bb17c45c ("arm64: dts: qcom: sm8150: Add DISPCC node")
Signed-off-by: Dmitry Baryshkov
---
Add compatible string for the DisplayPort controller found on the
Qualcomm SM8150 platform.
Signed-off-by: Dmitry Baryshkov
---
Documentation/devicetree/bindings/display/msm/dp-controller.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git
Enable display output on the SM8150 HDK device. This includes HDMI
output through the onboard DSI-HDMI bridge and DP output on the USB-C
port.
Dmitry Baryshkov (9):
dt-bindings: display: msm: dp: declare compatible string for sm8150
arm64: dts: qcom: sm8150: use SoC-specific compat for RPMh
There is a spelling mistake in a pr_err error message. Fix it.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/i915/gem/selftests/i915_gem_dmabuf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/gem/selftests/i915_gem_dmabuf.c
There is a spelling mistake in a DRM_DEBUG_KMS message. Fix it.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/gma500/cdv_intel_dp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/gma500/cdv_intel_dp.c
b/drivers/gpu/drm/gma500/cdv_intel_dp.c
index
On Sat, Dec 9, 2023, at 22:29, Samuel Holland wrote:
> On 2023-12-09 2:38 PM, Arnd Bergmann wrote:
>> On Fri, Dec 8, 2023, at 06:04, Samuel Holland wrote:
>>> On 2023-11-29 6:42 PM, Nathan Chancellor wrote:
https://lore.kernel.org/20231019205117.GA839902@dev-arch.thelio-3990X/
>>>
>>> I
On Fri, Dec 8, 2023, at 06:04, Samuel Holland wrote:
> On 2023-11-29 6:42 PM, Nathan Chancellor wrote:
>> On Thu, Nov 23, 2023 at 02:23:01PM +, Conor Dooley wrote:
>>> On Tue, Nov 21, 2023 at 07:05:15PM -0800, Samuel Holland wrote:
RISC-V uses kernel_fpu_begin()/kernel_fpu_end() like
Uwe Kleine-König писал(а) 09.12.2023 20:31:
> It's the ti_sn65dsi86.pwm auxiliary driver that creates the pwmchip, so
> let the auxiliary device be the parent of the pwm device.
>
> Note that getting a reference to the ti-sn65dsi86's pwm using pwm_get()
> isn't affected by this change as
It's the ti_sn65dsi86.pwm auxiliary driver that creates the pwmchip, so
let the auxiliary device be the parent of the pwm device.
Note that getting a reference to the ti-sn65dsi86's pwm using pwm_get()
isn't affected by this change as ti_sn65dsi86_add_aux_device() sets the
auxiliary device's
It's the ti_sn65dsi86.pwm auxiliary driver that creates the pwmchip, so
let the auxiliary device be the parent of the pwm device.
Note that getting a reference to the ti-sn65dsi86's pwm using pwm_get()
isn't affected by this change as ti_sn65dsi86_add_aux_device() sets the
auxiliary device's
Hi Andy,
Am Samstag, 9. Dezember 2023, 02:26:25 CET schrieb Andy Yan:
> Hi Heiko:
>
> On 12/9/23 00:29, Heiko Stübner wrote:
> > Am Donnerstag, 7. Dezember 2023, 09:02:35 CET schrieb Andy Yan:
> >> From: Andy Yan
> >>
> >> Add a Rockchip RK3588 compatible
> >>
> >> Signed-off-by: Andy Yan
> >
On Wed, Nov 29, 2023 at 09:13:34AM +, Sean Young wrote:
> In order to introduce a pwm api which can be used from atomic context,
> we will need two functions for applying pwm changes:
>
> int pwm_apply_might_sleep(struct pwm *, struct pwm_state *);
> int pwm_apply_atomic(struct
On Wed, Dec 06, 2023 at 11:49:46AM +0300, kova...@altlinux.org wrote:
> From: Vasiliy Kovalev
>
> This reverts commit 5a46dc8e4a064769e916d87bf9bccae75afc7289.
>
> Commit 50b6f2c8297793f7f3315623db78dcff85158e96 upstream.
>
> Commit 5a46dc8e4a0647 ("drm/edid: Fix csync detailed mode parsing")
On 08/12/2023 16:48, Chris Morgan wrote:
> From: Chris Morgan
>
> The RG-ARC panel is a panel specific to the Anbernic RG-ARC. It is 4
> inches in size (diagonally) with a resolution of 480x640.
>
> Signed-off-by: Chris Morgan
> ---
Acked-by: Krzysztof Kozlowski
Best regards,
Krzysztof
38 matches
Mail list logo
