From: Michael Walle <michael@walle.cc>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-kernel@vger.kernel.org, Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Russell King <linux@armlinux.org.uk>
Subject: Re: [RFC PATCH] mfd: mfd-core: inherit only valid dma_masks/flags from parent
Date: Wed, 11 Mar 2020 08:59:27 +0100 [thread overview]
Message-ID: <4832f1edcad3fadeafce77680a7e7138@walle.cc> (raw)
In-Reply-To: <20200311061806.GB10902@lst.de>
Am 2020-03-11 07:18, schrieb Christoph Hellwig:
> On Wed, Mar 11, 2020 at 12:09:35AM +0100, Michael Walle wrote:
>> Only copy the dma_masks and flags from the parent device, if the
>> parent
>> has a valid dma_mask/flags. Commit cdfee5623290 ("driver core:
>> initialize a default DMA mask for platform device") initialize the DMA
>> masks of a platform device. But if the parent doesn't have a dma_mask
>> set, for example if it's an I2C device, the dma_mask of the child
>> platform device will be set to zero again. Which leads to many "DMA
>> mask
>> not set" warnings, if the MFD cell has the of_compatible property set.
>>
>> [ 1.877937] sl28cpld-pwm sl28cpld-pwm: DMA mask not set
>> [ 1.883282] sl28cpld-pwm sl28cpld-pwm.0: DMA mask not set
>> [ 1.888795] sl28cpld-gpio sl28cpld-gpio: DMA mask not set
>>
>> Thus a MFD child should just inherit valid dma_masks and keep the
>> platform default otherwise.
>>
>> Cc: Christoph Hellwig <hch@lst.de>
>> Cc: Rob Herring <robh@kernel.org>
>> Cc: Robin Murphy <robin.murphy@arm.com>
>> Cc: Russell King <linux@armlinux.org.uk>
>> Signed-off-by: Michael Walle <michael@walle.cc>
>> ---
>>
>> Hi,
>>
>> I don't know if that is the correct way of handling things. Maybe I'm
>> also doing something wrong in my driver, I had a look at other I2C MFD
>> drivers but couldn't find a clue why they shouldn't have the same
>> problem.
>>
>> There was also a thread [1] about this topic, but there seems to be no
>> conclusion.
>>
>> [1] https://www.spinics.net/lists/linux-renesas-soc/msg31581.html
>>
>> drivers/mfd/mfd-core.c | 9 ++++++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/mfd/mfd-core.c b/drivers/mfd/mfd-core.c
>> index b9eb8f40c073..5d8ea5e8e93c 100644
>> --- a/drivers/mfd/mfd-core.c
>> +++ b/drivers/mfd/mfd-core.c
>> @@ -139,9 +139,12 @@ static int mfd_add_device(struct device *parent,
>> int id,
>>
>> pdev->dev.parent = parent;
>> pdev->dev.type = &mfd_dev_type;
>> - pdev->dev.dma_mask = parent->dma_mask;
>> - pdev->dev.dma_parms = parent->dma_parms;
>> - pdev->dev.coherent_dma_mask = parent->coherent_dma_mask;
>> + if (parent->dma_mask)
>> + pdev->dev.dma_mask = parent->dma_mask;
>> + if (parent->dma_parms)
>> + pdev->dev.dma_parms = parent->dma_parms;
>
> Both of these are pointers, and we can't just share them. You need
> to allocate storage for them and the allocate the values over.
So they were alreay copied wrong before this patch? If so, should
there be a fixes patch for it? The commit who introduced the copy
dates back to 2013:
b018e1361bad3 mfd: core: Copy DMA mask and params from parent
-michael
next prev parent reply other threads:[~2020-03-11 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 23:09 Michael Walle
2020-03-11 6:18 ` Christoph Hellwig
2020-03-11 7:59 ` Michael Walle [this message]
2020-03-11 11:25 ` Robin Murphy
2020-03-11 13:10 ` Michael Walle
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=4832f1edcad3fadeafce77680a7e7138@walle.cc \
--to=michael@walle.cc \
--cc=hch@lst.de \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.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®