>From: Ohad Ben-Cohen [mailto:o...@wizery.com]
>
>This patchset introduces an approach to eliminate the direct calls
>to follow_page and to the low level cache APIs.
>
>The patchset works by caching the page information while memory
>is mapped, and then using that information later when needed
>ins
Thara Gopinath writes:
> From: Thara Gopinath
> Subject: [PATCH 8/8] OMAP3: PM: Adding debug support to Voltage and
> Smartreflex drivers
> To: linux-omap@vger.kernel.org
> Cc: khil...@deeprootsystems.com, p...@pwsan.com, b-cous...@ti.com,
> vishwanath...@ti.com, saw...@ti.com, Thara Go
Kevin Hilman wrote:
> Vishwa,
>
> Can you have someone investigate/debug why using omap3_defconfig on
> 3630/Zoom3 results in no network while using omap_zoom3_defconfig
> seems to work?
>
> In addition, this would also be a good opportunity to get rid of the
> Zoom3-specific defconfig and move t
Gadiyar, Anand wrote:
> We need to wait on the IDLEST bit after the clocks are enabled
> before attempting to access any register.
>
> Currently, the USBTLL i-clock ops uses the clkops_omap2_dflt_wait,
> while the USBTLL f-clock ops uses clkops_omap2_dflt. If the
> i-clock is enabled first, the cl
Thara Gopinath writes:
> This patch adds the smartreflex hwmod data for OMAP3430
> and OMAP3630. A dev_attr is also added to the hwmod
> structure for each smartreflex module which contains
> SoC specific info like the efuse offsets, test n-values
> etc.
>
> Signed-off-by: Thara Gopinath
[...]
"Govindraj.R" writes:
> Avoid using hwmod lookup using name string rather
> retreive port info using the hwmod class interface.
>
> Cc: Kevin Hilman
> Signed-off-by: Govindraj.R
> ---
> arch/arm/mach-omap2/serial.c | 71 ++---
> 1 files changed, 31 inserti
Kevin Hilman writes:
> "Govindraj.R" writes:
>
>> Changes from v1:
>> * Incorporated : OMAP clock: Add uart4_ick/fck definitions for 3630
>> * using omap_mux_request_signal to retreive padconf offset
>> as per Tony's comments.
>> http://marc.info/?l=linux-omap&m=127609369220618&w=2
>> This
Senthil,
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Koen Kooi
> Sent: Monday, May 10, 2010 3:03 AM
> To: Guruswamy, Senthilvadivu
> Cc: linux-omap@vger.kernel.org; linux-fbdev-de...@lists.sourceforge.net;
> t...@a
Kevin Hilman writes:
> In the _setup() hook, check for valid IDLEST fields. If not set, use
> the module defaults since they are the same as the module defaults
> for most hwmods.
>
> Problem found because _wait_target_ready() will fail if IDLEST
> fields are not valid.
>
> Signed-off-by: Kevin
"Anders, David" writes:
>>
>> > The panda isn't 100% compatible with the blaze/sdp. There are/will
>> > be some significant differences. I understand the goal to make the
>> > "multi-boot" images and to reduce the amount of duplicated code in
>> > the kernel, however we can learn a little about
> -Original Message-
> From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
> Sent: Friday, June 18, 2010 10:14 AM
> To: Anders, David
> Cc: linux-omap@vger.kernel.org; t...@atomide.com
> Subject: Re: [PATCH] Add OMAP4 Panda support
>
> [please don't top-post: http://elinux.org/Netiquet
> IIUC, Panda was built to be compatible with the SDP/Blaze, right?
>
> If so, is there any reason we can't support both boards from the same
> board file?
>
> Just add the above MACHINE_START.._END section to board-4430sdp.c to handle
> the both machine IDs, but all the functions could be common
[please don't top-post: http://elinux.org/Netiquette]
"Anders, David" writes:
> The panda isn't 100% compatible with the blaze/sdp. There are/will
> be some significant differences. I understand the goal to make the
> "multi-boot" images and to reduce the amount of duplicated code in
> the kerne
"Kalliguddi, Hema" writes:
> Hi Benoit,
>
> I have 2 cases in usb for the need of separate API for setting the auto idle
> bit.
>
> 1. Below the link for omap3430TRM. Please refer 24.1.5.4.2 and 24.1.5.4.3
> there is note not to set smart
> idle and autoidle bit simultaneously. Suggestion is to
Kevin,
The panda isn't 100% compatible with the blaze/sdp. There are/will be some
significant differences. I understand the goal to make the "multi-boot" images
and to reduce the amount of duplicated code in the kernel, however we can learn
a little about this situation from the BeagleBoard. Du
"Anders, David" writes:
> Add initial support for the OMAP4430 based Panda board.
>
> Signed-off-by: David Anders
> ---
> arch/arm/configs/omap4_panda_defconfig | 1094
>
> arch/arm/mach-omap2/Kconfig|4 +
> arch/arm/mach-omap2/Makefile
DebBarma, Tarun Kanti had written, on 06/18/2010 07:17 AM, the following:
Generation of 1ms granular GPTIMER events using 32KHz or system clocks
as inputs does not have whole number count value to loaded into the register.
This inaccurate count value with respect to 1ms period leads to time drif
On Wed, Jun 16, 2010 at 10:56 AM, Tony Lindgren wrote:
> * Felipe Contreras [100611 19:03]:
>> On Fri, Jun 11, 2010 at 6:07 PM, Laurent Pinchart
>> wrote:
>> > My understanding is that Linus will remove all ARM defconfigs in 2.6.36,
>> > unless someone can convince him not to.
>>
>> Huh? I thoug
Generation of 1ms granular GPTIMER events using 32KHz or system clocks
as inputs does not have whole number count value to loaded into the register.
This inaccurate count value with respect to 1ms period leads to time drift
subsequently. OMAP3 and later silicones have dedicated registers for GPTI
On Fri, Jun 18, 2010 at 11:56:02AM +0200, ext Elvis Dowson wrote:
When adding support for OMAP4 Panda, and adding the necessary bits to
omap3_defconfig, will it be possible to ensure that all OMAP3 devices
also work the same, e.g. Gumstix Overo?
it should be possible. Ideally all omap2/3/4 boa
Hi Felipe,
On Jun 18, 2010, at 10:58 AM, Felipe Balbi wrote:
> should we drop the defconfig, though ? and just add the necessary bits to
> omap3_defconfig ?
When adding support for OMAP4 Panda, and adding the necessary bits to
omap3_defconfig, will it be possible to ensure that all OMAP3 devic
Hi Benoit,
I have 2 cases in usb for the need of separate API for setting the auto idle
bit.
1. Below the link for omap3430TRM. Please refer 24.1.5.4.2 and 24.1.5.4.3 there
is note not to set smart
idle and autoidle bit simultaneously. Suggestion is to set the auto idle 0
before setting smart
* Felipe Balbi [100618 09:55]:
> On Tue, May 18, 2010 at 05:36:36AM +0200, ext Tony Lindgren wrote:
> >Cool, good to see this posted early.
> >
> >However, looks like this can wait until the next merge window
> >though as it was posted so late.
>
> should we drop the defconfig, though ? and just
On Wed, 26 May 2010 10:30:14 +0300
Jarkko Nikula wrote:
> Hi
>
> There are now required sound/soc/ patches in mainline and linux-omap to get
> basic Nokia N900 audio working.
>
> Patch 1/3 is continuation to earlier set, see
>
> http://marc.info/?l=linux-omap&m=127306914008392&w=2
>
> IMO, it
On Tue, May 18, 2010 at 05:36:36AM +0200, ext Tony Lindgren wrote:
Cool, good to see this posted early.
However, looks like this can wait until the next merge window
though as it was posted so late.
should we drop the defconfig, though ? and just add the necessary bits
to omap3_defconfig ?
25 matches
Mail list logo
