Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [PATCH] media: atmel: atmel-isc: reworked driver and formats
To:     Ken Sloat <KSloat@aampglobal.com>,
        "Eugen.Hristev@microchip.com" <Eugen.Hristev@microchip.com>,
        "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "mchehab@kernel.org" <mchehab@kernel.org>,
        "Nicolas.Ferre@microchip.com" <Nicolas.Ferre@microchip.com>,
        "sakari.ailus@iki.fi" <sakari.ailus@iki.fi>
References: <1550219467-9532-1-git-send-email-eugen.hristev@microchip.com>
 <BL0PR07MB4115ECEE3BED0B46C342F4A9AD630@BL0PR07MB4115.namprd07.prod.outlook.com>
From:   Hans Verkuil <hverkuil@xs4all.nl>
Message-ID: <805728da-29ac-bf4b-ad61-95bc71036e23@xs4all.nl>
Date:   Mon, 11 Mar 2019 15:25:32 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <BL0PR07MB4115ECEE3BED0B46C342F4A9AD630@BL0PR07MB4115.namprd07.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi Ken,

On 2/18/19 2:37 PM, Ken Sloat wrote:
>> -----Original Message-----
>> From: Eugen.Hristev@microchip.com <Eugen.Hristev@microchip.com>
>> Sent: Friday, February 15, 2019 3:38 AM
>> To: linux-media@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux-
>> kernel@vger.kernel.org; mchehab@kernel.org;
>> Nicolas.Ferre@microchip.com; Ken Sloat <KSloat@aampglobal.com>;
>> sakari.ailus@iki.fi; hverkuil@xs4all.nl
>> Cc: Eugen.Hristev@microchip.com
>> Subject: [PATCH] media: atmel: atmel-isc: reworked driver and formats
>>
>> From: Eugen Hristev <eugen.hristev@microchip.com>
>>
>> This change is a redesign in the formats and the way the ISC is configured
>> w.r.t. sensor format and the output format from the ISC.
>> I have changed the splitting between sensor output (which is also ISC input)
>> and ISC output.
>> The sensor format represents the way the sensor is configured, and what ISC
>> is receiving.
>> The format configuration represents the way ISC is interpreting the data and
>> formatting the output to the subsystem.
>> Now it's much easier to figure out what is the ISC configuration for input, and
>> what is the configuration for output.
>> The non-raw format can be obtained directly from sensor or it can be done
>> inside the ISC. The controller format list will include a configuration for each
>> format.
>> The old supported formats are still in place, if we want to dump the sensor
>> format directly to the output, the try format routine will detect and configure
>> the pipeline accordingly.
>> This also fixes the previous issues when the raw format was NULL which
>> resulted in many crashes for sensors which did not have the expected/tested
>> formats.
>>
>> Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
>> ---
>> Hello Ken and possibly others using ISC driver,
>>
>> I would appreciate if you could test this patch with your sensor, because I do
>> not wish to break anything in your setups.
>> Feedback is appreciated if any errors appear, so I can fix them.
>> I tested with ov5640, ov7670, ov7740(only in 4.19 because on latest it's
>> broken for me...) Rebased this patch on top of mediatree.git/master Thanks!
>>
>> Eugen
>>
> Hi Eugen,
> 
> No problem I will try to test sometime this week on my setup. I appreciate you keeping me in the loop.

Were you able to test this patch? And if not, when do you think you can
test this? I think it would be good to test this before committing it
since it is a major change.

Regards,

	Hans