public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
Cc: <broonie@kernel.org>, <lgirdwood@gmail.com>,
	<peter.ujfalusi@linux.intel.com>,
	<yung-chuan.liao@linux.intel.com>, <linux-sound@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <patches@opensource.cirrus.com>
Subject: Re: [PATCH 4/5] ASoC: SDCA: Add missing function type names
Date: Mon, 6 Jan 2025 12:20:09 +0000	[thread overview]
Message-ID: <Z3vKeVipRSC9ABia@opensource.cirrus.com> (raw)
In-Reply-To: <f2038977-4f5b-4a9a-bd5f-89e6839e1703@linux.dev>

On Thu, Jan 02, 2025 at 04:01:19PM -0600, Pierre-Louis Bossart wrote:
> On 12/20/24 11:35, Charles Keepax wrote:
> >   	case SDCA_FUNCTION_TYPE_IMP_DEF:
> > -		dev_warn(dev, "unsupported SDCA function type %d\n", *function_type);
> > -		return -EINVAL;
> > +		*function_name = SDCA_FUNCTION_TYPE_IMP_DEF_NAME;
> > +		break;
> 
> but this one is controversial. We really have no idea what to do in this
> case. There could be completely different 'imp-def' functions that require
> different drivers. I don't know how the entire binding mechanism would work.
> Probably best to err on the side of throwing a 'not supported' error?
> 

I would certainly agree with you that a generic class driver
implementation would not bind against an imp def function, but I
see no reason to prevent custom driver implementations from being
able to access this function. They will be creating the parent
auxilary stuff and can bind whatever they like to this imp def
function.

Thanks,
Charles

  reply	other threads:[~2025-01-06 12:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 17:35 [PATCH 1/5] ASoC: SDCA: Add missing header includes Charles Keepax
2024-12-20 17:35 ` [PATCH 2/5] ASoC: SDCA: Clean up error messages Charles Keepax
2024-12-20 17:35 ` [PATCH 3/5] ASoC: SDCA: Add bounds check for function address Charles Keepax
2024-12-20 17:35 ` [PATCH 4/5] ASoC: SDCA: Add missing function type names Charles Keepax
2025-01-02 22:01   ` Pierre-Louis Bossart
2025-01-06 12:20     ` Charles Keepax [this message]
2024-12-20 17:35 ` [PATCH 5/5] ASoC: SDCA: Split function type patching and function naming Charles Keepax
2024-12-25  1:23 ` [PATCH 1/5] ASoC: SDCA: Add missing header includes Mark Brown
2025-01-06 12:07 ` Mark Brown

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=Z3vKeVipRSC9ABia@opensource.cirrus.com \
    --to=ckeepax@opensource.cirrus.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.dev \
    --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