From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 229F3C43381 for ; Thu, 21 Feb 2019 11:59:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DEEDD2084F for ; Thu, 21 Feb 2019 11:59:48 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="GyCyvZ+7" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727219AbfBUL7q (ORCPT ); Thu, 21 Feb 2019 06:59:46 -0500 Received: from mail-qt1-f193.google.com ([209.85.160.193]:44965 "EHLO mail-qt1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725891AbfBUL7q (ORCPT ); Thu, 21 Feb 2019 06:59:46 -0500 Received: by mail-qt1-f193.google.com with SMTP id d2so5439274qti.11 for ; Thu, 21 Feb 2019 03:59:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LGOw9ywCSvUfCW1qXHASBmsRFCOvpvYbnAMF4vxN9BM=; b=GyCyvZ+7RA+5h5eWa08KbBvOzhXqbxjm8xI2l5cFMeY/WesYU+/TvL6iF42Adbgyt4 Z5heJKf8wwRF6xLJaikSP8xx/dCxyyuV4i8JFVxXWfwcTAD6kK+eatByGswEYDbbuRNh OTzQBhhG0Ke8JjJ98HefIvd+pUH0gsW4FMogK9B6IBIKo+9HMIV4Tkcwbs4xarF3XvV/ /GrRxxd/OLgYYHcgFqBMuwWtGCfa3ugkQdkmvU4XSGWEEzp3BTEhWJG/v6kyM1Jtw+JA UzoTs0hY/ZkTsu1boQ9P7n2JvSj1V3xF2hr1NoGTItoI2D8Lu85GHdlonszxUP8jADno 4zsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LGOw9ywCSvUfCW1qXHASBmsRFCOvpvYbnAMF4vxN9BM=; b=RRfUoVt1KOtPJedz6yJPaEP8YMXJa2VL0oE0iHf7A3Y0D5DP/DIdYjvjKRCoRVLt22 CcnR4PyRpQRzxG7jnLgtBXNmanS6S06VVNP8IWU6WTq2b6ucxh9ge9sAz4Me61wL0vki 0iDmsZYODFBWq/JE7A3Us1nWhztPOcUz0MXyYm2D9GrNzkvfiZw+J+mjKz6sSSnbYJl2 q1ek8VqXK0VWBzNwuqo7S1YNxTnRXV1H0u2o+ROeRQzLWguGk0TnBuKGa2ObZ6+twP8i NF27L5oqvq0CsvuyxflYaSg2N2Lj3qFKdI59LjGsN9fFvfmN/dy3SuzUexOedSJEAr1R ewvg== X-Gm-Message-State: AHQUAuZhnHN8YPFf1mtGD65kq9oPA52p2LjUpmlaOIwnHQeY9xmUxUGl AqsKjq0Vh/FXJpfqx0oPyslXiwLQKhND+T4coSmAGg== X-Google-Smtp-Source: AHgI3IawX7wKB8wlzuG+pwwlVbA4kzQJb8+K1gtZWLYAo6PN+49Pxl7FZigIHGx+j2KT1tLioTI3GKWk1ffJGRbkQR4= X-Received: by 2002:ac8:26a7:: with SMTP id 36mr31988988qto.234.1550750385416; Thu, 21 Feb 2019 03:59:45 -0800 (PST) MIME-Version: 1.0 References: <20190208021631.30252-1-masneyb@onstation.org> In-Reply-To: <20190208021631.30252-1-masneyb@onstation.org> From: Linus Walleij Date: Thu, 21 Feb 2019 12:59:31 +0100 Message-ID: Subject: Re: [PATCH v2 00/11] qcom: ssbi-gpio: add support for hierarchical IRQ chip To: Brian Masney Cc: Stephen Boyd , Bjorn Andersson , Andy Gross , Marc Zyngier , Lee Jones , Thomas Gleixner , Shawn Guo , Doug Anderson , "open list:GPIO SUBSYSTEM" , Nicolas Dechesne , Niklas Cassel , David Brown , Rob Herring , Mark Rutland , "thierry.reding@gmail.com" , linux-arm-msm@vger.kernel.org, "linux-kernel@vger.kernel.org" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 8, 2019 at 3:16 AM Brian Masney wrote: > This patch series adds hierarchical IRQ chip support to ssbi-gpio so > that device tree consumers can request an IRQ directly from the GPIO > block rather than having to request an IRQ from the underlying PMIC. I have merged this series (+ associated fix) for the v5.1 merge window. If some disagrees you can shout now. Yours, Linus Walleij