msm: camera: Fix CCI error timeout issue

CCI error timeout happens in stability testing where more than one
camera is used concurrently for different CCI masters. In that case,
2 threads configures different queues. In rare case, interrupts for
both queues can come at same time. So, the status register should be
checked independently for all bits. Otherwise the function returns
without serivicing if any of the condition check in irq handler
evaluates to TRUE.

Change-Id: Id21615521df7df0c6a7364bd3c73d3d2c1c5ad9a
Signed-off-by: Sreesudhan Ramakrish Ramkumar <srramku@codeaurora.org>
camera_v2: Don't touch CCI if daemon crashed.

If daemon crashes, refrain from writing to the CCI. This is needed
because these writes will not wait in a process crash scenario and can
potentially leave the CCI in a bad state.

Change-Id: I530cf1d0b507a9b9d2bc5889a0c81609d770a14d
Signed-off-by: Ankit Premrajka <ankitp@codeaurora.org>
msm: camera: Reset core when HALT timeout

CCI has 2 queues to perform i2c transaction on 2 independent i2c
bus. During CCI init, both masters are RESET at the same time.
If some i2c transaction fails, following recovery procedure is
performed on that master.
1) Issue HALT
2) Wait for HALT ACK
3) Issue RESET for that MASTER
4) Wait for RESET ACK

If HALT ACK is not received. Hence step 3 and 4 is not performed.
This causes subsequent transaction on that MASTER to fail in special
case - Front camera transaction timeout while back camera is running
in the background. To avoid this, RESET core even though HALT ACK
is not received.

Change-Id: I0f77920ce00de9b8e633eeacaabdf579827f7b08
Signed-off-by: Sreesudhan Ramakrish Ramkumar <srramku@codeaurora.org>

Conflicts:

	drivers/media/platform/msm/camera_v2/sensor/cci/msm_cci.c
arm/dt: msm8974: Change I2C clock for main and sub camera separately

Change I2C clock for main and sub camera separately

Change-Id: Ifdd8d2458f1d47d13bed978e29ffbb23757bf860
Signed-off-by: Vasko Kalanoski <vaskok@codeaurora.org>

Conflicts:

	arch/arm/boot/dts/msm8974-camera.dtsi
msm: camera: Use correct type for function return code

Using an unsigned integer to hold the signed return code
is wrong. So fix it by using the correct type to hold the
return code.

CRs-fixed: 512824
Change-Id: I389732a9af740174b26c8c43946e638a1be0d2a2
Signed-off-by: Seemanta Dutta <seemanta@codeaurora.org>
msm: camera: Implements ISPIF HW reset.

1. Add version and ISPs number properties in DT ISPIF node
  ISPIF driver needs to know HW version of ISPIF module and number of
  ISPs to which it is connected in order to execute proper reset of
  ISPIF module. For this purpose, two optional properties for these
  are added to ISPIF node. Both properties are optional - if not
  present, ISPIF driver will use default values.

2. Resets ISPIF HW
  Force hardware reset during hardware start to ensure
  all the line buffers are cleared. Reset is done once after first
  open of the module. In order to reset module clocks of CSID and ISPs
  connected to it should be enabled.

Change-Id: I6570ea45d1211c66fe5d6e80d1d2faa019415b68
Signed-off-by: Petar Sivenov <psiven@codeaurora.org>

Conflicts:

	drivers/media/platform/msm/camera_v2/ispif/msm_ispif.h
msm: camera: Non-busy polling and timeout when stopping ISPIF.

Previously a busy loop used to wait for ISPIF stop on frame
boundary. This was bad not only for busy polling, but
because if sensor has stopped streaming for some reason, the ISPIF
will never stop thus making the loop endless.
The new solution uses readl_poll_timeout macro, polling once in
millisecond for maximum of 500 milliseconds (which corresponds to
2FPS - minimum supported frame rate). If polling times out, driver
reports the error to the user space for appropriate recovery.

Change-Id: I14e9825e2c8b67bab7a2e13fa0b0ef4710456805
Signed-off-by: Petar Sivenov <psiven@codeaurora.org>
msm: camera: Fix Possible Integer overflow in ispif driver

Fix Possible Integer overflow in ispif driver in multiple places.

CRs-Fixed: 510051
Change-Id: I738c11b2d8e2ef7433bb01ba416590f7952acc2e
Signed-off-by: Lakshmi Narayana Kalavala <lkalaval@codeaurora.org>
msm: camera: ISPIF HW reset is incorrecty invoked

