<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style>
***: ten1572377432463050 has joined #linux-media
<br> tmerciai has quit IRC (Ping timeout: 480 seconds)
<br> tmerciai has joined #linux-media
<br> ten1572377432463050 has quit IRC (Remote host closed the connection)
<br> ten1572377432463050 has joined #linux-media
<br> tmerciai has quit IRC (Ping timeout: 480 seconds)
<br> eelstrebor has joined #linux-media
<br> xecutertool has joined #linux-media
<br> xecutercmd has quit IRC (Ping timeout: 480 seconds)
<br> eelstrebor has quit IRC (Quit: Ex-Chat)
<br> tmerciai has joined #linux-media
<br> mvaittin has joined #linux-media
uajain: <u>sailus</u>: imx335 patches are already in. I think you meant IMX283 driver
<br> I'll resend.
***: tmerciai has quit IRC (Ping timeout: 480 seconds)
<br> tmerciai has joined #linux-media
uajain: <u>sailus</u>: Do you really mean imx335 patches? They are already in, in your 'test' branch.
<br> And for the IMX283 driver, the v4 version https://lore.kernel.org/linux-media/20240402-kernel-name-extraversion-v4-0-fb776893e4ec@ideasonboard.com/#t
<br> applies cleanly on your 'test' branch
sailus: <u>uajain</u>: Ah, right. It was too late in the evening to apply any patches. X-)
<br> Imx283 patches applied, thanks!
uajain: cool :)
<br> <u>sailus</u>: I think I need to resend anyways, because there is a change in your branch I think regarding pm_runtime_get_if_active()
sailus: <u>uajain</u>: That would have gone via the linux-pm tree.
uajain: oh that's why probably I missed it (I was based on media-stage tree when I sent out the v4)
<br> I am testing and compiling with W=1, will send out a v5 shortly after testing it.
sailus: Ah, the ign_use_count argument is gone. Yeah, I can address that.
<br> I thought that changes was already in rc1.
<br> Oh well...
uajain: Should I send out v5 with that addressed, if you want ?
sailus: No need to.
uajain: Ok :)
***: mvaittin has quit IRC (Ping timeout: 480 seconds)
sailus: It's in my "streaming" branch now.
hverkuil: <u>sailus</u>: will you make a PR? As I understand it you want the line base metadata series (https://patchwork.linuxtv.org/project/linux-media/list/?series=12719), the stream improvements series (https://patchwork.linuxtv.org/project/linux-media/list/?series=12708) and the RPi driver (https://patchwork.linuxtv.org/project/linux-media/list/?series=12707) merged, right?
***: djrscally has joined #linux-media
sailus: <u>hverkuil</u>: Roughly yes. Additionally IPU6 ISYS driver and the CCS driver improvements (used to be part of the metadata series) and the imx283 driver.
<br> It's a lot of patches.
<br> There are a bunch of other sensor driver patches, too.
<br> I'll try to make a PR on the first ones soon.
hverkuil: I think the line-base metadata series is the only one that changes the uAPI, right? So I would prefer to have a PR with that series + a driver that uses it (that's the RPi one).
***: sgruszka has joined #linux-media
sailus: <u>hverkuil</u>: IPU6 driver as well. Although the API isn't yet enabled by the series, these drivers are usable without the routing API, too.
<br> Internally they still depend on some of the patches in question.
hverkuil: If I remember correctly you have a series that depends on the stream improvement patches as well, so another PR with the stream improvement patches + a driver using those. After that PRs for the various other drivers that depend on the other core changes, I leave it to you to split it up.
sailus: Yes, that would be more than one series.
<br> <u>hverkuil</u>: First one sent.
***: jmassot has joined #linux-media
<br> mvaittin has joined #linux-media
<br> ao2 has joined #linux-media
<br> ao2 has quit IRC (Quit: Leaving)
<br> nas_chung has joined #linux-media
<br> jmassot has quit IRC (Remote host closed the connection)
<br> jmassot has joined #linux-media
<br> jmassot has quit IRC (Remote host closed the connection)
<br> Mo has joined #linux-media
<br> abws_ has joined #linux-media
<br> ten1572377432463050 has quit IRC (Remote host closed the connection)
<br> ten1572377432463050 has joined #linux-media
<br> hansg has joined #linux-media
<br> Mo_ has joined #linux-media
<br> jmassot has joined #linux-media
<br> Mo has quit IRC (Ping timeout: 480 seconds)
<br> ten1572377432463050 has quit IRC (Remote host closed the connection)
<br> ten1572377432463050 has joined #linux-media
<br> eelstrebor has joined #linux-media
<br> Mo_ has quit IRC (Quit: Leaving)
<br> mvaittin has quit IRC (Ping timeout: 480 seconds)
<br> mrpops2ko has quit IRC ()
<br> eelstrebor has quit IRC (Ping timeout: 480 seconds)
<br> svarbanov has joined #linux-media
sailus: <u>hverkuil</u>: Regarding the CUR_LINK_FREQ support in mei-csi driver---it needs to be a volatile control as the driver won't have a chance to read the value from upstream sub-device otherwise.
<br> Presumably all other drivers would need it, too.
***: eelstrebor has joined #linux-media
hverkuil: <u>sailus</u>: but it doesn't change continuously, right? I.e. when you start streaming, then presumably the frequency is set and remains fixed. So at that moment you can read it out and set the control.
<br> Volatile is really meant for e.g. getting the current gain (snapshot in time) as set by a hardware/firmware autogain algorithm.
<br> Similar really to a C volatile type: it can change at any time.
***: ao2 has joined #linux-media
<br> abws_ has quit IRC ()
<br> abws has joined #linux-media
<br> svarbanov has quit IRC (Ping timeout: 480 seconds)
<br> sgruszka has quit IRC (Quit: Leaving)
<br> digetx has quit IRC (Ping timeout: 480 seconds)
<br> svarbanov has joined #linux-media
sailus: <u>hverkuil</u>: How will the driver set the value if it won't get an event of some kind? The control framework does provide a way to do this and it's the volatile flag.
***: ao2 has quit IRC (Quit: Leaving)
<br> ten1572377432463050 has quit IRC (Remote host closed the connection)
<br> ten1572377432463050 has joined #linux-media
<br> prime has quit IRC (Ping timeout: 480 seconds)
<br> prime has joined #linux-media
<br> prime is now known as Guest2324
<br> hansg has quit IRC (Quit: Leaving)
<br> ten1572377432463050 has quit IRC (Remote host closed the connection)
<br> ten1572377432463050 has joined #linux-media
<br> eelstrebor has quit IRC (Ping timeout: 480 seconds)
<br> eelstrebor has joined #linux-media
<br> djrscally has quit IRC (Ping timeout: 480 seconds)
<br> BrianG61UK has joined #linux-media
<br> syoung has quit IRC (Read error: Connection reset by peer)
<br> syoung has joined #linux-media
<br> digetx has joined #linux-media