From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Marcos Del Sol Vives <marcos@orca.pet>,
William Breathitt Gray <wbg@kernel.org>,
linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2] gpio: vortex: add new GPIO device driver
Date: Fri, 11 Jul 2025 15:06:40 +0300 [thread overview]
Message-ID: <aHD-UH2PsnzJrvQ1@black.fi.intel.com> (raw)
In-Reply-To: <CAMRc=MeNo8sBToDu_P7SahMQcW1xGARgOyQdgJBf7LdtvoYduQ@mail.gmail.com>
On Fri, Jul 11, 2025 at 01:56:26PM +0200, Bartosz Golaszewski wrote:
> On Fri, Jul 11, 2025 at 1:43 PM Andy Shevchenko
> <andriy.shevchenko@intel.com> wrote:
> >
> > +Cc: William,
> > who is an expert in embedded industrial x86 platforms and might help with this.
> >
> > Bart, thanks for Cc'ing me. I have tons of questions and comments regarding this.
>
> FYI: I haven't given it a thorough review yet as I wanted to clarify
> the way the driver is registered first so thanks for looking into it.
Here is even more. There are drivers for 0x6030 chipset (rdc321x-southbridge.c),
this one is unclear to what chipset it is. Is it compatible with gpio-rdc321x.c?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-07-11 12:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 9:15 Marcos Del Sol Vives
2025-07-11 10:19 ` Bartosz Golaszewski
2025-07-11 14:24 ` Marcos Del Sol Vives
2025-07-11 15:01 ` Andy Shevchenko
2025-07-11 21:58 ` Marcos Del Sol Vives
2025-07-11 11:43 ` Andy Shevchenko
2025-07-11 11:56 ` Bartosz Golaszewski
2025-07-11 12:06 ` Andy Shevchenko [this message]
2025-07-11 13:52 ` Marcos Del Sol Vives
2025-07-11 14:53 ` Andy Shevchenko
2025-08-19 20:17 ` Marcos Del Sol Vives
2025-08-20 11:34 ` Andy Shevchenko
2025-08-20 12:00 ` William Breathitt Gray
2025-08-21 9:44 ` Andy Shevchenko
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=aHD-UH2PsnzJrvQ1@black.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcos@orca.pet \
--cc=wbg@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
all inboxes | Powered by JetHome®