Hi Russell, Javier,
On 02/24/2014 09:22 PM, Javier Martinez Canillas wrote:
> Hi Russell,
>
> On Mon, Feb 24, 2014 at 3:03 PM, Russell King - ARM Linux
> wrote:
>> On Mon, Feb 24, 2014 at 06:07:49PM +0100, Florian Vaussard wrote:
>>> + hdmi0: connector@0 {
>>> + compatible = "hdm
Quoting Nishanth Menon (2014-02-18 12:32:18)
> From: Mike Turquette
>
> This patch provides helper functions for drivers that wish to scale
> voltage through the clock rate-change notifiers. The approach taken
> is that the user-driver(cpufreq/devfreq) do not care about the
> details of the OPP t
On Sun, Feb 23, 2014 at 5:49 PM, Sebastian Reichel wrote:
> Add new method hsi_add_clients_from_dt, which can be used
> to initialize HSI clients from a device tree node.
>
> The patch also documents the DT binding for trivial HSI
> clients.
>
> Signed-off-by: Sebastian Reichel
> ---
> .../devic
Correcting myself from an earlier post..
On 02/24/2014 04:38 PM, Joel Fernandes wrote:
>>> Also with respect to virt_dma (which is used by edma to manage all the
>>> descriptors and lists) there are too many lists: submitted, issued,
>>> completed etc and the descriptor moves from one to the othe
Hi Russell,
Firstly, thanks for your quick reply.
On 02/24/2014 01:21 PM, Russell King - ARM Linux wrote:
> Wrapping... (I've had to manually edit this.)
>
> On Mon, Feb 24, 2014 at 01:03:32PM -0600, Joel Fernandes wrote:
>> Just wanted your thoughts/suggestions on how we can avoid overhead in
>
On Mon, Feb 24, 2014 at 01:03:32PM -0600, Joel Fernandes wrote:
> Hi folks,
>
> Just wanted your thoughts/suggestions on how we can avoid overhead in the EDMA
> dmaengine driver. I am seeing a lots of performance drop specially for small
> transfers with EDMA versus before raw EDMA was moved to DM
Hi Russell,
On Mon, Feb 24, 2014 at 3:03 PM, Russell King - ARM Linux
wrote:
> On Mon, Feb 24, 2014 at 06:07:49PM +0100, Florian Vaussard wrote:
>> + hdmi0: connector@0 {
>> + compatible = "hdmi-connector";
>
> This looks way to generic a compatible string. Are you sure it's
> co
On Mon, Feb 24, 2014 at 09:56:51AM -0600, Nishanth Menon wrote:
> On 02/24/2014 09:51 AM, Mark Rutland wrote:
> > On Sun, Feb 23, 2014 at 11:50:00PM +, Sebastian Reichel wrote:
>
> [...]
> >> +static int omap_ssi_port_runtime_suspend(struct device *dev)
> >> +{
> >> + struct hsi_port *po
Wrapping... (I've had to manually edit this.)
On Mon, Feb 24, 2014 at 01:03:32PM -0600, Joel Fernandes wrote:
> Just wanted your thoughts/suggestions on how we can avoid overhead in
> the EDMA dmaengine driver. I am seeing a lots of performance drop
> specially for small transfers with EDMA versus
Hi folks,
Just wanted your thoughts/suggestions on how we can avoid overhead in the EDMA
dmaengine driver. I am seeing a lots of performance drop specially for small
transfers with EDMA versus before raw EDMA was moved to DMAEngine framework
(atleast 25%).
One of the things I am thinking about is
Here are some basic OMAP test results for Linux v3.14-rc4.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.14-rc4/20140224102552/
Test summary
Build: uImage+dtb:
Pass ( 9/ 9): omap2plus_defconfig_am33xx_only/am335x-bone,
omap2plus_de
Mark, Ohad,
On 02/10/2014 01:27 PM, Suman Anna wrote:
Mark,
On 01/13/2014 06:19 PM, Suman Anna wrote:
Hi,
This is an updated series mainly addressing Mark Rutland's comments
about hwlock specifier being always one-cell. The series adds the
support for #hwlock-cells property and adds a simple
Mark, Kumar, Rob,
On 02/13/2014 07:15 PM, Suman Anna wrote:
From: Florian Vaussard
This patch adds the iommu bindings for all OMAP2+ SoCs. Apart from
the standard bindings used by OMAP peripherals, this patch uses a
'dma-window' (already used by Tegra SMMU) and adds two OMAP custom
bindings -
On Mon, Feb 24, 2014 at 06:07:49PM +0100, Florian Vaussard wrote:
> + hdmi0: connector@0 {
> + compatible = "hdmi-connector";
This looks way to generic a compatible string. Are you sure it's
correct?
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
im
Add the necessary DTS nodes to enable the micro-HDMI output on Parlor
board.
Signed-off-by: Florian Vaussard
---
arch/arm/boot/dts/omap4-duovero-parlor.dts | 36 ++
1 file changed, 36 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-duovero-parlor.dts
b/arch/arm/b
Gumstix DuoVero is an OMAP4430-based Computer On Module.
Parlor is one of the available expansion board.
Tested features:
- GPMC ethernet
- HSUSB2 and OTG
- Audio out
- WiFi and Bluetooth (w2cbw0015 SDIO module)
- LED and button
Signed-off-by: Florian Vaussard
---
.../devicetree/bindings/arm/om
Hi Benoit, Tony,
Here is a device tree to support the OMAP4430-based Gumstix DuoVero
with the Parlor expansion boards. All peripherals should be working
with current 3.14-rc4, except:
- GPMC ethernet (needs patches [1])
- TWL6040 init may fail (will send a bug report to ML)
- The HDMI output depe
Tony,
On 02/21/2014 05:03 PM, Tony Lindgren wrote:
* Nishanth Menon [140220 07:24]:
On 02/19/2014 08:58 PM, Paul Walmsley wrote:
On Wed, 19 Feb 2014, Nishanth Menon wrote:
Paul,
On 02/19/2014 03:22 PM, Paul Walmsley wrote:
[...]
- --
On 02/24/2014 09:51 AM, Mark Rutland wrote:
> On Sun, Feb 23, 2014 at 11:50:00PM +, Sebastian Reichel wrote:
[...]
>> +static int omap_ssi_port_runtime_suspend(struct device *dev)
>> +{
>> + struct hsi_port *port = dev_get_drvdata(dev);
>> + struct omap_ssi_port *omap_port = hsi_po
On Sun, Feb 23, 2014 at 11:50:00PM +, Sebastian Reichel wrote:
> Add OMAP SSI driver to the HSI subsystem.
>
> The Synchronous Serial Interface (SSI) is a legacy version
> of HSI. As in the case of HSI, it is mainly used to connect
> Application engines (APE) with cellular modem engines (CMT)
On Mon, Feb 24, 2014 at 03:21:05PM +0530, Kishon Vijay Abraham I wrote:
> Hi Roger,
>
> On Friday 21 February 2014 05:59 PM, Roger Quadros wrote:
> > On 02/21/2014 02:25 PM, Kishon Vijay Abraham I wrote:
> >> Hi Roger,
> >>
> >> On Wednesday 19 February 2014 06:07 PM, Roger Quadros wrote:
> >>> Hi
On Sat, Feb 22, 2014 at 02:15:25PM +, Russell King - ARM Linux wrote:
> On Fri, Feb 21, 2014 at 09:55:13AM -0600, Felipe Balbi wrote:
> > Here's the error I found:
> >
> > warning: (ARCH_HI3xxx && SOC_OMAP5 && ARCH_SHMOBILE_MULTI) selects
> > HAVE_ARM_TWD which has unmet direct dependencies (
On 02/18/2014 03:36 PM, Balaji T K wrote:
> On Monday 17 February 2014 05:06 PM, Daniel Mack wrote:
>> This should probably be done implicitly through mmc_of_parse(), but that
>> doesn't play well along with the multi-slot model the hsmmc driver
>> features. Hence, for now, do it manually. The prop
On Sun, Feb 23, 2014 at 11:49:58PM +, Sebastian Reichel wrote:
> Add of_match_table to hsi_char driver, so that it can
> be referenced from Device Tree.
>
> Signed-off-by: Sebastian Reichel
> ---
> drivers/hsi/clients/hsi_char.c | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff
On Sun, Feb 23, 2014 at 11:49:56PM +, Sebastian Reichel wrote:
> Add new method hsi_add_clients_from_dt, which can be used
> to initialize HSI clients from a device tree node.
>
> The patch also documents the DT binding for trivial HSI
> clients.
>
> Signed-off-by: Sebastian Reichel
> ---
>
On 02/23/2014 07:58 PM, Mark Brown wrote:
> On Tue, Feb 18, 2014 at 02:32:20PM -0600, Nishanth Menon wrote:
>
>> The current regulator model provides the basic building blocks for the
>> transitions, however SoC drivers specific to each of these devices, be
>> it cpufreq/devfreq have to replicate
Hi,
On Monday 24 February 2014 04:35 PM, Roger Quadros wrote:
> On 02/24/2014 11:51 AM, Kishon Vijay Abraham I wrote:
>> Hi Roger,
>>
>> On Friday 21 February 2014 05:59 PM, Roger Quadros wrote:
>>> On 02/21/2014 02:25 PM, Kishon Vijay Abraham I wrote:
Hi Roger,
On Wednesday 19 Febr
Hi Tony,
On Friday 14 February 2014 02:16 PM, Rajendra Nayak wrote:
> On Friday 14 February 2014 04:49 AM, Tony Lindgren wrote:
>> * Lokesh Vutla [140207 02:24]:
>>> From: Rajendra Nayak
>>>
>>> The SyncTimer in AM43x is clocked using the following two sources:
>>> 1) An inaccuarte 32k clock (CLK
Hi,
On 02/13/2014 07:15 PM, Suman Anna wrote:
> From: Florian Vaussard
>
> This patch adds the iommu bindings for all OMAP2+ SoCs. Apart from
> the standard bindings used by OMAP peripherals, this patch uses a
> 'dma-window' (already used by Tegra SMMU) and adds two OMAP custom
> bindings - 'ti,
On 02/24/2014 11:51 AM, Kishon Vijay Abraham I wrote:
> Hi Roger,
>
> On Friday 21 February 2014 05:59 PM, Roger Quadros wrote:
>> On 02/21/2014 02:25 PM, Kishon Vijay Abraham I wrote:
>>> Hi Roger,
>>>
>>> On Wednesday 19 February 2014 06:07 PM, Roger Quadros wrote:
Hi,
On 02/12/20
Currently INTC interrupts are handled using handle_level_irq which
will acknowledge the interrupt before running the handler. If a second
interrupt is then asserted and this interrupt is disabled while
running the first handler, the INTC will be brought into an
inconsistent state. In this state the
On Friday 21 February 2014 05:59 PM, Roger Quadros wrote:
> On 02/21/2014 02:25 PM, Kishon Vijay Abraham I wrote:
>> Hi Roger,
>>
>> On Wednesday 19 February 2014 06:07 PM, Roger Quadros wrote:
>>> Hi,
>>>
>>> On 02/12/2014 11:46 AM, Kishon Vijay Abraham I wrote:
On Wednesday 29 January 2014 0
Hi Roger,
On Friday 21 February 2014 05:59 PM, Roger Quadros wrote:
> On 02/21/2014 02:25 PM, Kishon Vijay Abraham I wrote:
>> Hi Roger,
>>
>> On Wednesday 19 February 2014 06:07 PM, Roger Quadros wrote:
>>> Hi,
>>>
>>> On 02/12/2014 11:46 AM, Kishon Vijay Abraham I wrote:
On Wednesday 29 Jan
33 matches
Mail list logo
