From: sathyanarayanan kuppuswamy <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sathyanarayanan Kuppuswamy Natarajan <sathyaosid@gmail.com>
Subject: Re: [PATCH 1/1] MAINTAINERS: Add entry for Whiskey Cove PMIC GPIO driver
Date: Fri, 30 Jun 2017 14:08:02 -0700 [thread overview]
Message-ID: <34f4ec54-6647-8b04-4c09-3b2fa16010e9@linux.intel.com> (raw)
In-Reply-To: <CAHp75VeB-0wbw7ti07Otnf4JCpX0iA494GWMb8U_qmv4ArHRCA@mail.gmail.com>
Hi Andy,
On 06/30/2017 01:51 PM, Andy Shevchenko wrote:
> If we are going to rename (which I personally consider as a good
> idea), this should follow it, and not otherwise.
I am having second thoughts about the rename. After going through the
spec documents, I found that there are two main differences between CHT
and BXT PMIC GPIO controllers.
1. BXT variant has 3 GPIO banks where as CHT variant has only 2 GPIO banks.
2. GPIO I/O control register and IRQ register mapping addresses are
different in both BXT and CHT variants.
Given above differences, I think we have a choice to use the current
driver and pass the above data difference to driver via .driver_data or
platform_data. This is a bit messy method because we are not getting the
register address or info about number of gpio banks from BIOS.
Other solution is to rename the existing driver to gpio-bxt-wcove.c and
create a new one for CHT (if required).
Let me know your comments.
--
Sathyanarayanan Kuppuswamy
Linux kernel developer
next prev parent reply other threads:[~2017-06-30 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 19:20 sathyanarayanan.kuppuswamy
2017-06-30 20:51 ` Andy Shevchenko
2017-06-30 21:08 ` sathyanarayanan kuppuswamy [this message]
2017-07-13 12: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=34f4ec54-6647-8b04-4c09-3b2fa16010e9@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sathyaosid@gmail.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 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®