From: Ferry Toth <fntoth@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Cc: "Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Ferry Toth" <fntoth@gmail.com>
Subject: Re: [PATCH v1 0/3] platform/x86: intel_scu_ipc: Avoid working around IO and cleanups
Date: Thu, 17 Oct 2024 23:10:03 +0200 [thread overview]
Message-ID: <09999c3e-e03b-409a-a8c3-37849fe50878@gmail.com> (raw)
In-Reply-To: <20241016115033.858574-1-andriy.shevchenko@linux.intel.com>
Hi
Op 16-10-2024 om 13:48 schreef Andy Shevchenko:
> The first patch avoids using a workaround for IO (which seems unneeded).
> The rest is a batch of cleanups. Cc'ed to Ferry in hope of testing on
> Intel Merrifield (the main platform that uses these APIs).
>
> Andy Shevchenko (3):
> platform/x86: intel_scu_ipc: Replace workaround by 32-bit IO
> platform/x86: intel_scu_ipc: Simplify code with cleanup helpers
> platform/x86: intel_scu_ipc: Save a copy of the entire struct
> intel_scu_ipc_data
>
> drivers/platform/x86/intel_scu_ipc.c | 142 ++++++++++++---------------
> 1 file changed, 61 insertions(+), 81 deletions(-)
>
Tested iio_info (mrfld_bcove_adc), host/gadget switch, power button.
Tested-by: Ferry Toth <fntoth@gmail.com> (Intel Edison-Arduino)
prev parent reply other threads:[~2024-10-17 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 11:48 Andy Shevchenko
2024-10-16 11:48 ` [PATCH v1 1/3] platform/x86: intel_scu_ipc: Replace workaround by 32-bit IO Andy Shevchenko
2024-10-16 11:48 ` [PATCH v1 2/3] platform/x86: intel_scu_ipc: Simplify code with cleanup helpers Andy Shevchenko
2024-10-21 7:00 ` Mika Westerberg
2024-10-21 8:34 ` Andy Shevchenko
2024-10-16 11:48 ` [PATCH v1 3/3] platform/x86: intel_scu_ipc: Save a copy of the entire struct intel_scu_ipc_data Andy Shevchenko
2024-10-21 7:00 ` Mika Westerberg
2024-10-17 21:10 ` Ferry Toth [this message]
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=09999c3e-e03b-409a-a8c3-37849fe50878@gmail.com \
--to=fntoth@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=platform-driver-x86@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
all inboxes | Powered by JetHome®