Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1503615 > unrolled thread

Re: [PATCH 0/5] ACPI / gpio: Updates to properties

Started byMika Westerberg <mika.westerberg@linux.intel.com>
First post2016-10-19 16:20 +0200
Last post2016-10-20 14:40 +0200
Articles 5 — 3 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH 0/5] ACPI / gpio: Updates to properties Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-10-19 16:20 +0200
    Re: [PATCH 0/5] ACPI / gpio: Updates to properties "Rafael J. Wysocki" <rafael@kernel.org> - 2016-10-19 23:30 +0200
      Re: [PATCH 0/5] ACPI / gpio: Updates to properties Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-10-20 10:00 +0200
      Re: [PATCH 0/5] ACPI / gpio: Updates to properties Linus Walleij <linus.walleij@linaro.org> - 2016-10-20 14:20 +0200
        Re: [PATCH 0/5] ACPI / gpio: Updates to properties Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-10-20 14:40 +0200

#1503615 — Re: [PATCH 0/5] ACPI / gpio: Updates to properties

FromMika Westerberg <mika.westerberg@linux.intel.com>
Date2016-10-19 16:20 +0200
SubjectRe: [PATCH 0/5] ACPI / gpio: Updates to properties
Message-ID<stZSO-2nd-73@gated-at.bofh.it>
On Fri, Sep 23, 2016 at 05:57:05PM +0300, Mika Westerberg wrote:
> Hi,
> 
> This series brings couple of useful GPIO related properties from Device
> Tree to ACPI _DSD device properties:
> 
>   - Names for GPIO lines
>   - GPIO hogging
>   - Holes in GPIO property lists
> 
> We are using these to get Intel Galileo better supported in the mainline
> kernel (but these may be useful for other boards as well). For example SPI
> chip select on Galileo is connected to a GPIO line so we need to be able to
> describe it in ACPI, and at the same time allow native chip selects.
> 
> GPIO hogging can be used to set initial state of certain GPIOs available on
> the headers regardless of the BIOS settings (which may be wrong as it knows
> nothing about which devices have been connected).
> 
> Mika Westerberg (5):
>   ACPI / documentation: Use recommended name in GPIO property names
>   ACPI / gpio: Add support for naming GPIOs
>   ACPI / gpio: Add hogging support
>   ACPI / property: Allow holes in reference properties
>   ACPI / gpio: Allow holes in list of GPIOs for a device

Any comments on the GPIO patches in this series?

At least the last one does not add any new bindings so it should be fine
to apply.

[toc] | [next] | [standalone]


#1504348

From"Rafael J. Wysocki" <rafael@kernel.org>
Date2016-10-19 23:30 +0200
Message-ID<su6AW-6Om-9@gated-at.bofh.it>
In reply to#1503615
On Wed, Oct 19, 2016 at 2:41 PM, Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
> On Fri, Sep 23, 2016 at 05:57:05PM +0300, Mika Westerberg wrote:
>> Hi,
>>
>> This series brings couple of useful GPIO related properties from Device
>> Tree to ACPI _DSD device properties:
>>
>>   - Names for GPIO lines
>>   - GPIO hogging
>>   - Holes in GPIO property lists
>>
>> We are using these to get Intel Galileo better supported in the mainline
>> kernel (but these may be useful for other boards as well). For example SPI
>> chip select on Galileo is connected to a GPIO line so we need to be able to
>> describe it in ACPI, and at the same time allow native chip selects.
>>
>> GPIO hogging can be used to set initial state of certain GPIOs available on
>> the headers regardless of the BIOS settings (which may be wrong as it knows
>> nothing about which devices have been connected).
>>
>> Mika Westerberg (5):
>>   ACPI / documentation: Use recommended name in GPIO property names
>>   ACPI / gpio: Add support for naming GPIOs
>>   ACPI / gpio: Add hogging support
>>   ACPI / property: Allow holes in reference properties
>>   ACPI / gpio: Allow holes in list of GPIOs for a device
>
> Any comments on the GPIO patches in this series?
>
> At least the last one does not add any new bindings so it should be fine
> to apply.

I have no comments, but I'd suggest resending them as a new series on
top of 4.9-rc1 (which includes the generic patches from this series).

