linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: Marc Zyngier <maz@kernel.org>, Thomas Gleixner <tglx@linutronix.de>
Cc: John Stultz <john.stultz@linaro.org>, Nishanth Menon <nm@ti.com>,
	Rob Herring <robh@kernel.org>, Suman Anna <s-anna@ti.com>,
	Jason Cooper <jason@lakedaemon.net>,
	<linux-kernel@vger.kernel.org>, <kernel-team@android.com>
Subject: Re: [GIT PULL] irqchip fixes for 5.9, take #1
Date: Mon, 24 Aug 2020 10:15:59 +0530	[thread overview]
Message-ID: <63e87365-7174-4438-6503-7f9895012fb3@ti.com> (raw)
In-Reply-To: <20200818151448.472216-1-maz@kernel.org>

Hi,

On 18/08/20 8:44 pm, Marc Zyngier wrote:
> Hi Thomas,
> 
> As -rc1 is out, here's the first batches of fixes for 5.9. The most
> important one is a fix for a typo that broke modular irqchips using
> the brand new set of macros. Oh hum...
> 
> The rest of it is what I was hinting at when I sent the original 5.9
> pull request, with a bunch of TI updates that deal with the change of
> their firmware interface. The handling of the dependencies was bad
> enough that I couldn't send it before -rc1 was out...
> 
> Please pull,

I see rc2[0] is already tagged. Any reason why this PR is not merged?

[0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/

Thanks and regards,
Lokesh

> 
> 	M.
> 
> The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
> 
>   Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git tags/irqchip-fixes-5.9-1
> 
> for you to fetch changes up to 7828a3ef8646fb2e69ed45616c8453a037ca7867:
> 
>   irqchip: Fix probing deferal when using IRQCHIP_PLATFORM_DRIVER helpers (2020-08-17 08:06:11 +0100)
> 
> ----------------------------------------------------------------
> irqchip fixes for Linux 5.9, take #1
> 
> - Fix an embarassing typo in the new module helpers, leading
>   to the probe failing most of the time
> 
> - The promised TI firmware rework that couldn't make it into
>   the merge window due to a very badly managed set of dependency
> 
> ----------------------------------------------------------------
> Lokesh Vutla (13):
>       firmware: ti_sci: Drop the device id to resource type translation
>       firmware: ti_sci: Drop unused structure ti_sci_rm_type_map
>       firmware: ti_sci: Add support for getting resource with subtype
>       dt-bindings: irqchip: ti, sci-intr: Update bindings to drop the usage of gic as parent
>       dt-bindings: irqchip: Convert ti, sci-intr bindings to yaml
>       irqchip/ti-sci-intr: Add support for INTR being a parent to INTR
>       dt-bindings: irqchip: ti, sci-inta: Update docs to support different parent.
>       dt-bindings: irqchip: Convert ti, sci-inta bindings to yaml
>       irqchip/ti-sci-inta: Do not store TISCI device id in platform device id field
>       irqchip/ti-sci-inta: Add support for INTA directly connecting to GIC
>       arm64: dts: k3-j721e: ti-sci-inta/intr: Update to latest bindings
>       arm64: dts: k3-am65: ti-sci-inta/intr: Update to latest bindings
>       arm64: dts: k3-am65: Update the RM resource types
> 
> Marc Zyngier (1):
>       irqchip: Fix probing deferal when using IRQCHIP_PLATFORM_DRIVER helpers
> 
>  .../bindings/interrupt-controller/ti,sci-inta.txt  |  66 ---------
>  .../bindings/interrupt-controller/ti,sci-inta.yaml |  98 +++++++++++++
>  .../bindings/interrupt-controller/ti,sci-intr.txt  |  82 -----------
>  .../bindings/interrupt-controller/ti,sci-intr.yaml | 102 ++++++++++++++
>  MAINTAINERS                                        |   4 +-
>  arch/arm64/boot/dts/ti/k3-am65-main.dtsi           |  36 +++--
>  arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi            |  12 +-
>  arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi         |   8 +-
>  arch/arm64/boot/dts/ti/k3-am654-base-board.dts     |   4 +-
>  .../boot/dts/ti/k3-j721e-common-proc-board.dts     |  10 +-
>  arch/arm64/boot/dts/ti/k3-j721e-main.dtsi          |  43 +++---
>  arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi    |  12 +-
>  drivers/firmware/ti_sci.c                          | 155 +++++++++------------
>  drivers/irqchip/irq-ti-sci-inta.c                  |  95 ++++++++++---
>  drivers/irqchip/irq-ti-sci-intr.c                  | 152 ++++++++++++--------
>  drivers/irqchip/irqchip.c                          |   2 +-
>  include/linux/soc/ti/ti_sci_protocol.h             |  13 ++
>  17 files changed, 517 insertions(+), 377 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/ti,sci-inta.txt
>  create mode 100644 Documentation/devicetree/bindings/interrupt-controller/ti,sci-inta.yaml
>  delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.txt
>  create mode 100644 Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.yaml
> 

      reply	other threads:[~2020-08-24  4:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18 15:14 [GIT PULL] irqchip fixes for 5.9, take #1 Marc Zyngier
2020-08-24  4:45 ` Lokesh Vutla [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=63e87365-7174-4438-6503-7f9895012fb3@ti.com \
    --to=lokeshvutla@ti.com \
    --cc=jason@lakedaemon.net \
    --cc=john.stultz@linaro.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=s-anna@ti.com \
    --cc=tglx@linutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).