All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
Cc: alsa-devel@alsa-project.org,
	pierre-louis.bossart@linux.intel.com,
	Basavaraj.Hiregoudar@amd.com, Sunil-kumar.Dommati@amd.com,
	Mario.Limonciello@amd.com, amadeuszx.slawinski@linux.intel.com,
	Mastan.Katragadda@amd.com, Arungopal.kondaveeti@amd.com,
	claudiu.beznea@microchip.com,
	Bard Liao <yung-chuan.liao@linux.intel.com>,
	Sanyog Kale <sanyog.r.kale@intel.com>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V6 2/8] soundwire: amd: Add support for AMD Manager driver
Date: Fri, 17 Mar 2023 19:04:23 +0530	[thread overview]
Message-ID: <ZBRsX7W4l1HyT44y@matsya> (raw)
In-Reply-To: <7a7f5d93-d6ec-5ad1-9927-7ac4b6d9a643@amd.com>

On 16-03-23, 19:28, Mukunda,Vijendar wrote:
> On 15/03/23 15:12, Vinod Koul wrote:
> > On 07-03-23, 19:01, Vijendar Mukunda wrote:

> >> +/**
> >> + * struct amd_sdw_manager - amd manager driver context
> >> + * @bus: bus handle
> >> + * @dev: linux device
> >> + * @mmio: SoundWire registers mmio base
> >> + * @acp_mmio: acp registers mmio base
> >> + * @reg_mask: register mask structure per manager instance
> >> + * @probe_work: SoundWire manager probe workqueue
> >> + * @acp_sdw_lock: mutex to protect acp share register access
> >> + * @num_din_ports: number of input ports
> >> + * @num_dout_ports: number of output ports
> >> + * @cols_index: Column index in frame shape
> >> + * @rows_index: Rows index in frame shape
> >> + * @instance: SoundWire manager instance
> >> + * @quirks: SoundWire manager quirks
> >> + * @wake_en_mask: wake enable mask per SoundWire manager
> >> + * @power_mode_mask: flag interprets amd SoundWire manager power mode
> >> + */
> >> +struct amd_sdw_manager {
> >> +	struct sdw_bus bus;
> >> +	struct device *dev;
> >> +
> >> +	void __iomem *mmio;
> >> +	void __iomem *acp_mmio;
> >> +
> >> +	struct sdw_manager_reg_mask *reg_mask;
> >> +	struct work_struct probe_work;
> >> +	/* mutex to protect acp common register access */
> >> +	struct mutex *acp_sdw_lock;
> >> +
> >> +	int num_din_ports;
> >> +	int num_dout_ports;
> >> +
> >> +	int cols_index;
> >> +	int rows_index;
> >> +
> >> +	u32 instance;
> >> +	u32 quirks;
> >> +	u32 wake_en_mask;
> >> +	u32 power_mode_mask;
> >> +};
> > Does the manager need to be exposed to rest of kernel or users of this
> > driver, is so why?
> Currently, amd_manager structure being used in ACP PCI driver
> (parent driver) and Soundwire DMA driver.
> 
> In ACP PCI driver, IRQ handler we will use amd_manager structure to
> schedule workqueue based on soundwire manager instance.
> In Soundwire DMA driver, we need to retrieve amd_manager instance.
> As per our design, we have fixed mapping. We need to use same set of
> DMA registers based on CPU DAI ID.
>  i.e if AUDIO0 TX port is selected in amd_manager driver
> then we need to use AUDIO0 TX registers for DMA programming.
> we have included comments for describing mapping in amd_manager.h
> file.

Sorry not sure I follow, can you elaborate which members of above struct
are used by PCI driver?

