From: Krzysztof Kozlowski <krzk@kernel.org>
To: Tudor Ambarus <tudor.ambarus@linaro.org>, jassisinghbrar@gmail.com
Cc: alim.akhtar@samsung.com, mst@redhat.com, javierm@redhat.com,
tzimmermann@suse.de, bartosz.golaszewski@linaro.org,
luzmaximilian@gmail.com, sudeep.holla@arm.com,
conor.dooley@microchip.com, bjorn@rivosinc.com,
ulf.hansson@linaro.org, linux-samsung-soc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, marcan@marcan.st,
neal@gompa.dev, alyssa@rosenzweig.io, broonie@kernel.org,
andre.draszik@linaro.org, willmcvicker@google.com,
peter.griffin@linaro.org, kernel-team@android.com,
vincent.guittot@linaro.org, daniel.lezcano@linaro.org
Subject: Re: [PATCH v2 2/2] firmware: add exynos acpm driver
Date: Wed, 23 Oct 2024 11:00:04 +0200 [thread overview]
Message-ID: <1e76bc70-21a6-4ac7-99ea-30a7ccf387bb@kernel.org> (raw)
In-Reply-To: <d91109a1-532a-4b95-ad4c-3b9cf8e3dbbb@linaro.org>
On 22/10/2024 09:58, Tudor Ambarus wrote:
>
>>>>
>>>> I also cannot find any piece of code setting several of above, e.g. tx_base
>>>
>>> I'm not writing any SRAM configuration fields, these fields are used to
>>> read/retrive the channel parameters from SRAM.
>>
>> I meany tx_base is always 0. Where is this property set? Ever?
>
> It's not zero. My assumption is it is set in the acpm firmware, but I
Where is any assignment to this member?
> don't have access to that to verify. Here are some debug prints made in
> the linux driver:
>
> [ 0.069575][ T1] gs-acpm-ipc 17610000.mailbox:
> exynos_mbox_chan_init ID = 2 poll = 1, mlen = 16, qlen = 5
> [ 0.069927][ T1] gs-acpm-ipc 17610000.mailbox:
> exynos_mbox_chan_init ID = 2 offsets: rx_base = 0x00038290 rx_front =
> 0x0003828c, rx_rear = 0x00038288
> [ 0.070449][ T1] gs-acpm-ipc 17610000.mailbox:
> exynos_mbox_chan_init ID = 2 offsets: tx_base = 0x000382f0 tx_front =
> 0x000382ec, tx_rear = 0x000382e8
>
>
> tx_base contains the SRAM offset of the RX queue used in linux. The
> offset is relative to the base address of the SRAM config data.
>
> tx_base is seen/named from the firmware's point of view, thus named TX.
> I assume the same struct is defined in the acpm firmware.
>
>
> Somewhere below in the linux driver I get the RX ring base address by doing:
>
> rx->base = exynos_acpm_get_iomem_addr(base, &shmem_chan->tx_base);
tx_base is still 0.
>
> where base is the SRAM base address of the channels configuration data.
>
> static void __iomem *exynos_acpm_get_iomem_addr(void __iomem *base,
>
>
> void __iomem *addr)
>
>
> {
>
>
> u32 offset;
>
>
>
>
>
> offset = readl_relaxed(addr);
>
>
> return base + offset;
>
>
> }
>
> Hope this clarifies a bit these struct members.
No, where is tx_base assigned?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-23 9:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 16:36 [PATCH v2 0/2] mailbox: add async request mechanism w/ a user Tudor Ambarus
2024-10-17 16:36 ` [PATCH v2 1/2] mailbox: add async request mechanism to empower controllers w/ hw queues Tudor Ambarus
2024-10-18 4:17 ` Jassi Brar
2024-10-18 7:49 ` Tudor Ambarus
2024-10-21 6:18 ` Tudor Ambarus
2024-10-21 16:32 ` Jassi Brar
2024-10-22 13:26 ` Tudor Ambarus
2024-10-24 1:27 ` Jassi Brar
2024-10-24 10:45 ` Tudor Ambarus
2024-10-29 15:59 ` Jassi Brar
2024-11-18 15:22 ` Tudor Ambarus
2024-10-17 16:36 ` [PATCH v2 2/2] firmware: add exynos acpm driver Tudor Ambarus
2024-10-21 11:52 ` Krzysztof Kozlowski
2024-10-21 14:12 ` Tudor Ambarus
2024-10-22 4:38 ` Krzysztof Kozlowski
2024-10-22 7:27 ` Vincent Guittot
2024-10-22 7:58 ` Tudor Ambarus
2024-10-23 9:00 ` Krzysztof Kozlowski [this message]
2024-10-23 9:53 ` Tudor Ambarus
2024-10-23 10:02 ` Tudor Ambarus
2024-10-24 9:36 ` Krzysztof Kozlowski
2024-10-25 10:00 ` Tudor Ambarus
2024-10-21 14:52 ` Tudor Ambarus
2024-10-21 16:47 ` Alim Akhtar
2024-10-25 9:44 ` Tudor Ambarus
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=1e76bc70-21a6-4ac7-99ea-30a7ccf387bb@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=alyssa@rosenzweig.io \
--cc=andre.draszik@linaro.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=bjorn@rivosinc.com \
--cc=broonie@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=daniel.lezcano@linaro.org \
--cc=jassisinghbrar@gmail.com \
--cc=javierm@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--cc=marcan@marcan.st \
--cc=mst@redhat.com \
--cc=neal@gompa.dev \
--cc=peter.griffin@linaro.org \
--cc=sudeep.holla@arm.com \
--cc=tudor.ambarus@linaro.org \
--cc=tzimmermann@suse.de \
--cc=ulf.hansson@linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=willmcvicker@google.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