From: Michael Schmitz <schmitzmic@gmail.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH v1 1/4] m68k - add MVME147 SCSI base address to mvme147hw.h
Date: Tue, 12 Jul 2022 08:04:51 +1200 [thread overview]
Message-ID: <45072190-af84-d275-b36f-d7f3ff11f403@gmail.com> (raw)
In-Reply-To: <CAK8P3a0JRhKj9aoS3-RKsu3yGW+0geSB7CqEytdbBn622nREFw@mail.gmail.com>
Am 11.07.2022 um 20:45 schrieb Arnd Bergmann:
> On Mon, Jul 11, 2022 at 6:16 AM Michael Schmitz <schmitzmic@gmail.com> wrote:
>> Am 11.07.2022 um 04:06 schrieb Arnd Bergmann:
>>> On Sat, Jul 9, 2022 at 2:10 AM Michael Schmitz <schmitzmic@gmail.com> wrote:
>>> I think this should be an 'void *__iomem' token, not a plain integer.
>>> Apparently the driver internally uses a 'volatile void *', but some of
>>> the other front-ends are already converted to use __iomem.
>>
>> I'll pass the base address through a platform data struct in the next
>> version to address your other concerns. Haven't seen __iomem types used
>> in the other drivers - two are Zorro devices, and two platform devices
>> (a3000 and sgiwd93). Found no other wd33c93 drivers...
>
> Right, I noticed this as well. The ideal way to do this would be to change
> all of these files to use __iomem tokens consistently, and then use
> ioread32be()/iowrite32be() in place of the volatile pointer dereference.
On a second glance, the Amiga drivers _do_ use iomem types (ZTWO_VADDR()
does the Right Thing, leaving this driver and SGI.
Changes in wd33c93.c proper (which I read your mail to suggest) would
require actual hardware regression testing IMO. Not sure I can do that.
Cheers,
Michael
>
> Maybe leave that for a follow-up series, you'll probably uncover
> more of these issues once you take that step.
>
> Arnd
>
next prev parent reply other threads:[~2022-07-11 20:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 0:10 [PATCH v1 0/4] Convert m68k MVME147 WD33C93 SCSI driver to DMA API Michael Schmitz
2022-07-09 0:10 ` [PATCH v1 1/4] m68k - add MVME147 SCSI base address to mvme147hw.h Michael Schmitz
2022-07-10 16:06 ` Arnd Bergmann
2022-07-11 4:16 ` Michael Schmitz
2022-07-11 8:45 ` Arnd Bergmann
2022-07-11 20:04 ` Michael Schmitz [this message]
2022-07-09 0:10 ` [PATCH v1 2/4] m68k - set up platform device for mvme147_scsi Michael Schmitz
2022-07-09 5:29 ` kernel test robot
2022-07-10 15:56 ` Arnd Bergmann
2022-07-11 4:11 ` Michael Schmitz
2022-07-09 0:10 ` [PATCH v1 3/4] scsi - convert mvme146_scsi.c to platform device Michael Schmitz
2022-07-10 16:11 ` Arnd Bergmann
2022-07-11 7:16 ` Geert Uytterhoeven
2022-07-11 7:57 ` Michael Schmitz
2022-07-11 8:27 ` Geert Uytterhoeven
2022-07-11 20:02 ` Michael Schmitz
2022-07-12 3:27 ` Michael Schmitz
2022-07-12 6:57 ` Geert Uytterhoeven
2022-07-12 7:59 ` Michael Schmitz
2022-07-09 0:10 ` [PATCH v1 4/4] scsi - convert mvme147_scsi driver to DMA API Michael Schmitz
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=45072190-af84-d275-b36f-d7f3ff11f403@gmail.com \
--to=schmitzmic@gmail.com \
--cc=arnd@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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