summaryrefslogtreecommitdiff
path: root/wiki/Chat_log/20211202-mm-chatlog
diff options
context:
space:
mode:
authorKuninori Morimoto <kuninori.morimoto.gx@renesas.com>2021-12-03 07:32:25 +0900
committerKuninori Morimoto <kuninori.morimoto.gx@renesas.com>2021-12-03 07:32:25 +0900
commit81aa85f8f360618698f23c93ab4b5827609371b4 (patch)
tree89fc4d92ae5893b40c0bbebdcaf56a65f4a25876 /wiki/Chat_log/20211202-mm-chatlog
parent520e2ac21fce8447ce849bdaccdb65345b6137f8 (diff)
wiki: Add M/M chatlog for 2021-12-02
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Diffstat (limited to 'wiki/Chat_log/20211202-mm-chatlog')
-rw-r--r--wiki/Chat_log/20211202-mm-chatlog170
1 files changed, 170 insertions, 0 deletions
diff --git a/wiki/Chat_log/20211202-mm-chatlog b/wiki/Chat_log/20211202-mm-chatlog
new file mode 100644
index 0000000..9efcc5f
--- /dev/null
+++ b/wiki/Chat_log/20211202-mm-chatlog
@@ -0,0 +1,170 @@
+< pinchartl> welcome to the MM meeting
+< pinchartl> Topic 1. Status Check for the Multimedia Tasks
+<pinchartl> * Jacopo: [18:11]
+<pinchartl> Since last meeting:
+<pinchartl> - Multiplexed streams support for GMSL: rebased on v9
+<pinchartl> - Review VIN/CSI multiplex support
+<pinchartl> - Minor max9271 fixes
+<pinchartl> Until next meeting:
+<pinchartl> - resume Condor GMSL upstreaming which is part of new BSP ticket
+<pinchartl> - v4l2 multiplex support fo adv748x
+<pinchartl> Issues and blockers: None
+<pinchartl> jmondi: any comment ?
+<jmondi> pinchartl: maybe for later
+<pinchartl> ok :)
+<pinchartl> * Kieran:
+<pinchartl> Since last meeting:
+<pinchartl> - linux-media reviews
+<pinchartl> - gpu: drm: panel-edp: Fix edp_panel_entry documentation
+<pinchartl> - arm64: dts: renesas: Merge hdmi0_con
+<pinchartl> - V3U DU / DSI clock issues resolved \o/ - Various DU/DSI cleanup
+ patches submitted to be squashed. - DU Driver patches posted - DT
+ patches posted
+<pinchartl> Until next meeting: [18:12]
+<pinchartl> - INTC_EX retesting (sorry, didn't get to this with the V3U
+ display work)
+<pinchartl> - Test CAN FD support from Uli
+<pinchartl> Issues and Blockers:
+<pinchartl> - [PATCH v2] Input: add 'safe' user switch codes
+<pinchartl> linux-input doesn't seem to want our test switches or even test
+ buttons to be supportable
+<pinchartl> kbingham: any comment ?
+<kbingham> No - just happy that I finally found and solved the v3U display
+ issue
+<pinchartl> \o/
+<pinchartl> that's very nice indeed, DSI support can now land upstream
+<pinchartl> I've moved your DT validation issue to the discussion points, but
+ it seems it should just be discussed with Rob on mailing lists,
+ right ? [18:13]
+*** damm (~damm@s214090.ppp.asahi-net.or.jp) has quit: Remote host closed the
+ connection [18:14]
+<pinchartl> * Laurent:
+<pinchartl> Since last meeting:
+<pinchartl> - V4L2 multiplexed streams development
+<pinchartl> Continued working with Tomi Valkeinen. Still work in progress (v10
+ is out).
+<pinchartl> - Tested HDMI probe issue with v5.15
+<pinchartl> The issue was caused by the missing CONFIG_DRM_DISPLAY_CONNECTOR
+ kernel option.
+<pinchartl> Bricked the ULCB in the process, BL2 doesn't want to calibrate the
+ DRAM anymore :-(
+<pinchartl> - Fix issues and posted new versions of V3U DSI driver
+*** damm (~damm@s214090.ppp.asahi-net.or.jp) has joined channel #periperi
+<pinchartl> Should hopefully be merged in v5.17.
+<pinchartl> - Investigated format modifiers usage in Weston
+<pinchartl> Context: "[PATCH] drm: rcar-du: add modifiers support"
+<pinchartl> It turns out that not specifying modifiers and specifying a linear
+ modifier isn't the same thing. Some old drivers (radeon and
+ nouveau pre-nv50) don't expose modifiers to userspace, and use
+ heuristics to select linear or tiled formats. Weston thus can't
+ assume that drivers that don't expose the modifiers API use linear
+ formats only.
+<pinchartl> - Merged miscellaneous display-related fixes for v5.17
+<pinchartl> Until next meeting:
+<pinchartl> - V4L2 multiplexed streams development
+<pinchartl> - Upstream pending SN65DSI86 patches (last missing piece for V3U
+ display)
+<pinchartl> - Hopefully unbrick my ULCB
+<pinchartl> Issues and blockers:
+<pinchartl> - Bricked ULCB H3 ES2.0. Can anyone help ?
+<pinchartl> any comment ?
+<wsa> did it just happen or did you do something special? [18:15]
+<pinchartl> I tried to update u-boot
+<pinchartl> which in turn required an update of TF-A
+<pinchartl> and *boom*
+<pinchartl> now BL2 fails to calibrate the DRAM
+<pinchartl> moriperi: I've seen your *maker tool announcements, maybe I should
+ look at that to see if it can compile a working TF-A for ULCB
+ [18:16]
+<moriperi> yes, please do that
+<pinchartl> I'm wondering, however, if you may have pre-compiled binaries that
+ I could test ?
+<pinchartl> it would save me disk space and CPU time for a test :-)
+<moriperi> Hehe, but If I did it, I need to send source code. because of GPL
+ [18:17]
+<pinchartl> you have sent the source code already, it's in the *maker git
+ trees :-) [18:18]
+<moriperi> Maybe yes
+<pinchartl> I've compiled the latest TF-A myself, and it doesn't work. I
+ wonder if the issue is specific to my board, if I picked a wrong
+ TF-A version, or if I compiled it incorrectly
+<moriperi> No, I need to send it not tool source, but U-boot source [18:19]
+<pinchartl> I can try compiling everything through yocto, but if you have
+ binaries already, it would be nice to test them. if they work I'll
+ investigate to see what mistake I did, if they don't work,
+ well... I don't know in that case :-)
+<pinchartl> I only need the TF-A binaries actually
+<moriperi> Hmm. I think we can use PeriJect Wiki to share binary ?
+<pinchartl> BL2, BL2, cert and boot params
+<pinchartl> those are not GPL I think [18:20]
+<pinchartl> if you can share them that would be great, otherwise I'll buy a
+ new disk and start a yocto build :-) [18:21]
+<pinchartl> * Morimoto-san
+<pinchartl> Since last meeting:
+<pinchartl> - Posted ALSA Framework cleanup patch, and was accepted
+<pinchartl> - Get many feedback from ML about my issue and/or patch, but had
+ no time to check it yet
+<pinchartl> - Customer want to use complex connected Sound, but has some
+ issue. Not investigated yet.
+<pinchartl> Until next meeting:
+<pinchartl> - Need to check HDMI-Sound probe issue (From Laurent) [18:22]
+<pinchartl> - Need to check New Sound Card DT warning issue (From Geert)
+<pinchartl> - Need to check Sound complex connection issue (From Renesas Guy)
+<pinchartl> Issues and blockers: None
+<pinchartl> moriperi: any comment ?
+<pinchartl> there seems to be a never-ending supply of sound issue that you
+ have to solve :-)
+<moriperi> Thanks. no comment.
+<moriperi> ./yocto-make -b -a -m 5.1.0 m3ulcb
+<moriperi> Oops
+<pinchartl> that's a useful comment :-)
+<moriperi> You need is only "./yocto-make 5.1.0 h3ulcb" on maker
+<pinchartl> (note that I have a H3 ES2.0 ULCB, not M3)
+<pinchartl> ok
+<pinchartl> I'll see if that can be done without an extra 100GB of disk space
+ and 3 days of compilation :-) [18:23]
+<pinchartl> * Niklas:
+<pinchartl> Since last meeting:
+<pinchartl> - [PATCH 0/4] media: videobuf2: Add a transfer error event
+<pinchartl> - [PATCH] rcar-vin: Add check for completed capture before
+ completing buffer
+<pinchartl> - [PATCH] dt-bindings: staging: media: i2c: Add bindings for Maxim
+ Integrated MAX96712
+<pinchartl> - [PATCH] rcar-vin: Update format alignment constraints
+<pinchartl> - [PATCH v2 0/3] media: rcar-{csi2,vin}: Move to full Virtual
+ Channel routing per CSI-2 IP
+<pinchartl> - [PATCH] media: rcar-csi2: Suppress bind and unbind nodes in
+ sysfs
+<pinchartl> - [PATCH] media: rcar-vin: Disallow unbinding and binding of
+ individual VINs
+<pinchartl> - [PATCH] media: rcar-vin: Do not hold the group lock when
+ unregistering notifier
+<pinchartl> Until next meeting:
+<pinchartl> - Address more capture related issues from periject
+<pinchartl> - When the routing patches gets merged continue the then unblocked
+ UDS work
+<pinchartl> - Follow up pending patches
+<pinchartl> Issues and blockers: None
+<pinchartl> neg: any comment ?
+<neg> No comment on the status, I will be out-of-office Dec 21 -- Jan 4, so I
+ expect a little bit less then normal output until next meeting.
+<pinchartl> thank you [18:24]
+<pinchartl> I expect everybody to take some holidays ?
+<pinchartl> I'll likely be away on the 24th, 28th and 29th [18:25]
+*** damm (~damm@s214090.ppp.asahi-net.or.jp) has quit: Remote host closed the
+ connection
+<kbingham> indeed, I'll have holidays around Xmas/NYE
+*** damm (~damm@s214090.ppp.asahi-net.or.jp) has joined channel #periperi
+<pinchartl> do you know the dates already ? [18:26]
+<pinchartl> jmondi: how about you ?
+<pinchartl> any discussion topic for today ?
+<jmondi> pinchartl: no plans, I'll be around with a few days of holiday here
+ and there [18:27]
+<kbingham> I know the date of Xmas day, and NYE but not more than that yet ;-)
+<pinchartl> I assume this means no discussion topic [18:28]
+<pinchartl> I thus propose adjourning the meeting [18:29]
+<pinchartl> does anyone second ?
+<jmondi> seconded :)
+<neg> second
+<pinchartl> meeting adjourned
+