-- 
~Vinod

  reply	other threads:[~2023-03-17 13:35 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230307133135.545952-1-Vijendar.Mukunda@amd.com>
2023-03-07 13:31 ` [PATCH V6 1/8] soundwire: export sdw_compute_slave_ports() function Vijendar Mukunda
2023-03-07 13:31 ` Vijendar Mukunda via Alsa-devel
2023-03-07 13:31 ` [PATCH V6 2/8] soundwire: amd: Add support for AMD Manager driver Vijendar Mukunda
2023-03-07 15:25   ` Pierre-Louis Bossart
2023-03-07 20:36     ` Mukunda,Vijendar via Alsa-devel
2023-03-07 20:36     ` Mukunda,Vijendar
2023-03-15  9:42   ` Vinod Koul
2023-03-16 13:58     ` Mukunda,Vijendar via Alsa-devel
2023-03-16 13:58     ` Mukunda,Vijendar
2023-03-17 13:34       ` Vinod Koul [this message]
2023-03-17 14:04         ` Mukunda,Vijendar
2023-03-17 14:04         ` Mukunda,Vijendar via Alsa-devel
2023-03-07 13:31 ` Vijendar Mukunda via Alsa-devel
2023-03-07 13:31 ` [PATCH V6 3/8] soundwire: amd: register SoundWire manager dai ops Vijendar Mukunda
2023-03-15  9:58   ` Vinod Koul
2023-03-16  3:32     ` Mukunda,Vijendar via Alsa-devel
2023-03-16  3:32     ` Mukunda,Vijendar
2023-03-07 13:31 ` Vijendar Mukunda via Alsa-devel
2023-03-07 13:31 ` [PATCH V6 4/8] soundwire: amd: enable build for AMD SoundWire manager driver Vijendar Mukunda
2023-03-15  9:59   ` Vinod Koul
2023-03-16  3:29     ` Mukunda,Vijendar via Alsa-devel
2023-03-16  3:29     ` Mukunda,Vijendar
2023-03-07 13:31 ` Vijendar Mukunda via Alsa-devel
2023-03-07 13:31 ` [PATCH V6 5/8] soundwire: amd: add SoundWire manager interrupt handling Vijendar Mukunda
2023-03-15 10:06   ` Vinod Koul
2023-03-16 17:04     ` Mukunda,Vijendar via Alsa-devel
2023-03-16 17:04     ` Mukunda,Vijendar
2023-03-17 13:36       ` Vinod Koul
2023-03-17 14:46         ` Mukunda,Vijendar via Alsa-devel
2023-03-17 14:46         ` Mukunda,Vijendar
2023-03-07 13:31 ` Vijendar Mukunda via Alsa-devel
2023-03-07 13:31 ` [PATCH V6 6/8] soundwire: amd: add runtime pm ops for AMD SoundWire manager driver Vijendar Mukunda via Alsa-devel
2023-03-07 13:31 ` Vijendar Mukunda
2023-03-07 13:31 ` [PATCH V6 7/8] soundwire: amd: handle SoundWire wake enable interrupt Vijendar Mukunda via Alsa-devel
2023-03-07 13:31 ` Vijendar Mukunda
2023-03-07 13:31 ` [PATCH V6 8/8] soundwire: amd: add pm_prepare callback and pm ops support Vijendar Mukunda
2023-03-07 15:28   ` Pierre-Louis Bossart
2023-03-07 20:25     ` Mukunda,Vijendar via Alsa-devel
2023-03-07 20:25     ` Mukunda,Vijendar
2023-03-07 21:08       ` Pierre-Louis Bossart
2023-03-08  4:32         ` Mukunda,Vijendar
2023-03-08 13:58           ` Pierre-Louis Bossart
2023-03-08 14:19             ` Mukunda,Vijendar
2023-03-08 14:23               ` Pierre-Louis Bossart
2023-03-08 15:05                 ` Mukunda,Vijendar via Alsa-devel
2023-03-08 15:05                 ` Mukunda,Vijendar
2023-03-08 14:19             ` Mukunda,Vijendar via Alsa-devel
2023-03-08  4:32         ` Mukunda,Vijendar via Alsa-devel
2023-03-07 13:31 ` Vijendar Mukunda via Alsa-devel

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=ZBRsX7W4l1HyT44y@matsya \
    --to=vkoul@kernel.org \
    --cc=Arungopal.kondaveeti@amd.com \
    --cc=Basavaraj.Hiregoudar@amd.com \
    --cc=Mario.Limonciello@amd.com \
    --cc=Mastan.Katragadda@amd.com \
    --cc=Sunil-kumar.Dommati@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=claudiu.beznea@microchip.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=sanyog.r.kale@intel.com \
    --cc=vijendar.mukunda@amd.com \
    --cc=yung-chuan.liao@linux.intel.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 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.