From: sathya <sathyaosid@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: "x86@kernel.org" <x86@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Zha Qipeng <qipeng.zha@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"dvhart@infradead.org" <dvhart@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Shevchenko <andy@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>
Subject: Re: [RFC v1 4/6] platform: x86: Add generic Intel IPC driver
Date: Mon, 21 Aug 2017 22:09:43 -0700 [thread overview]
Message-ID: <a6c43a40-9c47-330c-975c-cb60e63793a4@gmail.com> (raw)
In-Reply-To: <CAHp75VftGZRoT6aFMD8Mi1GQ=846gwSWTsE-HU00+ijuTtgo4g@mail.gmail.com>
Hi Andy,
On 08/18/2017 05:38 AM, Andy Shevchenko wrote:
> On Tue, Aug 1, 2017 at 9:13 PM,
> <sathyanarayanan.kuppuswamy@linux.intel.com> wrote:
>> From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
>>
>> Currently intel_scu_ipc.c, intel_pmc_ipc.c and intel_punit_ipc.c
>> redundantly implements the same IPC features and has lot of code
>> duplication between them. This driver addresses this issue by grouping
>> the common IPC functionalities under the same driver.
>>
>> Signed-off-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
>> ---
>> arch/x86/include/asm/intel_ipc_dev.h | 148 ++++++++++++
> No, it should go under include/linux/platform_data/x86/
>
>> +/*
>> + * intel_ipc_dev.h: IPC class device header file
> No file names in the top of files.
>
>> + *
>> + * (C) Copyright 2017 Intel Corporation
>> + *
>> + * This program is free software; you can redistribute it and/or
>> + * modify it under the terms of the GNU General Public License
>> + * as published by the Free Software Foundation; version 2
>> + * of the License.
>> + *
>> + */
>> +struct intel_ipc_dev_cfg {
>> + void __iomem *base;
>> + void __iomem *wrbuf_reg;
>> + void __iomem *rbuf_reg;
>> + void __iomem *sptr_reg;
>> + void __iomem *dptr_reg;
>> + void __iomem *status_reg;
>> + void __iomem *cmd_reg;
> No, you have to switch to regmap instead.
Do you want me to register regmap in intel_pmc_ipc.c and pass this
regmap pointer to devm_intel_ipc_dev_create()
instead of regular mem address ? Please correct me if my understanding
is incorrect.
But I don't understand how this change will improve the design.
>
>> + int mode;
>> + int irq;
>> + int irqflags;
>> + int chan_type;
>> + bool use_msi;
>> +};
>
-
Sathya
next prev parent reply other threads:[~2017-08-22 5:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 18:13 [RFC v1 0/6] PMC/PUNIT IPC driver cleanup sathyanarayanan.kuppuswamy
2017-08-01 18:13 ` [RFC v1 1/6] platform/x86: intel_pmc_ipc: Fix error handling in ipc_pci_probe() sathyanarayanan.kuppuswamy
2017-08-18 12:22 ` Andy Shevchenko
2017-08-22 5:01 ` sathya
2017-08-01 18:13 ` [RFC v1 2/6] platform/x86: intel_pmc_ipc: Use devm_* calls in driver probe sathyanarayanan.kuppuswamy
2017-08-18 12:24 ` Andy Shevchenko
2017-08-22 5:05 ` sathya
2017-08-22 9:45 ` Andy Shevchenko
2017-08-01 18:13 ` [RFC v1 3/6] platform/x86: intel_pmc_ipc: Use MFD framework to create dependent devices sathyanarayanan.kuppuswamy
2017-08-02 5:14 ` Chakravarty, Souvik K
2017-08-02 21:59 ` sathyanarayanan kuppuswamy
2017-08-03 3:03 ` Chakravarty, Souvik K
2017-08-18 12:29 ` Andy Shevchenko
2017-08-22 5:02 ` sathya
2017-08-01 18:13 ` [RFC v1 4/6] platform: x86: Add generic Intel IPC driver sathyanarayanan.kuppuswamy
2017-08-18 12:38 ` Andy Shevchenko
2017-08-22 5:09 ` sathya [this message]
2017-08-22 9:50 ` Andy Shevchenko
2017-08-01 18:13 ` [RFC v1 5/6] platform/x86: intel_punit_ipc: Use generic intel ipc device calls sathyanarayanan.kuppuswamy
2017-08-01 18:13 ` [RFC v1 6/6] platform/x86: intel_pmc_ipc: Use generic Intel IPC " sathyanarayanan.kuppuswamy
2017-08-06 18:37 ` [RFC v1 0/6] PMC/PUNIT IPC driver cleanup Andy Shevchenko
2017-08-18 12: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=a6c43a40-9c47-330c-975c-cb60e63793a4@gmail.com \
--to=sathyaosid@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=qipeng.zha@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=x86@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®