mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>, Sinan Kaya <Okaya@kernel.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Shawn Lin <shawn.lin@rock-chips.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	faiz_abbas@ti.com, chunyan.zhang@unisoc.com,
	Jisheng.Zhang@synaptics.com, ludovic.barre@st.com,
	Arnd Bergmann <arnd@arndb.de>,
	alex.smith@imgtec.com, chris.brandt@renesas.com,
	linux-mmc <linux-mmc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 09/11] mmc: add PCI dependency into IOSF_MBI
Date: Wed, 2 Jan 2019 16:03:14 +0200	[thread overview]
Message-ID: <21e732e8-84e4-72f9-4142-8e6af54f1346@intel.com> (raw)
In-Reply-To: <CAJZ5v0hw_=Odpok=6qWVWAfJ0wG7Z8NjwzMCpaFgxYnEAreKcg@mail.gmail.com>

On 31/12/18 11:40 AM, Rafael J. Wysocki wrote:
> On Sun, Dec 30, 2018 at 7:57 PM Sinan Kaya <Okaya@kernel.org> wrote:
>>
>> On Wed, Dec 26, 2018 at 12:41 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
>>>
>>> On Mon, Dec 24, 2018 at 12:26 AM Sinan Kaya <okaya@kernel.org> wrote:
>>>>
>>>> Select IOSF_MBI only when PCI is set.
>>>>
>>>> Signed-off-by: Sinan Kaya <okaya@kernel.org>
>>>> ---
>>>>  drivers/mmc/host/Kconfig | 2 +-
>>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
>>>> index e26b8145efb3..4c5f037b246d 100644
>>>> --- a/drivers/mmc/host/Kconfig
>>>> +++ b/drivers/mmc/host/Kconfig
>>>> @@ -117,7 +117,7 @@ config MMC_RICOH_MMC
>>>>  config MMC_SDHCI_ACPI
>>>>         tristate "SDHCI support for ACPI enumerated SDHCI controllers"
>>>>         depends on MMC_SDHCI && ACPI
>>>
>>> It should depend on PCI as well, shouldn't it?
>>>
>>
>> I don't think so. The PCI dependency is at IOSF_MBI code so code
>> should select IOSF_MBI only when x86 and pci is defined as below.
>>
>> This driver does not depend on PCI.
> 
> Are you sure?
> 
> Do you know any systems in which to use it without PCI?
> 

Qualcomm use it and I don't know if those systems have PCI.
AMD use it but probably also have PCI.  And yes Intel systems (just BYT and
CHT IIRC) that use this driver will always have PCI.

  reply	other threads:[~2019-01-02 14:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181223232521.11320-1-okaya@kernel.org>
2018-12-23 23:25 ` [PATCH v3 01/11] ACPI / LPSS: Make PCI dependency explicit Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 02/11] ata: make PCI dependency explicit for PATA_ACPI Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 03/11] vga-switcheroo: make PCI dependency explicit Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 04/11] platform/x86: intel_ips: " Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 05/11] platform/x86: intel_pmc: Make " Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 06/11] apple-gmux: " Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 07/11] drivers: thermal: int3406_thermal: " Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 08/11] ASoC: Intel: atom: " Sinan Kaya
2018-12-26 17:35   ` Pierre-Louis Bossart
2018-12-26 20:07     ` Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 09/11] mmc: add PCI dependency into IOSF_MBI Sinan Kaya
2018-12-26  9:40   ` Rafael J. Wysocki
2018-12-30 18:56     ` Sinan Kaya
2018-12-31  9:40       ` Rafael J. Wysocki
2019-01-02 14:03         ` Adrian Hunter [this message]
2019-01-02 14:15           ` Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 10/11] x86: select IOSF_MBI only when CONFIG_PCI is set Sinan Kaya
2018-12-25  9:13   ` Rafael J. Wysocki
2018-12-30 19:04     ` Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 11/11] drivers: thermal: int340x_thermal: Make PCI dependency explicit Sinan Kaya

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=21e732e8-84e4-72f9-4142-8e6af54f1346@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=Jisheng.Zhang@synaptics.com \
    --cc=Okaya@kernel.org \
    --cc=alex.smith@imgtec.com \
    --cc=arnd@arndb.de \
    --cc=chris.brandt@renesas.com \
    --cc=chunyan.zhang@unisoc.com \
    --cc=faiz_abbas@ti.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ludovic.barre@st.com \
    --cc=rafael@kernel.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=ulf.hansson@linaro.org \
    --cc=yamada.masahiro@socionext.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®