Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: "Hauke Mehrtens" <hauke@hauke-m.de>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Florian Fainelli" <florian.fainelli@broadcom.com>,
	"Broadcom internal kernel review list"
	<bcm-kernel-feedback-list@broadcom.com>,
	"Álvaro Fernández Rojas" <noltari@gmail.com>,
	linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 2/5] mips: bmips: rework and cache CBR addr handling
Date: Thu, 20 Jun 2024 16:40:42 +0200	[thread overview]
Message-ID: <ZnQ/auhuPWb1SGjb@alpha.franken.de> (raw)
In-Reply-To: <20240611113538.9004-3-ansuelsmth@gmail.com>

On Tue, Jun 11, 2024 at 01:35:34PM +0200, Christian Marangi wrote:
> Rework the handling of the CBR address and cache it. This address
> doesn't change and can be cached instead of reading the register every
> time.
> 
> This is in preparation of permitting to tweak the CBR address in DT with
> broken SoC or bootloader.
> 
> bmips_cbr_addr is defined in smp-bmips.c to keep compatibility with
> legacy brcm47xx/brcm63xx and generic BMIPS target.
> 
> Acked-by: Florian Fainelli <florian.fainelli@broadcom.com>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
>  arch/mips/bcm47xx/prom.c      | 3 +++
>  arch/mips/bcm63xx/prom.c      | 3 +++
>  arch/mips/bmips/dma.c         | 2 +-
>  arch/mips/bmips/setup.c       | 4 +++-
>  arch/mips/include/asm/bmips.h | 1 +
>  arch/mips/kernel/smp-bmips.c  | 6 ++++--
>  6 files changed, 15 insertions(+), 4 deletions(-)

still problems on a bcm47xx build:

mips64-linux-gnu-ld: arch/mips/bcm47xx/prom.o: in function `prom_init':
/local/tbogendoerfer/korg/linux/arch/mips/bcm47xx/prom.c:(.init.text+0x3c): undefined reference to `bmips_cbr_addr'
mips64-linux-gnu-ld: /local/tbogendoerfer/korg/linux/arch/mips/bcm47xx/prom.c:(.init.text+0x44): undefined reference to `bmips_cbr_addr'

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2024-06-20 14:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 11:35 [PATCH v7 0/5] mips: bmips: improve handling of RAC and CBR addr Christian Marangi
2024-06-11 11:35 ` [PATCH v7 1/5] mips: bmips: BCM6358: make sure CBR is correctly set Christian Marangi
2024-06-11 12:49   ` Thomas Bogendoerfer
2024-06-11 13:04     ` Christian Marangi
2024-06-11 14:03       ` Thomas Bogendoerfer
2024-06-11 14:12   ` Thomas Bogendoerfer
2024-06-11 11:35 ` [PATCH v7 2/5] mips: bmips: rework and cache CBR addr handling Christian Marangi
2024-06-20 14:40   ` Thomas Bogendoerfer [this message]
2024-06-20 15:28     ` Christian Marangi
2024-06-11 11:35 ` [PATCH v7 3/5] dt-bindings: mips: brcm: Document brcm,bmips-cbr-reg property Christian Marangi
2024-06-11 11:35 ` [PATCH v7 4/5] mips: bmips: setup: make CBR address configurable Christian Marangi
2024-06-11 11:35 ` [PATCH v7 5/5] mips: bmips: enable RAC on BMIPS4350 Christian Marangi

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=ZnQ/auhuPWb1SGjb@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=ansuelsmth@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=hauke@hauke-m.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=noltari@gmail.com \
    --cc=robh@kernel.org \
    --cc=zajec5@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