Hi Maxime,
On 10/04/2018 05:04 PM, Maxime Ripard wrote:
> Hi!
>
> On Mon, Oct 01, 2018 at 02:12:31PM +, Hugues FRUCHET wrote:
This is working perfectly fine on my parallel setup and allows me to
well support VGA@30fps (instead 27) and also support XGA(1024x768)@15fps
that I
Hi!
On Mon, Oct 01, 2018 at 02:12:31PM +, Hugues FRUCHET wrote:
> >> This is working perfectly fine on my parallel setup and allows me to
> >> well support VGA@30fps (instead 27) and also support XGA(1024x768)@15fps
> >> that I never seen working before.
> >> So at least for the parallel
Hi Maxime,
On 09/28/2018 06:05 PM, Maxime Ripard wrote:
> Hi Hugues,
>
> On Thu, Sep 27, 2018 at 03:59:04PM +, Hugues FRUCHET wrote:
>> Hi Maxime & all OV5640 stakeholders,
>>
>> I've just pushed a new patchset also related to rate/pixel clock
>> handling [1], based on your V3 great work:
>>
Hi Hugues,
On Thu, Sep 27, 2018 at 03:59:04PM +, Hugues FRUCHET wrote:
> Hi Maxime & all OV5640 stakeholders,
>
> I've just pushed a new patchset also related to rate/pixel clock
> handling [1], based on your V3 great work:
> >media: ov5640: Adjust the clock based on the expected rate
Hi Maxime & all OV5640 stakeholders,
I've just pushed a new patchset also related to rate/pixel clock
handling [1], based on your V3 great work:
>media: ov5640: Adjust the clock based on the expected rate
>media: ov5640: Remove the clocks registers initialization
>media: ov5640:
On Thu, May 17, 2018 at 01:22:07PM +0200, Maxime Ripard wrote:
> Hi,
>
> On Thu, May 17, 2018 at 11:24:04AM +0200, Daniel Mack wrote:
> > Hi,
> >
> > On Thursday, May 17, 2018 10:53 AM, Maxime Ripard wrote:
> > > Here is a "small" series that mostly cleans up the ov5640 driver code,
> > > slowly
Hi,
On Thu, May 17, 2018 at 11:24:04AM +0200, Daniel Mack wrote:
> Hi,
>
> On Thursday, May 17, 2018 10:53 AM, Maxime Ripard wrote:
> > Here is a "small" series that mostly cleans up the ov5640 driver code,
> > slowly getting rid of the big data array for more understandable code
> >
Hi,
On Thursday, May 17, 2018 10:53 AM, Maxime Ripard wrote:
Here is a "small" series that mostly cleans up the ov5640 driver code,
slowly getting rid of the big data array for more understandable code
(hopefully).
The biggest addition would be the clock rate computation at runtime,
instead of
Hi,
Here is a "small" series that mostly cleans up the ov5640 driver code,
slowly getting rid of the big data array for more understandable code
(hopefully).
The biggest addition would be the clock rate computation at runtime,
instead of relying on those arrays to setup the clock tree
properly.