You can add my ACK to them if that helps.

Thanks,
Rafael

[toc] | [prev] | [next] | [standalone]


#1504601

FromMika Westerberg <mika.westerberg@linux.intel.com>
Date2016-10-20 10:00 +0200
Message-ID<sugqB-4Bq-15@gated-at.bofh.it>
In reply to#1504348
On Wed, Oct 19, 2016 at 11:22:03PM +0200, Rafael J. Wysocki wrote:
> On Wed, Oct 19, 2016 at 2:41 PM, Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
> > On Fri, Sep 23, 2016 at 05:57:05PM +0300, Mika Westerberg wrote:
> >> Hi,
> >>
> >> This series brings couple of useful GPIO related properties from Device
> >> Tree to ACPI _DSD device properties:
> >>
> >>   - Names for GPIO lines
> >>   - GPIO hogging
> >>   - Holes in GPIO property lists
> >>
> >> We are using these to get Intel Galileo better supported in the mainline
> >> kernel (but these may be useful for other boards as well). For example SPI
> >> chip select on Galileo is connected to a GPIO line so we need to be able to
> >> describe it in ACPI, and at the same time allow native chip selects.
> >>
> >> GPIO hogging can be used to set initial state of certain GPIOs available on
> >> the headers regardless of the BIOS settings (which may be wrong as it knows
> >> nothing about which devices have been connected).
> >>
> >> Mika Westerberg (5):
> >>   ACPI / documentation: Use recommended name in GPIO property names
> >>   ACPI / gpio: Add support for naming GPIOs
> >>   ACPI / gpio: Add hogging support
> >>   ACPI / property: Allow holes in reference properties
> >>   ACPI / gpio: Allow holes in list of GPIOs for a device
> >
> > Any comments on the GPIO patches in this series?
> >
> > At least the last one does not add any new bindings so it should be fine
> > to apply.
> 
> I have no comments, but I'd suggest resending them as a new series on
> top of 4.9-rc1 (which includes the generic patches from this series).
> 
> You can add my ACK to them if that helps.

OK, I will do that. Thanks!

[toc] | [prev] | [next] | [standalone]


#1504825

FromLinus Walleij <linus.walleij@linaro.org>
Date2016-10-20 14:20 +0200
Message-ID<sukue-7se-39@gated-at.bofh.it>
In reply to#1504348
On Wed, Oct 19, 2016 at 11:22 PM, Rafael J. Wysocki <rafael@kernel.org> wrote:
> On Wed, Oct 19, 2016 at 2:41 PM, Mika Westerberg

>> Any comments on the GPIO patches in this series?
>>
>> At least the last one does not add any new bindings so it should be fine
>> to apply.
>
> I have no comments, but I'd suggest resending them as a new series on
> top of 4.9-rc1 (which includes the generic patches from this series).
>
> You can add my ACK to them if that helps.

OK I had some comments so please adress these but resend on top
of v4.9-rc1 indeed. If they are already higher up in my mailbox then
look into my comments and post again, hehe.

Thanks!

Yours,
Linus Walleij

[toc] | [prev] | [next] | [standalone]


#1504854

FromMika Westerberg <mika.westerberg@linux.intel.com>
Date2016-10-20 14:40 +0200
Message-ID<sukNA-7z7-31@gated-at.bofh.it>
In reply to#1504825
On Thu, Oct 20, 2016 at 02:17:40PM +0200, Linus Walleij wrote:
> On Wed, Oct 19, 2016 at 11:22 PM, Rafael J. Wysocki <rafael@kernel.org> wrote:
> > On Wed, Oct 19, 2016 at 2:41 PM, Mika Westerberg
> 
> >> Any comments on the GPIO patches in this series?
> >>
> >> At least the last one does not add any new bindings so it should be fine
> >> to apply.
> >
> > I have no comments, but I'd suggest resending them as a new series on
> > top of 4.9-rc1 (which includes the generic patches from this series).
> >
> > You can add my ACK to them if that helps.
> 
> OK I had some comments so please adress these but resend on top
> of v4.9-rc1 indeed. If they are already higher up in my mailbox then
> look into my comments and post again, hehe.

I will, thanks!

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web