From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: dlemoal@kernel.org, linux-ide@vger.kernel.org,
linux-m68k@vger.kernel.org, will@sowerbutts.com,
rz@linux-m68k.org, stable@vger.kernel.org,
Finn Thain <fthain@linux-m68k.org>
Subject: Re: [PATCH v3 1/2] ata: pata_falcon: fix IO base selection for Q40
Date: Tue, 22 Aug 2023 19:27:34 +1200 [thread overview]
Message-ID: <aabc6bd8-6407-3fa3-c620-69b290b3108c@gmail.com> (raw)
In-Reply-To: <CAMuHMdWNm7RdZcTa5EaWaFZ4NhPi75y8i31C2dkzJ5Hc4rtSJA@mail.gmail.com>
Hi Geert,
Am 22.08.2023 um 19:05 schrieb Geert Uytterhoeven:
>>>> + if (base_res) { /* only Q40 has IO resources */
>>>> + io_offset = 0x10000;
>>>> + reg_scale = 1;
>>>> + base = (void __iomem *)base_res->start;
>>>> + ctl_base = (void __iomem *)ctl_res->start;
>>>> +
>>>> + ata_port_desc(ap, "cmd %pa ctl %pa",
>>>> + &base_res->start,
>>>> + &ctl_res->start);
>>> This can be moved outside the else, using %px to format base and
>>> ctl_base.
>>
>> Right - do we need some additional message spelling out what address Q40
>> uses for data transfers? (Redundant for Falcon, of course ...)
>>
>> Though that could be handled outside the else, too:
>>
>> ata_port_desc(ap, "cmd %px ctl %px data %pa",
>> base, ctl_base, &ap->ioaddr.data_addr);
>
> I guess that wouldn't hurt.
Done - I'll send out v4 tomorrow.
Cheers,
Michael
>
> Gr{oetje,eeting}s,
>
> Geert
>
next prev parent reply other threads:[~2023-08-22 7:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230818234903.9226-1-schmitzmic@gmail.com>
2023-08-18 23:49 ` [PATCH v3 1/2] ata: pata_falcon: fix IO base selection for Q40 Michael Schmitz
2023-08-21 7:50 ` Geert Uytterhoeven
2023-08-21 23:57 ` Michael Schmitz
2023-08-22 7:05 ` Geert Uytterhoeven
2023-08-22 7:27 ` Michael Schmitz [this message]
2023-08-22 8:27 ` Michael Schmitz
2023-08-22 8:39 ` Geert Uytterhoeven
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=aabc6bd8-6407-3fa3-c620-69b290b3108c@gmail.com \
--to=schmitzmic@gmail.com \
--cc=dlemoal@kernel.org \
--cc=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=rz@linux-m68k.org \
--cc=stable@vger.kernel.org \
--cc=will@sowerbutts.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