Grant Likely wrote:
>
> On Tue, Jan 03, 2012 at 01:53:28PM +0530, Thomas Abraham wrote:
> > Hi Sylwester,
> >
> > On 3 January 2012 03:49, Sylwester Nawrocki wrote:
> > > Hi Thomas,
> > >
> > > thank you for clarifying.
> > >
> > > On 01/02/2012 03:14 AM, Thomas Abraham wrote:
> > >>
> > >> The f
On Tue, Jan 03, 2012 at 03:15:05PM +0100, Cousson, Benoit wrote:
> Hi Grant,
>
> On 12/19/2011 3:02 PM, Rob Herring wrote:
> >On 12/05/2011 08:23 AM, Benoit Cousson wrote:
> >>The current implementation just ignore any NULL string inserted in a
> >>multiple strings property.
> >>In some cases we c
On Mon, Dec 05, 2011 at 03:23:56PM +0100, Benoit Cousson wrote:
> In a HW system, resources in general have name to identify them.
> The is the case as well for IORESOURCE_IRQ resources filled by DT
> "interrupts" entries.
> The current DT mechanism is relying on the "interrupts" order to identify
On Tue, Jan 03, 2012 at 01:53:28PM +0530, Thomas Abraham wrote:
> Hi Sylwester,
>
> On 3 January 2012 03:49, Sylwester Nawrocki wrote:
> > Hi Thomas,
> >
> > thank you for clarifying.
> >
> > On 01/02/2012 03:14 AM, Thomas Abraham wrote:
> >>
> >> The following is a snippet from the dts file used
This is an incremental patch updating to the revised bindings for matrix
keyboards.
This includes an optional "linux,fn-keymap" binding that is not yet implemented,
that will be used to specify the Fn-key modifier layout if needed.
New for v2:
* Removed references to "matrix-keyboard-controller"
Hi Stephen,
On Mon, Dec 12, 2011 at 12:23 PM, Stephen Warren wrote:
> Simon Glass wrote at Monday, December 12, 2011 1:19 PM:
>> On Mon, Dec 12, 2011 at 12:04 PM, Stephen Warren wrote:
>> > You may define constants as follows:
>> >
>> > /define/ TWO 2;
>> > /define/ FOUR 4;
>> > /define/ OTHER F
Hi Jon,
On Thu, Dec 22, 2011 at 6:17 AM, Jon Loeliger wrote:
>> Hi Jon,
>>
>> >> Has this been applied? I cannot see it in the repo.
>>
>> Please can you let me know about the status of this patch?
>>
>> Regards,
>> Simon
>
> Simon,
>
> Sorry. Except for a minor "we should test this" comment
> f
On Tuesday, January 03, 2012 02:58:57 PM Olof Johansson wrote:
> On Tue, Jan 3, 2012 at 2:42 PM, Stephen Warren wrote:
> > Olof Johansson wrote at Tuesday, January 03, 2012 3:28 PM:
> >> This includes an optional "linux,fn-keymap" binding that is not yet
> >> implemented, that will be used to spec
On Tue, Jan 3, 2012 at 2:42 PM, Stephen Warren wrote:
> Olof Johansson wrote at Tuesday, January 03, 2012 3:28 PM:
>> This includes an optional "linux,fn-keymap" binding that is not yet
>> implemented,
>> that will be used to specify the Fn-key modifier layout if needed.
>
>> diff --git a/Documen
Olof Johansson wrote at Tuesday, January 03, 2012 3:28 PM:
> This includes an optional "linux,fn-keymap" binding that is not yet
> implemented,
> that will be used to specify the Fn-key modifier layout if needed.
> diff --git a/Documentation/devicetree/bindings/input/tegra-kbc.txt
...
> +Required
Olof Johansson wrote at Tuesday, January 03, 2012 2:37 PM:
> This adds a simple device tree binding for simple key matrix data and
> a helper to fill in the platform data.
>
> The implementation is in a shared file outside if drivers/input/keyboard
> since some drivers in drivers/input/misc might
This includes an optional "linux,fn-keymap" binding that is not yet implemented,
that will be used to specify the Fn-key modifier layout if needed.
Signed-off-by: Olof Johansson
Acked-by: Grant Likely
---
This patch depends on "Input: keyboard - add device tree bindings for
simple key matrixes"
On Monday, January 02, 2012, Thomas Abraham wrote:
> Hi Rafael,
>
> On 29 December 2011 03:47, Rafael J. Wysocki wrote:
> > On Wednesday, December 28, 2011, Thomas Abraham wrote:
> >> Hi Mark, Rafael,
> >
> > Hi,
> >
> >> On 27 December 2011 02:14, Rafael J. Wysocki wrote:
> >> > On Monday, Dece
On Monday, January 02, 2012, Grant Likely wrote:
> On Mon, Dec 26, 2011 at 08:13:19PM +0100, Rafael J. Wysocki wrote:
> > Hi,
> >
> > On Monday, December 12, 2011, Thomas Abraham wrote:
> > > A device node pointer is added to generic pm domain structure to associate
> > > the domain with a node in
This adds a simple device tree binding for simple key matrix data and
a helper to fill in the platform data.
The implementation is in a shared file outside if drivers/input/keyboard
since some drivers in drivers/input/misc might be making use of it
as well.
Changes since v3:
* Dropped compatible
On Mon, Jan 2, 2012 at 12:18 AM, Grant Likely wrote:
> I'd like to see a "tegra," prefix on these custom properties, but otherwise
> the binding looks okay to me. You should also consider a '-ms' suffix on
> the millisecond properties.
Ok, I added "nvidia," prefix for the properties, and pushed
On Tue, Jan 03, 2012 at 01:47:09PM +, Russell King - ARM Linux wrote:
> On Tue, Jan 03, 2012 at 09:25:30PM +0800, Richard Zhao wrote:
> > In latest v6 version, I get clk transition latency from dt property, and get
> > regulator transition latency from regulator API.
> > Could you please help
On Tue, Jan 03, 2012 at 05:06:15PM +, Russell King - ARM Linux wrote:
> On Tue, Jan 03, 2012 at 08:44:32AM -0800, Dmitry Torokhov wrote:
> > On Tue, Jan 03, 2012 at 04:29:30PM +, Russell King - ARM Linux wrote:
> > > On Tue, Jan 03, 2012 at 08:22:21AM -0800, Simon Glass wrote:
> > > > Can t
Olof Johansson wrote at Sunday, January 01, 2012 11:09 PM:
> This adds a simple device tree binding for simple key matrix data and
> a helper to fill in the platform data.
>
> The implementation is in a shared file outside if drivers/input/keyboard
> since some drivers in drivers/input/misc might
On Sun, Jan 1, 2012 at 11:21 PM, Grant Likely wrote:
> On Wed, Dec 28, 2011 at 11:06:02PM -0800, Olof Johansson wrote:
>> On Wed, Dec 28, 2011 at 11:01 PM, Stephen Warren wrote:
>> > Can we deprecate the Samsung format, and only allow it for that Samsung
>> > device (and allow both there), and re
On Tue, Jan 03, 2012 at 08:44:32AM -0800, Dmitry Torokhov wrote:
> On Tue, Jan 03, 2012 at 04:29:30PM +, Russell King - ARM Linux wrote:
> > On Tue, Jan 03, 2012 at 08:22:21AM -0800, Simon Glass wrote:
> > > Can the Linux key codes fit in 8 bits?
> >
> > That depends on your point of view.
> >
On Tue, Jan 3, 2012 at 8:44 AM, Dmitry Torokhov
wrote:
> On Tue, Jan 03, 2012 at 04:29:30PM +, Russell King - ARM Linux wrote:
>> On Tue, Jan 03, 2012 at 08:22:21AM -0800, Simon Glass wrote:
>> > Can the Linux key codes fit in 8 bits?
>>
>> That depends on your point of view.
>>
>> If you hack
On Tue, Jan 03, 2012 at 04:29:30PM +, Russell King - ARM Linux wrote:
> On Tue, Jan 03, 2012 at 08:22:21AM -0800, Simon Glass wrote:
> > Can the Linux key codes fit in 8 bits?
>
> That depends on your point of view.
>
> If you hack on X, then the answer is yes and you ignore the squeels of
>
From: Jean-Christophe PLAGNIOL-VILLARD
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
[nicolas.fe...@atmel.com: modify DT initialization]
Signed-off-by: Nicolas Ferre
---
v2: - no BUG_ON() anymore in case of an "interrupts" property missing
just stop configuring the gpio bank
- revie
On Tue, Jan 03, 2012 at 08:22:21AM -0800, Simon Glass wrote:
> Can the Linux key codes fit in 8 bits?
That depends on your point of view.
If you hack on X, then the answer is yes and you ignore the squeels of
your users when certain key presses get misinterpreted. (The Psion LX
platform, otherwi
On 12/16/2011 11:11 AM, Jamie Iles :
> Hi Nicolas, Jean-Christophe,
>
> This looks pretty good to me, but a couple of minor comments inline.
>
> Jamie
>
> On Thu, Dec 15, 2011 at 08:16:05PM +0100, Nicolas Ferre wrote:
>> From: Jean-Christophe PLAGNIOL-VILLARD
>>
>> Signed-off-by: Jean-Christoph
Hi Olof,
On Tue, Jan 3, 2012 at 7:43 AM, Olof Johansson wrote:
> Hi,
>
> On Mon, Jan 02, 2012 at 10:39:04AM -0800, Simon Glass wrote:
>> > diff --git a/Documentation/devicetree/bindings/input/matrix-keymap.txt
>> > b/Documentation/devicetree/bindings/input/matrix-keymap.txt
>> > new file mode 10
Hi,
On Mon, Jan 02, 2012 at 10:39:04AM -0800, Simon Glass wrote:
> > diff --git a/Documentation/devicetree/bindings/input/matrix-keymap.txt
> > b/Documentation/devicetree/bindings/input/matrix-keymap.txt
> > new file mode 100644
> > index 000..1db8e12
> > --- /dev/null
> > +++ b/Documentation
Hi Grant,
On 12/19/2011 3:02 PM, Rob Herring wrote:
On 12/05/2011 08:23 AM, Benoit Cousson wrote:
The current implementation just ignore any NULL string inserted in a
multiple strings property.
In some cases we can have a property with a fix number of strings but
not necessarily used, like for
On 1/2/2012 10:04 AM, Grant Likely wrote:
> On Thu, Dec 22, 2011 at 03:56:37PM +0100, Benoit Cousson wrote:
>> Add initial device-tree support for twl familly chips.
>> The current version is missing the regulator entries due
>> to the lack of DT regulator bindings for the moment.
>> Only the simpl
On Tue, Jan 03, 2012 at 09:25:30PM +0800, Richard Zhao wrote:
> Hi Russel,
>
> On 3 January 2012 17:06, Russell King - ARM Linux
> wrote:
> > On Mon, Dec 26, 2011 at 09:44:52PM +0800, Richard Zhao wrote:
> >> On Mon, Dec 26, 2011 at 11:10:30AM +, Mark Brown wrote:
> >> > The *call* is there i
Hi Ilya,
On 12/28/11 01:02, Ilya Yanok wrote:
> On 27.12.2011 11:56, Igor Grinberg wrote:
>>> +/*
>>> + * use fake regulator for vdds_dsi as we can't find this pin inside
>>> + * AM3517 datasheet.
>>> + */
>>> +static struct regulator_consumer_supply mt_ventoux_vdds_dsi_supply[] = {
>>> + REGULA
On Mon, Dec 26, 2011 at 09:44:52PM +0800, Richard Zhao wrote:
> On Mon, Dec 26, 2011 at 11:10:30AM +, Mark Brown wrote:
> > The *call* is there in the regulator subsystem, it's just that none of
> > the drivers back it up with an actual implementation yet. Which turns
> > out to be a good thin
Hi Sylwester,
On 3 January 2012 03:49, Sylwester Nawrocki wrote:
> Hi Thomas,
>
> thank you for clarifying.
>
> On 01/02/2012 03:14 AM, Thomas Abraham wrote:
>>
>> The following is a snippet from the dts file used for testing.
>>
>> [...]
>>
>> lcd0:power-domain-lcd0 {
>> compat
34 matches
Mail list logo
