Add Marvell MMP2 camera host interface.
Signed-off-by: Lubomir Rintel
---
.../bindings/media/marvell,mmp2-ccic.txt | 30 +++
1 file changed, 30 insertions(+)
create mode 100644
Documentation/devicetree/bindings/media/marvell,mmp2-ccic.txt
diff --git a/Documentation/device
The access to REG_CLKCTRL or REG_CTRL1 without the clock enabled hangs
the machine. Enable the clock first.
Signed-off-by: Lubomir Rintel
---
drivers/media/platform/marvell-ccic/mmp-driver.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/media/platform/marvell-ccic
The commit 05fed81625bf ("[media] marvell-ccic: add MIPI support for
marvell-ccic driver") that claimed to add CSI2 turned on C0_EOF_VSYNC for
parallel bus without a very good explanation.
That broke camera on OLPC XO-1.75 which precisely uses a sensor on a
parallel bus. Revert that chunk.
Tested
This accesses the clock registers directly and thus is not too
devicetree friendly. If it's actually needed it needs to be done
differently.
Signed-off-by: Lubomir Rintel
---
.../media/platform/marvell-ccic/mcam-core.c | 6 -
.../media/platform/marvell-ccic/mcam-core.h | 1 -
.../media
The commit 71862f63f351 ("media: ov7670: Add the ov7670_s_power function")
added a s_power function. For some reason it didn't register it with v4l2,
only uses it internally. Fix this now.
Signed-off-by: Lubomir Rintel
---
drivers/media/i2c/ov7670.c | 1 +
1 file changed, 1 insertion(+)
diff --
Hi,
this patch set somewhat modernizes the Marvel MMP2 CCIC driver. Notably,
it ports it from the platform data (which seems unused as the board
support code never made it) to devicetree.
At the core of the rework is the move to asynchronous sensor discovery
and clock management with the standard
This provides more power saving when the sensor is off.
While at that, do the delay on power/clock enable even if the sensor driver
itself doesn't control the GPIOs. This is required for the OLPC XO-1
platform, that lacks the proper power/reset properties in its DT, but
needs the delay after the s
The platform data is actually not used anywhere (along with the CSI
support) and should be safe to remove.
Signed-off-by: Lubomir Rintel
---
.../media/platform/marvell-ccic/mmp-driver.c | 36 ++-
1 file changed, 27 insertions(+), 9 deletions(-)
diff --git a/drivers/media/platfo
Remove structure members and headers that are not actually used. Saves
us from some noise in subsequent cleanup commits.
Signed-off-by: Lubomir Rintel
---
drivers/media/platform/marvell-ccic/mcam-core.c | 1 -
drivers/media/platform/marvell-ccic/mcam-core.h | 3 ---
drivers/media/platform/marv
An instance of a sensor on DT-based MMP2 platform is always going to be
created asynchronously.
Let's move the manual device creation away from the core to the Cafe
driver (used on OLPC XO-1, not present in DT) and set up appropriate
async matches: I2C on Cafe, FWNODE on MMP (OLPC XO-1.75).
Signe
The commit d790b7eda953 ("[media] vb2-dma-sg: move dma_(un)map_sg here")
left dma_desc_nent unset. It previously contained the number of DMA
descriptors as returned from dma_map_sg().
We can now (since the commit referred to above) obtain the same value from
the sg_table and drop dma_desc_nent alt
The sensor needs the MCLK clock running when it's being probed. On
platforms where the sensor is instantiated from a DT (MMP2) it is going
to happen asynchronously.
Therefore, the current modus operandi, where the bridge driver fiddles
with the sensor power and clock itself is not going to fly. As
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Mon Nov 5 05:00:09 CET 2018
media-tree git hash:dafb7f9aef2fd44991ff1691721ff765a23be27b
media_build git
Hello dear
Greetings to you,I am Dr.Kannan, a personal account manager to Late Engr.
Richard Hernandez, who died with his family in the missing Malaysian Air crash
of 2014. His account with us is in intestate with no claim his fixed deposit of
U$D 7 Million.
I have been mandated by the Bank Ma
On Sun, Nov 04, 2018 at 09:57:46PM +0100, Benjamin Valentin wrote:
> The Xbox DVD Remote feels somewhat sluggish, pressing a button
> repeatedly is sometimes interpreted as it being kept pressed down.
>
> It seems like the RC subsystem is doing some incorrect heuristics when
> in fact the data tha
The Xbox DVD Remote feels somewhat sluggish, pressing a button
repeatedly is sometimes interpreted as it being kept pressed down.
It seems like the RC subsystem is doing some incorrect heuristics when
in fact the data that comes from the device is already pretty clean.
When looking at rc_keydown(
Hello Laurent,
Thank you for the review and the comments.
Please modify the subject / description as you see fit.
I will make sure to use the right prefix in future submissions.
Best regards,
Sergey
On Thu, Nov 1, 2018 at 9:10 AM Laurent Pinchart
wrote:
>
> Hi Sergey,
>
> Thank you for the patch
The fwnode_graph_get_next_endpoint() returns an 'endpoint' node pointer
with refcount incremented, and refcount of the passed as a previous
'endpoint' node is decremented.
So when iterating over all nodes using fwnode_graph_get_next_endpoint(),
we don't need to call fwnode_handle_put() for each no
On Thu 2018-10-04 23:29:03, Lubomir Rintel wrote:
> When the "xclk" clock was added, it was made mandatory. This broke the
> driver on an OLPC plaform which doesn't know such clock. Make it
> optional.
>
> Tested on a OLPC XO-1 laptop.
>
> Cc: sta...@vger.kernel.org # 4.11+
> Fixes: 0a024d634cee
syzbot has found a reproducer for the following crash on:
HEAD commit:d2ff0ff2c23f Merge tag 'armsoc-fixes' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1128a44740
kernel config: https://syzkaller.appspot.com/x/.config?x=9384ec
20 matches
Mail list logo
