All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: kernel test robot <lkp@intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Andy Shevchenko <andy@kernel.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-gpio@vger.kernel.org
Subject: Re: [PATCH v3] pinctrl: baytrail: Clear direct_irq_en flag on broken configs
Date: Wed, 12 Jan 2022 23:01:45 +0200	[thread overview]
Message-ID: <Yd9BuYQw8nhx+Dal@smile.fi.intel.com> (raw)
In-Reply-To: <1fb6eb89-7c87-b30e-0ebe-911ce7dcf881@redhat.com>

On Wed, Jan 12, 2022 at 09:50:47PM +0100, Hans de Goede wrote:
> On 1/12/22 21:44, Andy Shevchenko wrote:

...

> I think you will find v4 interesting because I've done a detailed
> analysis of how the pinctrl conf0 pad register trigger bits and the IO-APIC
> trigger bits work together, which is quite enlightening to how this all
> works (and AFAICT not documented).

With excitement looking forward to it!

-- 
With Best Regards,
Andy Shevchenko



WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v3] pinctrl: baytrail: Clear direct_irq_en flag on broken configs
Date: Wed, 12 Jan 2022 23:01:45 +0200	[thread overview]
Message-ID: <Yd9BuYQw8nhx+Dal@smile.fi.intel.com> (raw)
In-Reply-To: <1fb6eb89-7c87-b30e-0ebe-911ce7dcf881@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 466 bytes --]

On Wed, Jan 12, 2022 at 09:50:47PM +0100, Hans de Goede wrote:
> On 1/12/22 21:44, Andy Shevchenko wrote:

...

> I think you will find v4 interesting because I've done a detailed
> analysis of how the pinctrl conf0 pad register trigger bits and the IO-APIC
> trigger bits work together, which is quite enlightening to how this all
> works (and AFAICT not documented).

With excitement looking forward to it!

-- 
With Best Regards,
Andy Shevchenko


  reply	other threads:[~2022-01-12 21:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 23:44 [PATCH v3] pinctrl: baytrail: Clear direct_irq_en flag on broken configs Hans de Goede
     [not found] ` <CAHp75Vfgpm7sROw_Ay8+tK0bhu-kCbS=O_kwax+i_vaH7H4wXA@mail.gmail.com>
2022-01-08  9:59   ` [PATCH] " Hans de Goede
2022-01-12 20:20     ` Hans de Goede
2022-01-12 20:42       ` Andy Shevchenko
2022-01-12 20:45         ` Hans de Goede
2022-01-08 18:54 ` [PATCH v3] " kernel test robot
2022-01-08 18:54   ` kernel test robot
2022-01-12 19:58   ` Hans de Goede
2022-01-12 19:58     ` Hans de Goede
2022-01-12 20:44     ` Andy Shevchenko
2022-01-12 20:44       ` Andy Shevchenko
2022-01-12 20:50       ` Hans de Goede
2022-01-12 20:50         ` Hans de Goede
2022-01-12 21:01         ` Andy Shevchenko [this message]
2022-01-12 21:01           ` Andy Shevchenko
2022-01-08 18:54 ` kernel test robot
2022-01-08 18:54   ` kernel test robot

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=Yd9BuYQw8nhx+Dal@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=hdegoede@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=mika.westerberg@linux.intel.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.