Hi,
la, 2012-10-13 kello 01:00 +0530, Shubhrajyoti Datta kirjoitti:
> On Sat, Oct 13, 2012 at 12:10 AM, Kevin Hilman
> wrote:
> > From: Kevin Hilman
> >
> > Currently, runtime PM is used to keep the device enabled only during
> > active transfers and for a configurable runtime PM autosuspend tim
Hi,
pe, 2012-10-12 kello 14:46 +, Strashko, Grygorii kirjoitti:
> Hi Kevin,
>
> yep, [1] is the same fix - thanks.
>
> Hi Kalle,
>
> i've applied these changes and PM runtime fix on top of
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
> (omap2plus_defconfig)
> Cou
Hi,
On Fri, Oct 12, 2012 at 21:54:52, Tony Lindgren wrote:
> * Russell King - ARM Linux [121012 08:56]:
> > omap-gpmc omap-gpmc: error: clk_get
> > omap-gpmc: probe of omap-gpmc failed with error -2
>
> I think Afzal posted something about this already? Looks
> like this too could be sparse IRQ
gpmc has been converted to a driver. It requests clock with
con-id "fck", if not available, probe fails. Clock for gpmc
device with con-id "fck" is created (aliased) along with
hwmod device, and for that to happen, main_clk needs to be
specified in hwmod entry, add it for OMAP4.
Note that the corr
After commit 846a136881b8f73c1f74250bf6acfaa309cab1f2 ("ARM: vfp: fix
saving d16-d31 vfp registers on v6+ kernels"), the OMAP 2430SDP board
started crashing during boot with omap2plus_defconfig:
[3.875122] mmcblk0: mmc0:e624 SD04G 3.69 GiB
[3.915954] mmcblk0: p1
[4.086639] Internal e
On 15 October 2012 02:58, Paul Walmsley wrote:
>
> Fix by implementing a request from Russell King to add a new HWCAP
> flag that affirmatively indicates the presence of the d16-d31
> registers:
[...]
> diff --git a/arch/arm/include/uapi/asm/hwcap.h
> b/arch/arm/include/uapi/asm/hwcap.h
> index
After commit 846a136881b8f73c1f74250bf6acfaa309cab1f2 ("ARM: vfp: fix
saving d16-d31 vfp registers on v6+ kernels"), the OMAP 2430SDP board
started crashing during boot with omap2plus_defconfig:
[3.875122] mmcblk0: mmc0:e624 SD04G 3.69 GiB
[3.915954] mmcblk0: p1
[4.086639] Internal e
Commit 3b2f8f82dad7d1f79cdc8fc05bd1c94baf109bde ("i2c: omap: switch to
threaded IRQ support") causes communication with I2C devices to fail
after system suspend/resume on all OMAP3 devices:
...
[ 40.228576] PM: noirq resume of devices complete after 3.723 msecs
[ 40.233184] PM: early resume o
On Fri, Oct 12, 2012 at 6:24 PM, Tony Lindgren wrote:
>> Error setting wl12xx data: -38
..
> Ohad, can you please take a look?
Sure, -38 is -ENOSYS which is returned when the wl12xx driver isn't configured.
This isn't an error (it's a user decision, and it shouldn't elicit any
error) and the pat
Add the registers used to configure the CSI-2 receiver PHY on OMAP3430 and
3630 and map them in the ISP driver. The register is part of the control
block but it only is needed by the ISP driver.
Signed-off-by: Sakari Ailus
Acked-by: Tony Lindgren
---
arch/arm/mach-omap2/devices.c | 10
Configure CSI-2 phy based on platform data in the ISP driver. For that, the
new V4L2_CID_IMAGE_SOURCE_PIXEL_RATE control is used. Previously the same
was configured from the board code.
Signed-off-by: Sakari Ailus
Acked-by: Laurent Pinchart
---
drivers/media/platform/omap3isp/isp.h |3
Add PHY routing configuration for both 3430 and 3630. Also add register bit
definitions of CSIRXFE and CAMERA_PHY_CTRL registers on OMAP 3430 and 3630,
respectively.
Signed-off-by: Sakari Ailus
---
drivers/media/platform/omap3isp/ispcsiphy.c | 89 +++
drivers/media/plat
Hi all,
This is an update to an old patchset for CSI-2 configuration for OMAP 3430
and 3630. The patches have been tested on the 3630 only so far, and I don't
plan to test them on 3430 in the near future.
I've made changes according to Laurent's suggestions to the patches, with
the exception of a
13 matches
Mail list logo