On Sat, Mar 12, 2022 at 01:53:26AM +, Hyeonggon Yoo wrote:
> On Fri, Mar 04, 2022 at 04:06:19PM +0900, Byungchul Park wrote:
> > Hi Linus and folks,
> >
> > I've been developing a tool for detecting deadlock possibilities by
> > tracking wait/event rather than lock(?) acquisition order to try
On Fri, Mar 11, 2022 at 12:36:09PM +0100, Sam Ravnborg wrote:
> Hi Xin.
>
> On Fri, Mar 11, 2022 at 06:35:25PM +0800, Xin Ji wrote:
> > The property length which returns from "of_get_property", it means array
> > bytes count if the property has prefix as "/bits/ 8". The driver should
> > call func
On 3/13/2022 5:38 PM, Andi Shyti wrote:
Hi Michal,
[...]
+static ssize_t punit_req_freq_mhz_show(struct device *dev,
+ struct device_attribute *attr,
+ char *buff)
+{
+ struct intel_gt *gt = intel_gt_sysfs_get_dr
Hi Michal,
[...]
> > +static ssize_t punit_req_freq_mhz_show(struct device *dev,
> > + struct device_attribute *attr,
> > + char *buff)
> > +{
> > + struct intel_gt *gt = intel_gt_sysfs_get_drvdata(dev, attr->attr.name);
> > +
Hi Andrzej,
[...]
> > +static ssize_t act_freq_mhz_show(struct device *dev,
> > +struct device_attribute *attr, char *buff)
> > +{
> > + s64 actual_freq = sysfs_gt_attribute_r_func(dev, attr,
> > + __act_freq_mhz_show);
>
Hi Andrzej,
> > Now tiles have their own sysfs interfaces under the gt/
> > directory. Because RC6 is a property that can be configured on a
> > tile basis, then each tile should have its own interface
> >
> > The new sysfs structure will have a similar layout for the 4 tile
> > case:
> >
> > /s
> > > > > +struct intel_gt *intel_gt_sysfs_get_drvdata(struct device *dev,
> > > > > + const char *name)
> > > > > +{
> > > > > + struct kobject *kobj = &dev->kobj;
> > > > > +
> > > > > + /*
> > > > > + * We are interested at knowing from where
Den 13.03.2022 17.07, skrev Tom Rix:
>
> On 3/13/22 8:41 AM, Noralf Trønnes wrote:
>>
>> Den 13.03.2022 15.10, skrev t...@redhat.com:
>>> From: Tom Rix
>>>
>>> repaper_spi_transfer() allocates a single byte
>>> for the spi header and then another buffer for
>>> the payload. Combine the allocs
On 3/13/22 18:50, Krzysztof Kozlowski wrote:
On 13/03/2022 18:09, Marek Vasut wrote:
On 3/13/22 16:47, Krzysztof Kozlowski wrote:
Hi,
[...]
diff --git a/Documentation/devicetree/bindings/display/bridge/nxp,ldb.yaml
b/Documentation/devicetree/bindings/display/bridge/nxp,ldb.yaml
new file mod
Hi Andrzej,
I'm sorry, but I'm not fully understanding,
> > > > +struct intel_gt *intel_gt_sysfs_get_drvdata(struct device *dev,
> > > > + const char *name)
> > > > +{
> > > > + struct kobject *kobj = &dev->kobj;
> > > > +
> > > > + /*
> > > >
Hi
Am 08.03.22 um 18:43 schrieb Jocelyn Falempe:
commit f86c3ed55920 ("drm/mgag200: Split PLL setup into compute and
update functions") introduced a regression for g200wb and g200ew.
The PLLs are not set up properly, and VGA screen stays
black, or displays "out of range" message.
MGA1064_WB_P
Commit 6f29e04938bf ("fbdev: Improve performance of sys_imageblit()")
broke sys_imageblit() for image width that are not aligned to 8-bit
boundaries. Fix this by handling the trailing pixels on each line
separately. The performance improvements in the original commit do not
regress by this change.
Commit 0d03011894d2 ("fbdev: Improve performance of cfb_imageblit()")
broke cfb_imageblit() for image widths that are not aligned to 8-bit
boundaries. Fix this by handling the trailing pixels on each line
separately. The performance improvements in the original commit do not
regress by this change.
Recent optimization of the fbdev image-bitting helpers broke the code for
image width that do not align with multiples of 8. Both, sys and cfb, are
affected. Fix this problem by handling the trailing pixels on each line
separately.
Tested with simpledrm and the 7x14 font.
Thomas Zimmermann (2):
Hi Geert
Am 10.03.22 um 20:23 schrieb Geert Uytterhoeven:
[...]
How do I activate the 7x14 font? It's compiled into the kernel already
(CONFIG_FONT_7x14=y).
Documentation/fb/fbcon.rst:1. fbcon=font:
Or just disable all other fonts.
Thanks. I've been able to reproduce the problem and will s
https://bugzilla.kernel.org/show_bug.cgi?id=205089
--- Comment #35 from Christine Lemmer-Webber (cweb...@dustycloud.org) ---
Here's the dmesg output that appears to be associated with when everything
broke:
[ 51.645260] amdgpu :05:00.0: amdgpu: [gfxhub0] retry page fault
(src_id:0 ring:0 vm
On 13/03/2022 18:09, Marek Vasut wrote:
> On 3/13/22 16:47, Krzysztof Kozlowski wrote:
>
> Hi,
>
> [...]
>
>>> diff --git a/Documentation/devicetree/bindings/display/bridge/nxp,ldb.yaml
>>> b/Documentation/devicetree/bindings/display/bridge/nxp,ldb.yaml
>>> new file mode 100644
>>> index 00
https://bugzilla.kernel.org/show_bug.cgi?id=205089
Christine Lemmer-Webber (cweb...@dustycloud.org) changed:
What|Removed |Added
CC||cweb...
On 3/13/22 16:47, Krzysztof Kozlowski wrote:
Hi,
[...]
diff --git a/Documentation/devicetree/bindings/display/bridge/nxp,ldb.yaml
b/Documentation/devicetree/bindings/display/bridge/nxp,ldb.yaml
new file mode 100644
index 0..a05dd05547836
--- /dev/null
+++ b/Documentation/devicetre
On 3/13/22 8:41 AM, Noralf Trønnes wrote:
Den 13.03.2022 15.10, skrev t...@redhat.com:
From: Tom Rix
repaper_spi_transfer() allocates a single byte
for the spi header and then another buffer for
the payload. Combine the allocs into a single
buffer with offsets. To simplify the offsets
put
On 13/03/2022 13:38, Marek Vasut wrote:
> The i.MX8MP contains two syscon registers which are responsible
> for configuring the on-SoC DPI-to-LVDS serializer. Add DT binding
> which represents this serializer as a bridge.
>
> Signed-off-by: Marek Vasut
> Cc: Laurent Pinchart
> Cc: Lucas Stach
>
Den 13.03.2022 15.10, skrev t...@redhat.com:
> From: Tom Rix
>
> repaper_spi_transfer() allocates a single byte
> for the spi header and then another buffer for
> the payload. Combine the allocs into a single
> buffer with offsets. To simplify the offsets
> put the header after the payload.
Hi Abhinav
On Fri, Mar 11, 2022 at 09:47:17AM -0800, Abhinav Kumar wrote:
> On 3/10/2022 11:28 PM, Laurent Pinchart wrote:
> > On Thu, Mar 10, 2022 at 05:49:59PM -0800, Abhinav Kumar wrote:
> >> Make changes to rcar_du driver to start using drm_encoder pointer
> >> for drm_writeback_connector.
> >
From: Tom Rix
repaper_spi_transfer() allocates a single byte
for the spi header and then another buffer for
the payload. Combine the allocs into a single
buffer with offsets. To simplify the offsets
put the header after the payload.
Signed-off-by: Tom Rix
---
drivers/gpu/drm/tiny/repaper.c |
While adding CEA modes, try to get available EEODB block
number. Then based on it to parse numbers of ext blocks,
retrieve CEA information and add more CEA modes.
Cc: Jani Nikula
Cc: Ville Syrjala
Cc: Ankit Nautiyal
Cc: Drew Davenport
Cc: intel-gfx
Signed-off-by: Lee Shawn C
---
drivers/gpu
Find HF-SCDB information in CEA extensions block. And retrieve
Max_TMDS_Character_Rate that support by sink device.
v2: HF-SCDB and HF-VSDBS carry the same SCDS data. Reuse
drm_parse_hdmi_forum_vsdb() to parse this packet.
Cc: Jani Nikula
Cc: Ville Syrjala
Cc: Ankit Nautiyal
Cc: Drew Daven
According to HDMI 2.1 spec.
"The HDMI Forum EDID Extension Override Data Block (HF-EEODB)
is utilized by Sink Devices to provide an alternate method to
indicate an EDID Extension Block count larger than 1, while
avoiding the need to present a VESA Block Map in the first
E-EDID Extension Block."
I
Try to find and parse more CEA ext blocks if edid->extensions
is greater than one.
v2: split prvious patch to two. And do CEA block parsing
in this one.
v3: simplify this patch based on previous change.
v4: refine patch v3.
Cc: Jani Nikula
Cc: Ville Syrjala
Cc: Ankit Nautiyal
Cc: Drew Dave
drm_find_cea_extension() always look for a top level CEA block. Pass
ext_index from caller then this function to search next available
CEA ext block from a specific EDID block pointer.
v2: save proper extension block index if CTA data information
was found in DispalyID block.
v3: using differe
Support to parse multiple CEA extension blocks and HF-EEODB to
extend drm edid driver's capability.
v4: add one more patch to support HF-SCDB
v5: HF-SCDB and HF-VSDBS carry the same SCDS data. Reuse
drm_parse_hdmi_forum_vsdb() to parse this packet.
v6: save proper extension block index if CTA
On Sun, Mar 13, 2022 at 6:13 AM Piotr Oniszczuk
wrote:
>
>
>
> > Wiadomość napisana przez Peter Geis w dniu
> > 26.01.2022, o godz. 21:24:
> >
> > The hdmi-cec clock must be 32khz in order for cec to work correctly.
> > Ensure after enabling the clock we set it in order for the hardware to
> > w
The i.MX8MP contains two syscon registers which are responsible
for configuring the on-SoC DPI-to-LVDS serializer. Implement a
simple bridge driver for this serializer.
Signed-off-by: Marek Vasut
Cc: Laurent Pinchart
Cc: Lucas Stach
Cc: Maxime Ripard
Cc: Peng Fan
Cc: Robby Cai
Cc: Robert Fos
The i.MX8MP contains two syscon registers which are responsible
for configuring the on-SoC DPI-to-LVDS serializer. Add DT binding
which represents this serializer as a bridge.
Signed-off-by: Marek Vasut
Cc: Laurent Pinchart
Cc: Lucas Stach
Cc: Maxime Ripard
Cc: Peng Fan
Cc: Rob Herring
Cc: R
Hi Laurent,
Thanks for the feedback.
> Subject: Re: [RFC 11/28] drm: rcar-du: Add num_rpf to struct
> rcar_du_device_info
>
> Hi Biju,
>
> Thank you for the patch.
>
> On Wed, Jan 12, 2022 at 05:45:55PM +, Biju Das wrote:
> > Number of RPF's VSP is different on R-Car and RZ/G2L R-Car Gen3
https://bugzilla.kernel.org/show_bug.cgi?id=211807
notsyncing (song...@gmail.com) changed:
What|Removed |Added
CC||song...@gmail.com
--- Co
35 matches
Mail list logo
