All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap <linux-omap@vger.kernel.org>, arm-soc <arm@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] omap soc regression fixes for v5.0-rc cycle
Date: Fri, 15 Feb 2019 13:40:36 +0100	[thread overview]
Message-ID: <CAK8P3a1Me9rDbvv7ZTybnxMP=yUNr+aSRfdGUfevf=tXJfo2kQ@mail.gmail.com> (raw)
In-Reply-To: <pull-1548949376-511005@atomide.com>

On Thu, Jan 31, 2019 at 4:44 PM Tony Lindgren <tony@atomide.com> wrote:
-----
> SoC fixes for omaps for v5.0-rc cycle
>
> This series contains two SoC regression fixes and one uninitialized
> variable fix:
>
> - Fix inverted nirq pin handling for omap5 that started producing
>   warnings with earlier GIC direction checks and took a while to
>   understand and confirm. Basically there are two sys_nirq pins
>   that are bypassing peripheral modules and inverted automatically
>   by the SoC and need to be handled with a custom irq_set_type()
>
> - Recent ti-sysc changes caused a regression to the pwm-omap-dmtimer
>   code where the device tree handling code for timer source clock
>   gets confused. It looks like we can remove that code eventually,
>   but for now we just drop a bogus pm_runtime_irq_safe() for the
>   timers with the related quirks caused by pm_runtime_irq_safe(),
>   and have the standard assigned-clocks and assigned-clock-parents
>   deal with setting the source clock
>
> - Fix potentially uninitialized value for display init code if
>   regmap_read() fails

Pulled into arm/fixes branch, thanks!

     Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap <linux-omap@vger.kernel.org>, arm-soc <arm@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] omap soc regression fixes for v5.0-rc cycle
Date: Fri, 15 Feb 2019 13:40:36 +0100	[thread overview]
Message-ID: <CAK8P3a1Me9rDbvv7ZTybnxMP=yUNr+aSRfdGUfevf=tXJfo2kQ@mail.gmail.com> (raw)
In-Reply-To: <pull-1548949376-511005@atomide.com>

On Thu, Jan 31, 2019 at 4:44 PM Tony Lindgren <tony@atomide.com> wrote:
-----
> SoC fixes for omaps for v5.0-rc cycle
>
> This series contains two SoC regression fixes and one uninitialized
> variable fix:
>
> - Fix inverted nirq pin handling for omap5 that started producing
>   warnings with earlier GIC direction checks and took a while to
>   understand and confirm. Basically there are two sys_nirq pins
>   that are bypassing peripheral modules and inverted automatically
>   by the SoC and need to be handled with a custom irq_set_type()
>
> - Recent ti-sysc changes caused a regression to the pwm-omap-dmtimer
>   code where the device tree handling code for timer source clock
>   gets confused. It looks like we can remove that code eventually,
>   but for now we just drop a bogus pm_runtime_irq_safe() for the
>   timers with the related quirks caused by pm_runtime_irq_safe(),
>   and have the standard assigned-clocks and assigned-clock-parents
>   deal with setting the source clock
>
> - Fix potentially uninitialized value for display init code if
>   regmap_read() fails

Pulled into arm/fixes branch, thanks!

     Arnd

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-02-15 12:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 15:44 [GIT PULL] omap soc regression fixes for v5.0-rc cycle Tony Lindgren
2019-01-31 15:44 ` Tony Lindgren
2019-02-15 12:40 ` Arnd Bergmann [this message]
2019-02-15 12:40   ` Arnd Bergmann

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='CAK8P3a1Me9rDbvv7ZTybnxMP=yUNr+aSRfdGUfevf=tXJfo2kQ@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=arm@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /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.