Currently ISPIF HW reset is implemented for msm8974 ISPIF HW module only.
However, the check for module is not correct and reset sequence is executed
for 8226 also, putting HW in bad state. The patch uses correct check
against HW version to prevent that.

Change-Id: Iff9ab2deb7c6c207d9493ce2abe56bad4d9d7f6f
Signed-off-by: Petar Sivenov <psiven@codeaurora.org>
msm: camera: Fix ispif stop frame boundary timeout issue

Previously a 500ms timeout set for stop frame boundary.
But sometimes when doing snapshot with large linecount may make
the frame rate drop to 1fps. Set the timeout to 1s to avoid camera
crash.

Change-Id: Id51fb3eb58300df20e792bdab9702af7c4e18943
Signed-off-by: Ju He <juhe@codeaurora.org>
msm: camera: Enabling all CSI clocks for ISPIF hw reset.

To perform complete ISPIF HW reset need to enable all CSI
clocks. Earlier only csi0 clock was enabled, causing problems
in reseting RDI interface. Also added change to disable clocks
before returning from hw reset if there is a timeout.

Change-Id: Ia0befc058f06596688b9310ee6c8bf4b017a13ce
Signed-off-by: Sagar Gore <csgore@codeaurora.org>
msm-camera: enable csi-ahb-clk while accessing csi phy registers.

Turning on csi_ahb_clk while accessing csi phy registers at boot
time to avoid boot time crashes.

Change-Id: I88474a99141036e5d1adb541545e22bda78dc01c
Signed-off-by: Aditya Jonnalagadda <ajonnala@codeaurora.org>

Conflicts:

	arch/arm/mach-msm/clock-8610.c
	drivers/media/platform/msm/camera_v2/sensor/csiphy/msm_csiphy.c
msm: ispif: Clean up typecasts/format specifiers

Clean up typecasts and format specifiers in msm_ispif.c

Change-Id: I53b8aec6f5a2a5f0271ca2f5cab5de6d72c186c2
Signed-off-by: Seemanta Dutta <seemanta@codeaurora.org>
msm: camera: Fix unterminated of_device_id table

Add a NULL table entry at end for msm, ispif and
msm_generic_buf_mgr device tree match tables.

Change-Id: I05f08c77a8a25112cd17955e98018ac88b7a834c
CRs-Fixed: 582110
Signed-off-by: Hariram Purushothaman <hpurus@codeaurora.org>
msm: camera: Add defensive check in ISPIF driver

In case of error handling, call ispif release only if ispif handle
is valid. In case of mm-qcamara-daemon crash when camera is not open,
these handles are not valid. Hence it leads to kernel crash in ispif
release handler.

Change-Id: Ifb402b6907052594d12fcf9495694e6c5184af1b
Signed-off-by: Sreesudhan Ramakrish Ramkumar <srramku@codeaurora.org>
msm: camera: Add in-sensor mode support for eeprom

Add in-sensor mode calibration support for eeprom.
User are able to write back calibration settings
via ioctrl interface of the sensor.

Change-Id: I5fbfa8967885b683e498fe670a0c36d58d4b44e7
Signed-off-by: Ju He <juhe@codeaurora.org>
msm: camera: Fix various small issues in cci driver

Remove some unused ioctl exposed, Also add
some bound checks for ioctl user params.

Change-Id: Ifdd441fdb25fd20b005c4e4e1ebe4e203f1216ac
CRs-Fixed: 511382
Signed-off-by: Hariram Purushothaman <hpurus@codeaurora.org>

Conflicts:

	drivers/media/platform/msm/camera_v2/sensor/cci/msm_cci.c
msm: camera_v2: CCI release resources in case of timeout

Turn off the CCI clocks and release gpio if reset timeout error is
received in function_msm_cci_init()

Change-Id: Ib4387ce08635e0b4e6458f225bd3013557d6b5fa
Signed-off-by: Evgeniy Borisov <eborisov@codeaurora.org>
msm: camera: solve twice request MCLK GPIO for camera

In 8x26 MTP/QRD design, main/front camera sensor shares
the same MCLK GPIO, the poweron may fails in some cases
Change the process to output a error message for driver
bringup state to make sure other gpio are handled properly.

Change-Id: I48ee01f32ae5d7e02d3efe8578a747f23a6d8a71
Signed-off-by: Su Liu <suliu@codeaurora.org>
msm: camera: Stream on optimization

Remove sleep in msm_csiphy_lane_config().

Change-Id: Ieede0ed325422c4323ffd69ddcbc20a36889c763
Signed-off-by: Evgeniy Borisov <eborisov@codeaurora.org>