From: Stepan Moskovchenko <stepanm@codeaurora.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: dwalker@codeaurora.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v4] arm: msm: Add MSM IOMMU support.
Date: Tue, 17 Aug 2010 02:02:44 -0700 [thread overview]
Message-ID: <4C6A5034.2090406@codeaurora.org> (raw)
In-Reply-To: <20100816183226.GA31512@phenom.dumpdata.com>
On 8/16/2010 11:32 AM, Konrad Rzeszutek Wilk wrote:
> I did a very brief look.
>
>> + dmac_flush_range(fl_table, fl_table + SZ_16K);
>> +
>> + for (i = 0; i< 4096; i++)
> Can you use a #define for the 4096? Will that value ever change?
I suppose a #define can be used, but this is a HW-specific number that
will never ever change.
>> + if ((fl_table[i]& 0x03) == FL_TYPE_TABLE) {
>> + void *sl_table = __va(fl_table[i]& 0xFFFFFC00);
> Does it make sense to define say:
> #define MASK_XX (x) x& 0xFFFFFC00
> and
> #define MASK_XY (x) x& 0xFFFF0000
>
> and use those instead of these hard-coded values?
I guess so.. again, HW specific.
>> + priv->pgtable = (unsigned long *)__get_free_pages(GFP_KERNEL, 2);
> Ugh. Can you use get_order(SZ_16K) instead?
>
>> + /* Invalidate context TLB */
>> + SET_CTX_TLBIALL(base, ctx, 0);
>> + SET_V2PPR_VA(base, ctx, va>> 12);
> Hmm, PAGE_SHIFT can't be used? Or some other #define?
I guess I can use the IOMMU PA shift. PAGE_SHIFT is not appropriate here
because that is MMU-specific.
I can put out a v5 early next week.
Thanks
Steve
WARNING: multiple messages have this Message-ID (diff)
From: stepanm@codeaurora.org (Stepan Moskovchenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] arm: msm: Add MSM IOMMU support.
Date: Tue, 17 Aug 2010 02:02:44 -0700 [thread overview]
Message-ID: <4C6A5034.2090406@codeaurora.org> (raw)
In-Reply-To: <20100816183226.GA31512@phenom.dumpdata.com>
On 8/16/2010 11:32 AM, Konrad Rzeszutek Wilk wrote:
> I did a very brief look.
>
>> + dmac_flush_range(fl_table, fl_table + SZ_16K);
>> +
>> + for (i = 0; i< 4096; i++)
> Can you use a #define for the 4096? Will that value ever change?
I suppose a #define can be used, but this is a HW-specific number that
will never ever change.
>> + if ((fl_table[i]& 0x03) == FL_TYPE_TABLE) {
>> + void *sl_table = __va(fl_table[i]& 0xFFFFFC00);
> Does it make sense to define say:
> #define MASK_XX (x) x& 0xFFFFFC00
> and
> #define MASK_XY (x) x& 0xFFFF0000
>
> and use those instead of these hard-coded values?
I guess so.. again, HW specific.
>> + priv->pgtable = (unsigned long *)__get_free_pages(GFP_KERNEL, 2);
> Ugh. Can you use get_order(SZ_16K) instead?
>
>> + /* Invalidate context TLB */
>> + SET_CTX_TLBIALL(base, ctx, 0);
>> + SET_V2PPR_VA(base, ctx, va>> 12);
> Hmm, PAGE_SHIFT can't be used? Or some other #define?
I guess I can use the IOMMU PA shift. PAGE_SHIFT is not appropriate here
because that is MMU-specific.
I can put out a v5 early next week.
Thanks
Steve
next prev parent reply other threads:[~2010-08-17 9:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 19:45 [PATCH v4] arm: msm: Add MSM IOMMU support Stepan Moskovchenko
2010-08-10 19:45 ` Stepan Moskovchenko
2010-08-12 14:30 ` Joerg Roedel
2010-08-12 14:30 ` Joerg Roedel
2010-08-16 18:32 ` Konrad Rzeszutek Wilk
2010-08-16 18:32 ` Konrad Rzeszutek Wilk
2010-08-17 9:02 ` Stepan Moskovchenko [this message]
2010-08-17 9:02 ` Stepan Moskovchenko
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=4C6A5034.2090406@codeaurora.org \
--to=stepanm@codeaurora.org \
--cc=dwalker@codeaurora.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.