From: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
To: Lee Jones <lee.jones@linaro.org>,
Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Support Opensource <Support.Opensource@diasemi.com>
Subject: RE: [RESEND v2 PATCH 2/2] mfd: da9063: Add support for latest DA silicon revision
Date: Thu, 16 Apr 2020 09:06:10 +0000 [thread overview]
Message-ID: <AM6PR10MB22636366A37AD47ECEB30B7580D80@AM6PR10MB2263.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20200416080631.GV2167633@dell>
On 16 April 2020 09:07, Lee Jones wrote:
> On Mon, 06 Apr 2020, Adam Thomson wrote:
>
> > This update adds new regmap tables to support the latest DA silicon
> > which will automatically be selected based on the chip and variant
> > information read from the device.
> >
> > Signed-off-by: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
> > Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
> > ---
> > drivers/mfd/da9063-i2c.c | 91
> ++++++++++++++++++++++++++++++++++++-----
> > include/linux/mfd/da9063/core.h | 1 +
> > 2 files changed, 82 insertions(+), 10 deletions(-)
>
> Can this patch be applied on its own?
Sadly not. Relies on a new switch statement added by the first patch.
prev parent reply other threads:[~2020-04-16 9:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 8:54 [RESEND PATCH v2 0/2] Resolve revision handling and add support for DA silicon Adam Thomson
2020-04-06 8:54 ` [RESEND PATCH v2 1/2] mfd: da9063: Fix revision handling to correctly select reg tables Adam Thomson
2020-04-16 7:59 ` Lee Jones
2020-04-16 9:04 ` Adam Thomson
2020-04-17 9:24 ` Lee Jones
2020-04-17 9:51 ` Adam Thomson
2020-04-20 7:31 ` Lee Jones
2020-04-20 8:14 ` Adam Thomson
2020-04-06 8:54 ` [RESEND v2 PATCH 2/2] mfd: da9063: Add support for latest DA silicon revision Adam Thomson
2020-04-16 8:06 ` Lee Jones
2020-04-16 9:06 ` Adam Thomson [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=AM6PR10MB22636366A37AD47ECEB30B7580D80@AM6PR10MB2263.EURPRD10.PROD.OUTLOOK.COM \
--to=adam.thomson.opensource@diasemi.com \
--cc=Support.Opensource@diasemi.com \
--cc=lee.jones@linaro.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;
as well as URLs for NNTP newsgroup(s).