linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-xtensa@linux-xtensa.org,
	Chris Zankel <chris@zankel.net>,
	Max Filippov <jcmvbkbc@gmail.com>
Subject: [PULL 0/9] xtensa fixes for v5.0-rc5
Date: Fri,  1 Feb 2019 11:40:47 -0800	[thread overview]
Message-ID: <20190201194047.13667-1-jcmvbkbc@gmail.com> (raw)

Hi Linus,

please pull the following batch of fixes for the Xtensa architecture.

The following changes since commit 49a57857aeea06ca831043acbb0fa5e0f50602fd:

  Linux 5.0-rc3 (2019-01-21 13:14:44 +1300)

are available in the git repository at:

  git://github.com/jcmvbkbc/linux-xtensa.git tags/xtensa-20190201

for you to fetch changes up to 25384ce5f9530def39421597b1457d9462df6455:

  xtensa: SMP: limit number of possible CPUs by NR_CPUS (2019-01-27 10:04:30 -0800)

----------------------------------------------------------------
xtensa fixes for v5.0-rc5

- fix ccount_timer_shutdown for secondary CPUs;
- fix secondary CPU initialization;
- fix secondary CPU reset vector clash with double exception vector;
- fix present CPUs when booting with 'maxcpus' parameter;
- limit possible CPUs by configured NR_CPUS;
- issue a warning if xtensa PIC is asked to retrigger anything other
  than software IRQ;
- fix masking/unmasking of the first two IRQs on xtensa MX PIC;
- fix typo in Kconfig description for user space unaligned access
  feature;
- fix Kconfig warning for selecting BUILTIN_DTB.

----------------------------------------------------------------
Corentin Labbe (2):
      xtensa: Fix typo use space=>user space
      xtensa: rename BUILTIN_DTB to BUILTIN_DTB_SOURCE

Max Filippov (7):
      xtensa: SMP: fix ccount_timer_shutdown
      xtensa: SMP: fix secondary CPU initialization
      xtensa: smp_lx200_defconfig: fix vectors clash
      xtensa: SMP: mark each possible CPU as present
      drivers/irqchip: xtensa: add warning to irq_retrigger
      drivers/irqchip: xtensa-mx: fix mask and unmask
      xtensa: SMP: limit number of possible CPUs by NR_CPUS

 arch/xtensa/Kconfig                         |  4 +--
 arch/xtensa/boot/dts/Makefile               |  6 ++---
 arch/xtensa/configs/audio_kc705_defconfig   |  2 +-
 arch/xtensa/configs/cadence_csp_defconfig   |  2 +-
 arch/xtensa/configs/generic_kc705_defconfig |  2 +-
 arch/xtensa/configs/nommu_kc705_defconfig   |  2 +-
 arch/xtensa/configs/smp_lx200_defconfig     |  3 ++-
 arch/xtensa/kernel/head.S                   |  5 +++-
 arch/xtensa/kernel/smp.c                    | 41 +++++++++++++++++++----------
 arch/xtensa/kernel/time.c                   |  2 +-
 drivers/irqchip/irq-xtensa-mx.c             | 40 +++++++++++++++++-----------
 drivers/irqchip/irq-xtensa-pic.c            |  6 ++++-
 12 files changed, 73 insertions(+), 42 deletions(-)

-- 
Thanks.
-- Max

             reply	other threads:[~2019-02-01 19:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01 19:40 Max Filippov [this message]
2019-02-02  1:00 ` [PULL 0/9] xtensa fixes for v5.0-rc5 pr-tracker-bot

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=20190201194047.13667-1-jcmvbkbc@gmail.com \
    --to=jcmvbkbc@gmail.com \
    --cc=chris@zankel.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=torvalds@linux-foundation.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 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).