mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bumwoo Lee" <bw365.lee@samsung.com>
To: "'Chanwoo Choi'" <cwchoi00@gmail.com>,
	"'MyungJoo Ham'" <myungjoo.ham@samsung.com>,
	"'Chanwoo Choi'" <cw00.choi@samsung.com>,
	<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v4 4/4] extcon: Added extcon_alloc_groups to simplify extcon register function
Date: Mon, 20 Mar 2023 12:12:33 +0900	[thread overview]
Message-ID: <186501d95ad9$d0812d30$71838790$@samsung.com> (raw)
In-Reply-To: <3de6d1b0-51f8-368b-e73f-8c1e007bf7f8@gmail.com>


> -----Original Message-----
> From: Chanwoo Choi <cwchoi00@gmail.com>
> Sent: Monday, March 13, 2023 8:08 PM
> To: Bumwoo Lee <bw365.lee@samsung.com>; MyungJoo Ham
> <myungjoo.ham@samsung.com>; Chanwoo Choi <cw00.choi@samsung.com>; linux-
> kernel@vger.kernel.org
> Subject: Re: [PATCH v4 4/4] extcon: Added extcon_alloc_groups to simplify
> extcon register function
> 
> On 23. 3. 2. 18:01, Bumwoo Lee wrote:
> > The alloc groups is functionalized from extcon_dev_register.
> >
> > Signed-off-by: Bumwoo Lee <bw365.lee@samsung.com>
> > ---
> >  drivers/extcon/extcon.c | 58
> > +++++++++++++++++++++++++----------------
> >  1 file changed, 36 insertions(+), 22 deletions(-)
> >
> > diff --git a/drivers/extcon/extcon.c b/drivers/extcon/extcon.c index
> > 321988231806..c366a7988daf 100644
> > --- a/drivers/extcon/extcon.c
> > +++ b/drivers/extcon/extcon.c
> > @@ -1181,6 +1181,39 @@ static int extcon_alloc_muex(struct extcon_dev
> *edev)
> >  	return 0;
> >  }
> >
> > +/**
> > + * extcon_alloc_groups() - alloc the groups for extcon device
> > + * @edev:	extcon device
> > + *
> > + * Returns 0 if success or error number if fail.
> > + */
> > +static int extcon_alloc_groups(struct extcon_dev *edev) {
> > +	int index;
> > +
> 
> ditto.
> 
> 	if (!edev)
> 		return -EINVAL;
> 
> > +	if (!edev->max_supported)
> > +		return 0;
> > +
> > +	edev->extcon_dev_type.groups = kcalloc(edev->max_supported + 2,
> > +			sizeof(struct attribute_group *),
> > +			GFP_KERNEL);
> > +	if (!edev->extcon_dev_type.groups)
> > +		return -ENOMEM;
> > +
> > +	edev->extcon_dev_type.name = dev_name(&edev->dev);
> > +	edev->extcon_dev_type.release = dummy_sysfs_dev_release;
> > +
> > +	for (index = 0; index < edev->max_supported; index++)
> > +		edev->extcon_dev_type.groups[index] = &edev-
> >cables[index].attr_g;
> > +
> > +	if (edev->mutually_exclusive)
> > +		edev->extcon_dev_type.groups[index] = &edev->attr_g_muex;
> > +
> > +	edev->dev.type = &edev->extcon_dev_type;
> > +
> > +	return 0;
> > +}
> > +
> >  /**
> >   * extcon_dev_register() - Register an new extcon device
> >   * @edev:	the extcon device to be registered
> > @@ -1236,28 +1269,9 @@ int extcon_dev_register(struct extcon_dev *edev)
> >  	if (ret < 0)
> >  		goto err_alloc_muex;
> >
> > -	if (edev->max_supported) {
> > -		edev->extcon_dev_type.groups =
> > -			kcalloc(edev->max_supported + 2,
> > -				sizeof(struct attribute_group *),
> > -				GFP_KERNEL);
> > -		if (!edev->extcon_dev_type.groups) {
> > -			ret = -ENOMEM;
> > -			goto err_alloc_groups;
> > -		}
> > -
> > -		edev->extcon_dev_type.name = dev_name(&edev->dev);
> > -		edev->extcon_dev_type.release = dummy_sysfs_dev_release;
> > -
> > -		for (index = 0; index < edev->max_supported; index++)
> > -			edev->extcon_dev_type.groups[index] =
> > -				&edev->cables[index].attr_g;
> > -		if (edev->mutually_exclusive)
> > -			edev->extcon_dev_type.groups[index] =
> > -				&edev->attr_g_muex;
> > -
> > -		edev->dev.type = &edev->extcon_dev_type;
> > -	}
> > +	ret = extcon_alloc_groups(edev);
> > +	if (ret < 0)
> > +		goto err_alloc_groups;
> >
> >  	spin_lock_init(&edev->lock);
> >  	if (edev->max_supported) {
> 
> --

Thank you for the review and I will send a new patch including what you
mentioned soon

Thanks,


> Best Regards,
> Samsung Electronics
> Chanwoo Choi



  reply	other threads:[~2023-03-20  3:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230302090149epcas1p18924c1d17c91f6ecad2049e46b0b1e33@epcas1p1.samsung.com>
2023-03-02  9:01 ` [PATCH v4 0/4] Simplify extcon_dev_register function Bumwoo Lee
     [not found]   ` <CGME20230302090149epcas1p35d6a66bf8b29ef159ecee93441560c58@epcas1p3.samsung.com>
2023-03-02  9:01     ` [PATCH v4 1/4] extcon: Removed redundant null checking for class Bumwoo Lee
2023-03-13 11:03       ` Chanwoo Choi
     [not found]   ` <CGME20230302090149epcas1p2bad39de9aa367644cda3ffcb4dd4a612@epcas1p2.samsung.com>
2023-03-02  9:01     ` [PATCH v4 2/4] extcon: Added extcon_alloc_cables to simplify extcon register function Bumwoo Lee
2023-03-13 11:06       ` Chanwoo Choi
2023-03-13 11:07         ` Chanwoo Choi
     [not found]   ` <CGME20230302090149epcas1p31a7f99d83947be1d6f06141b352ce041@epcas1p3.samsung.com>
2023-03-02  9:01     ` [PATCH v4 3/4] extcon: Added extcon_alloc_muex " Bumwoo Lee
2023-03-13 11:08       ` Chanwoo Choi
     [not found]   ` <CGME20230302090149epcas1p33a5cd34ed350301b547c2ac3914569d4@epcas1p3.samsung.com>
2023-03-02  9:01     ` [PATCH v4 4/4] extcon: Added extcon_alloc_groups " Bumwoo Lee
2023-03-13 11:08       ` Chanwoo Choi
2023-03-20  3:12         ` Bumwoo Lee [this message]
     [not found]   ` <CGME20230302090149epcas1p35d6a66bf8b29ef159ecee93441560c58@epcms1p7>
2023-03-08  6:55     ` [PATCH v4 1/4] extcon: Removed redundant null checking for class MyungJoo Ham

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='186501d95ad9$d0812d30$71838790$@samsung.com' \
    --to=bw365.lee@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=cwchoi00@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.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

all inboxes | Powered by JetHome®