From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Elwell Subject: Re: [PATCH v2 1/4] staging/vc04_services: Use correct cache line size Date: Fri, 14 Sep 2018 19:12:06 +0100 Message-ID: <6097c969-4290-bb92-3569-72e89561490c@raspberrypi.org> References: <1536931375-48769-1-git-send-email-phil@raspberrypi.org> <1536931375-48769-2-git-send-email-phil@raspberrypi.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: driverdev-devel-bounces@linuxdriverproject.org Sender: "devel" To: Florian Fainelli , Rob Herring , Stefan Wahren , Greg Kroah-Hartman , devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org, Russell King , Arnd Bergmann , linux-arm-kernel@lists.infradead.org, bcm-kernel-feedback-list@broadcom.com, devel@driverdev.osuosl.org List-Id: devicetree@vger.kernel.org On 14/09/2018 18:03, Florian Fainelli wrote: > On 09/14/2018 06:22 AM, Phil Elwell wrote: >> Use the compatible string in the DTB to select the correct cache line >> size for the SoC - 32 for BCM2835, and 64 for BCM2836 and BCM2837. >> >> Signed-off-by: Phil Elwell >> --- > > [snip] > >> @@ -170,6 +170,14 @@ static struct device *vchiq_dev; >> static DEFINE_SPINLOCK(msg_queue_spinlock); >> static struct platform_device *bcm2835_camera; >> >> +static struct vchiq_drvdata bcm2835_drvdata = { >> + .cache_line_size = 32, >> +}; >> + >> +static struct vchiq_drvdata bcm2836_drvdata = { >> + .cache_line_size = 64, >> +}; > > Those two structures could probably be marked const. Other than that, > the approach definitively looks good to me. The mutability is intentional - the structure pointer to the firmware is also stored there. This isn't the only piece of mutable static data in a driver that will only have a single instance, so allocating and initialising a per-instance structure seems needlessly complicated. Thanks for the feedback. Phil