All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Brad Bishop <bradleyb@fuzziesquirrel.com>,
	 ken.th.liu@foxconn.com, john.hc.wang@foxconn.com
Subject: Re: [PATCH linux dev-4.10 v3 0/3] Clean up mach-aspeed/aspeed.c
Date: Tue, 6 Jun 2017 17:07:38 +0930	[thread overview]
Message-ID: <CACPK8XcMEREexL-ODXE8jMCT=V3f8Wcw6Kdzy=hPmmV801UYxA@mail.gmail.com> (raw)
In-Reply-To: <1496650682.8159.26.camel@aj.id.au>

On Mon, Jun 5, 2017 at 5:48 PM, Andrew Jeffery <andrew@aj.id.au> wrote:
> On Fri, 2017-05-05 at 12:12 +0930, Andrew Jeffery wrote:
>> Hi all,
>>
>> Here's v3 of the series cleaning up the board file given functionality we now
>> have in the tree. Between patches acked and applied from v1 and v2, there's
>> only Barreleye left. I've dug into the archives and Cc'ed Ken and John so they
>> can provide feedback if they have availability.
>>
>> A slip of the fingers meant that v2 didn't actually get Cc'ed to the list, so
>> apologies for that. Xo kindly Cc'ed his replies so the acks at least saw the
>> light of day.
>>
>> Again, the controversial patch is the debounce patch for BMC_PWBTN_IN_N, which
>> changes how the GPIO is exposed to userspace (and so needs a corresponding
>> userspace update). I'm hoping Brad can give feedback or start the discussion to
>> coordinate the userspace change.
>>
>> Cheers,
>>
>> Andrew
>>
>
> Joel, I'd like to see at least the first two patches taken. Hopefully
> some of the GPIO work that Brad was involved in can be applied to the
> Barreleye userspace so we can also take the third patch.
>
>> Andrew Jeffery (3):
>>   aspeed: barreleye: Remove unnecessary GPIO configuration
>>   aspeed: barreleye: Passthrough debounce isn't required
>
> Take the above two with some testing.

Those two have been merged into 4.10. They are not part of the kernel
bump I sent today, but will be part of the next.


>>   aspeed: barreleye: Debounce BMC_PWBTN_IN_N through devicetree
>
> Take this one once we we're ready in userspace.

Cool. Is there a ticket open to track that work?

Cheers,

Joel

      reply	other threads:[~2017-06-06  7:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05  2:42 [PATCH linux dev-4.10 v3 0/3] Clean up mach-aspeed/aspeed.c Andrew Jeffery
2017-05-05  2:42 ` [PATCH linux dev-4.10 v3 1/3] aspeed: barreleye: Remove unnecessary GPIO configuration Andrew Jeffery
2017-05-05  2:42 ` [PATCH linux dev-4.10 v3 2/3] aspeed: barreleye: Passthrough debounce isn't required Andrew Jeffery
2017-05-05  2:42 ` [PATCH linux dev-4.10 v3 3/3] aspeed: barreleye: Debounce BMC_PWBTN_IN_N through devicetree Andrew Jeffery
2017-06-05  8:18 ` [PATCH linux dev-4.10 v3 0/3] Clean up mach-aspeed/aspeed.c Andrew Jeffery
2017-06-06  7:37   ` Joel Stanley [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACPK8XcMEREexL-ODXE8jMCT=V3f8Wcw6Kdzy=hPmmV801UYxA@mail.gmail.com' \
    --to=joel@jms.id.au \
    --cc=andrew@aj.id.au \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=john.hc.wang@foxconn.com \
    --cc=ken.th.liu@foxconn.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.