public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: nikita.shubin@maquefel.me
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Hartley Sweeten <hsweeten@visionengravers.com>
Subject: Re: [RFC PATCH 0/3] gpio: ep93xx: convert to multi irqchips
Date: Mon, 28 Dec 2020 18:14:44 +0300	[thread overview]
Message-ID: <115071609167990@mail.yandex.ru> (raw)
In-Reply-To: <CACRpkdZ=QBGZ9G97+2xPRk4PTTSHGHL64bTLZGbz5kFsg-NqWg@mail.gmail.com>

27.12.2020, 16:55, "Linus Walleij" <linus.walleij@linaro.org>:
> Paging Hartley who I think uses this chip.
>
> On Thu, Dec 24, 2020 at 12:22 PM Nikita Shubin
> <nikita.shubin@maquefel.me> wrote:
>
>>  I was lucky enough to became an owner of some splendid piece's of
>>  antiques called ts7250 based on the top of Cirrus Logic EP9302.
>>
>>  I don't know what fate expects this hardware (it's not EOL it's just Not
>>  recommended for new designs) but i wanted to share fixes in ep93xx gpio area.
>>
>>  It seems ep93xx is deadly broken at current state usage of AB gpiochips
>>  interrupts leads to deadlocks coused by irq_unmask/irq_mask recursions.
>>
>>  Port F is not working at all:
>
> Yeah when I converted this gpio driver I did not have access to a hardware
> which made use of port F :(
>
> I used the SIM.One board but they all died on me, then I acquired another
> EP93xx board that I just didn't have time to test.
>
> The long term plan is to convert these boards to use device tree and
> multiplatform. Interested in the job? ;)
>

I had such a thought, but I was stopped by the delusion that no one is using this 
hardware anymore.

Not promising anything right now - but such a job sounds like a real fun.

> Thanks for fixing up the GPIO chip, let's get the patches in shape and
> merge as fixes. Bartosz is handling the fixes right now, I'll try to review too!

I am glad that this work is interesting not only for me. For this, I'm willing to put in 
a little effort to make the proposed changes look decent.

>
> Yours,
> Linus Walleij

  reply	other threads:[~2020-12-28 15:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24 11:22 [RFC PATCH 0/3] gpio: ep93xx: convert to multi irqchips Nikita Shubin
2020-12-24 11:22 ` [RFC PATCH 1/3] " Nikita Shubin
2020-12-26 17:52   ` Andy Shevchenko
2020-12-28 15:05     ` nikita.shubin
2020-12-24 11:22 ` [RFC PATCH 2/3] gpio: ep93xx: drop to_irq binding Nikita Shubin
2020-12-27 21:21   ` Linus Walleij
2021-01-04 14:17     ` Bartosz Golaszewski
2020-12-24 11:22 ` [RFC PATCH 3/3] gpio: ep93xx: specify gpio_irq_chip->first Nikita Shubin
2020-12-27 21:22   ` Linus Walleij
2020-12-26 17:34 ` [RFC PATCH 0/3] gpio: ep93xx: convert to multi irqchips Andy Shevchenko
2020-12-27 14:00   ` Linus Walleij
2020-12-27 13:55 ` Linus Walleij
2020-12-28 15:14   ` nikita.shubin [this message]
2020-12-28 20:41     ` Linus Walleij

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=115071609167990@mail.yandex.ru \
    --to=nikita.shubin@maquefel.me \
    --cc=bgolaszewski@baylibre.com \
    --cc=hsweeten@visionengravers.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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