From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Vijendar Mukunda <Vijendar.Mukunda@amd.com>,
broonie@kernel.org, alsa-devel@alsa-project.org
Cc: Mastan.Katragadda@amd.com, Sunilkumar.Dommati@amd.com,
Basavaraj.Hiregoudar@amd.com,
open list <linux-kernel@vger.kernel.org>,
Vinod Koul <vkoul@kernel.org>,
Mario.Limonciello@amd.com, arungopal.kondaveeti@amd.com,
Sanyog Kale <sanyog.r.kale@intel.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>
Subject: Re: [PATCH] soundwire: export sdw_compute_slave_ports() function
Date: Wed, 1 Feb 2023 17:21:15 -0600 [thread overview]
Message-ID: <84adef23-fecf-76ec-c597-5f8b4be214da@linux.intel.com> (raw)
In-Reply-To: <20230201165944.3169125-1-Vijendar.Mukunda@amd.com>
On 2/1/23 10:59, Vijendar Mukunda wrote:
> Export sdw_compute_slave_ports() function to use it in another
> soundwire manager module.
> Move sdw_transport_data structure to bus header file to export
> sdw_compute_slave_ports() function.
>
> Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
If a specific platform has a need to modify parts of the bit allocation
but can reuse parts of the code, that's fine. The 'generic bandwidth
allocation' was meant to be a reference, not a one-size-fits-all solution.
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> ---
> drivers/soundwire/bus.h | 9 +++++++++
> drivers/soundwire/generic_bandwidth_allocation.c | 12 +++---------
> 2 files changed, 12 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/soundwire/bus.h b/drivers/soundwire/bus.h
> index 7631ef5e71fb..141b99ac58de 100644
> --- a/drivers/soundwire/bus.h
> +++ b/drivers/soundwire/bus.h
> @@ -144,6 +144,13 @@ struct sdw_master_runtime {
> struct list_head bus_node;
> };
>
> +struct sdw_transport_data {
> + int hstart;
> + int hstop;
> + int block_offset;
> + int sub_block_offset;
> +};
> +
> struct sdw_dpn_prop *sdw_get_slave_dpn_prop(struct sdw_slave *slave,
> enum sdw_data_direction direction,
> unsigned int port_num);
> @@ -213,5 +220,7 @@ int sdw_bwrite_no_pm_unlocked(struct sdw_bus *bus, u16 dev_num, u32 addr, u8 val
>
> void sdw_clear_slave_status(struct sdw_bus *bus, u32 request);
> int sdw_slave_modalias(const struct sdw_slave *slave, char *buf, size_t size);
> +void sdw_compute_slave_ports(struct sdw_master_runtime *m_rt,
> + struct sdw_transport_data *t_data);
>
> #endif /* __SDW_BUS_H */
> diff --git a/drivers/soundwire/generic_bandwidth_allocation.c b/drivers/soundwire/generic_bandwidth_allocation.c
> index f7c66083a4dd..39543048baa7 100644
> --- a/drivers/soundwire/generic_bandwidth_allocation.c
> +++ b/drivers/soundwire/generic_bandwidth_allocation.c
> @@ -28,15 +28,8 @@ struct sdw_group {
> unsigned int *rates;
> };
>
> -struct sdw_transport_data {
> - int hstart;
> - int hstop;
> - int block_offset;
> - int sub_block_offset;
> -};
> -
> -static void sdw_compute_slave_ports(struct sdw_master_runtime *m_rt,
> - struct sdw_transport_data *t_data)
> +void sdw_compute_slave_ports(struct sdw_master_runtime *m_rt,
> + struct sdw_transport_data *t_data)
> {
> struct sdw_slave_runtime *s_rt = NULL;
> struct sdw_port_runtime *p_rt;
> @@ -85,6 +78,7 @@ static void sdw_compute_slave_ports(struct sdw_master_runtime *m_rt,
> }
> }
> }
> +EXPORT_SYMBOL(sdw_compute_slave_ports);
>
> static void sdw_compute_master_ports(struct sdw_master_runtime *m_rt,
> struct sdw_group_params *params,
next prev parent reply other threads:[~2023-02-03 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 16:59 [PATCH] soundwire: export sdw_compute_slave_ports() function Vijendar Mukunda
2023-02-01 23:21 ` Pierre-Louis Bossart [this message]
2023-02-07 6:14 ` Mukunda,Vijendar
2023-02-08 6:33 ` Christoph Hellwig
2023-02-08 7:19 ` Mukunda,Vijendar
-- strict thread matches above, loose matches on Subject: below --
2023-02-07 7:16 Vijendar Mukunda
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=84adef23-fecf-76ec-c597-5f8b4be214da@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Mastan.Katragadda@amd.com \
--cc=Sunilkumar.Dommati@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=arungopal.kondaveeti@amd.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanyog.r.kale@intel.com \
--cc=vkoul@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox