From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-pci <linux-pci@vger.kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/5] MIPS: ralink: implement 'pcibios_root_bridge_prepare()'
Date: Wed, 12 Jan 2022 21:10:19 +0100 [thread overview]
Message-ID: <CAMhs-H851_Dh4R2TXWh80n1BwXQ7PdY+mQ652iWkJs2erCgK-A@mail.gmail.com> (raw)
In-Reply-To: <20220112182015.GA403047@roeck-us.net>
On Wed, Jan 12, 2022 at 7:20 PM Guenter Roeck <linux@roeck-us.net> wrote:
>
> On Tue, Dec 07, 2021 at 11:49:21AM +0100, Sergio Paracuellos wrote:
> > PCI core code call 'pcibios_root_bridge_prepare()' function inside function
> > 'pci_register_host_bridge()'. This point is very good way to properly enter
> > into this MIPS ralink specific code to properly setup I/O coherency units
> > with PCI memory addresses.
> >
> > Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
>
> FWIW:
>
> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Thanks!
Best regards,
Sergio Paracuellos
>
> > ---
> > arch/mips/ralink/mt7621.c | 31 +++++++++++++++++++++++++++++++
> > 1 file changed, 31 insertions(+)
> >
> > diff --git a/arch/mips/ralink/mt7621.c b/arch/mips/ralink/mt7621.c
> > index bd71f5b14238..d6efffd4dd20 100644
> > --- a/arch/mips/ralink/mt7621.c
> > +++ b/arch/mips/ralink/mt7621.c
> > @@ -10,6 +10,8 @@
> > #include <linux/slab.h>
> > #include <linux/sys_soc.h>
> > #include <linux/memblock.h>
> > +#include <linux/pci.h>
> > +#include <linux/bug.h>
> >
> > #include <asm/bootinfo.h>
> > #include <asm/mipsregs.h>
> > @@ -22,6 +24,35 @@
> >
> > static void *detect_magic __initdata = detect_memory_region;
> >
> > +int pcibios_root_bridge_prepare(struct pci_host_bridge *bridge)
> > +{
> > + struct resource_entry *entry;
> > + resource_size_t mask;
> > +
> > + entry = resource_list_first_type(&bridge->windows, IORESOURCE_MEM);
> > + if (!entry) {
> > + pr_err("Cannot get memory resource\n");
> > + return -EINVAL;
> > + }
> > +
> > + if (mips_cps_numiocu(0)) {
> > + /*
> > + * Hardware doesn't accept mask values with 1s after
> > + * 0s (e.g. 0xffef), so warn if that's happen
> > + */
> > + mask = ~(entry->res->end - entry->res->start) & CM_GCR_REGn_MASK_ADDRMASK;
> > + WARN_ON(mask && BIT(ffz(~mask)) - 1 != ~mask);
> > +
> > + write_gcr_reg1_base(entry->res->start);
> > + write_gcr_reg1_mask(mask | CM_GCR_REGn_MASK_CMTGT_IOCU0);
> > + pr_info("PCI coherence region base: 0x%08llx, mask/settings: 0x%08llx\n",
> > + (unsigned long long)read_gcr_reg1_base(),
> > + (unsigned long long)read_gcr_reg1_mask());
> > + }
> > +
> > + return 0;
> > +}
> > +
> > phys_addr_t mips_cpc_default_phys_base(void)
> > {
> > panic("Cannot detect cpc address");
> > --
> > 2.33.0
> >
next prev parent reply other threads:[~2022-01-12 20:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 10:49 [PATCH v3 0/5] PCI: mt7621: Remove specific MIPS code from driver Sergio Paracuellos
2021-12-07 10:49 ` [PATCH v3 1/5] PCI: Let pcibios_root_bridge_prepare() access to 'bridge->windows' Sergio Paracuellos
2021-12-07 10:49 ` [PATCH v3 2/5] MIPS: ralink: implement 'pcibios_root_bridge_prepare()' Sergio Paracuellos
2022-01-12 18:20 ` Guenter Roeck
2022-01-12 20:10 ` Sergio Paracuellos [this message]
2022-01-12 20:10 ` Thomas Bogendoerfer
2022-01-13 5:53 ` Sergio Paracuellos
2021-12-07 10:49 ` [PATCH v3 3/5] PCI: mt7621: Avoid custom MIPS code in driver code Sergio Paracuellos
2021-12-07 10:49 ` [PATCH v3 4/5] PCI: mt7621: Add missing 'MODULE_LICENSE()' definition Sergio Paracuellos
2021-12-07 10:49 ` [PATCH v3 5/5] PCI: mt7621: Allow COMPILE_TEST for all arches Sergio Paracuellos
2022-01-12 14:42 ` [PATCH v3 0/5] PCI: mt7621: Remove specific MIPS code from driver Sergio Paracuellos
2022-01-12 18:06 ` Lorenzo Pieralisi
2022-01-12 18:21 ` Guenter Roeck
2022-01-12 20:09 ` Sergio Paracuellos
2022-01-12 21:52 ` Bjorn Helgaas
2022-01-13 5:52 ` Sergio Paracuellos
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=CAMhs-H851_Dh4R2TXWh80n1BwXQ7PdY+mQ652iWkJs2erCgK-A@mail.gmail.com \
--to=sergio.paracuellos@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lorenzo.pieralisi@arm.com \
--cc=tsbogend@alpha.franken.de \
/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).