Hi Hugues, > Am 22.06.2017 um 17:41 schrieb H. Nikolaus Schaller <hns@xxxxxxxxxxxxx>: > > >> Am 22.06.2017 um 17:05 schrieb Hugues Fruchet <hugues.fruchet@xxxxxx>: >> >> This patchset enables OV9655 camera support. >> >> OV9655 support has been tested using STM32F4DIS-CAM extension board >> plugged on connector P1 of STM32F746G-DISCO board. >> Due to lack of OV9650/52 hardware support, the modified related code >> could not have been checked for non-regression. >> >> First patches upgrade current support of OV9650/52 to prepare then >> introduction of OV9655 variant patch. >> Because of OV9655 register set slightly different from OV9650/9652, >> not all of the driver features are supported (controls). Supported >> resolutions are limited to VGA, QVGA, QQVGA. >> Supported format is limited to RGB565. >> Controls are limited to color bar test pattern for test purpose. >> >> OV9655 initial support is based on a driver written by H. Nikolaus Schaller [1]. > > Great! Thanks again for picking up or work and trying to get it upstream. > > I will test as soon as possible. I have tried and had to fix some issues first: * gpio properties have a different name than in our approach (but that is something maintainers have to decide and is easy to follow this or that way) * there is no clock-frequency property which makes the driver request a clock frequency (something our camera interface expects this way) * there is no vana-supply regulator and we need that to power on/off the camera on demand (reset and pwdn isn't enough in our hardware) * for some unknown reason the driver does not load automatically from DT compatibility string and needs to be explicitly modprobed * unfortunately we still get no image :( The latter is likely a setup issue of our camera interface (OMAP3 ISP = Image Signal Processor) which we were not yet able to solve. Oscilloscoping signals on the interface indicated that signals and sync are correct. But we do not know since mplayer only shows a green screen. Therefore we had not submitted anything upstream ourselves, because our driver setup isn't finished and completely working. I have written some more specific comments linked to proposals for patches as answer to your [PATCH v1 1/6] BR and thanks, Nikolaus
