public inbox for linux-gpio@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Sungbo Eo <mans0n@gorani.run>,
	Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Michal Simek <michal.simek@xilinx.com>, <git@amd.com>,
	git <git@xilinx.com>
Subject: Re: [PATCH 2/2] gpio: Add support for SLG7XL45106 I2C GPO expander
Date: Wed, 29 Jun 2022 12:37:30 +0200	[thread overview]
Message-ID: <02badfe5-395d-b63b-cf18-e2b3aad93625@amd.com> (raw)
In-Reply-To: <CAHp75Ve_mgam2jcyFG-NggziUScK3JBZ4fmtN+rjd+Vra=ixuw@mail.gmail.com>



On 6/29/22 12:15, Andy Shevchenko wrote:
> On Wed, Jun 29, 2022 at 9:14 AM Michal Simek <michal.simek@amd.com> wrote:
>> On 6/29/22 03:00, Sungbo Eo wrote:
>>> On 2022-06-29 04:21, Andy Shevchenko wrote:
>>>> On Tue, Jun 28, 2022 at 9:13 PM Andy Shevchenko
>>>> <andy.shevchenko@gmail.com> wrote:
> 
> ...
> 
>>>> Actually, why can't pca9570 be amended to support this?
> 
>>> It seems the slg7xl45106 driver reads/writes a reg at 0xDB so it is not
>>> compatible with pca9570 driver (in the current state), and (I suppose)
>>> it could be converted to use gpio-regmap.
>>>
>>> [1]
>>> https://lore.kernel.org/linux-gpio/69f5d1a1970838b8c4bd8d6e8dba6cac@walle.cc/
>>
>> As was mentioned driver is based on pca9570 and the only important difference is
>> with i2c_smbus_read_byte/i2c_smbus_read_byte_data and especially
>> i2c_smbus_write_byte/i2c_smbus_write_byte_data.
>>
>> Read can be aligned without any issue but write will have if/else because of
>> i2c_smbus_write_byte_data. Example below.
>>
>> Something like this. If this change is fine I think there won't be any issue to
>> just merge it with pca9570.
> 
> Thanks, I also would like to see something as below in the result.

ok. Good.

> 
>> diff --git a/drivers/gpio/gpio-slg7xl45106.c b/drivers/gpio/gpio-slg7xl45106.c
>> index bf25e6fb6782..b90950ae38c1 100644
>> --- a/drivers/gpio/gpio-slg7xl45106.c
>> +++ b/drivers/gpio/gpio-slg7xl45106.c
>> @@ -22,20 +22,24 @@
>>    struct slg7xl45106 {
>>           struct gpio_chip chip;
>>           struct mutex lock;      /* To protect writes */
>> +       u32 command;
>>    };
>>
>>    static int slg7xl45106_read(struct slg7xl45106 *gpio)
>>    {
>>           struct i2c_client *client = to_i2c_client(gpio->chip.parent);
>>
>> -       return i2c_smbus_read_byte_data(client, SLG7XL45106_GPO_REG);
>> +       return i2c_smbus_read_byte_data(client, gpio->command);
>>    }
>>
>>    static int slg7xl45106_write(struct slg7xl45106 *gpio, u8 value)
>>    {
>>           struct i2c_client *client = to_i2c_client(gpio->chip.parent);
>>
>> -       return i2c_smbus_write_byte_data(client, SLG7XL45106_GPO_REG, value);
>> +       if (gpio->command)
>> +               return i2c_smbus_write_byte_data(client, SLG7XL45106_GPO_REG,
>> value);
> 
> Missed change to gpio->command :-)

I found it too. :-)

Shubhrajyoti: Can you please merge that slg driver to 9570? That dt-binding will 
require small massage too.

Thanks,
Michal



  reply	other threads:[~2022-06-29 10:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 14:33 [PATCH 0/2] gpio: Add support for SLG7XL45106 I2C GPO expander Shubhrajyoti Datta
2022-06-28 14:33 ` [PATCH 1/2] dt-bindings: gpio: Add gpio-slg7xl45106.yaml Shubhrajyoti Datta
2022-06-28 14:33 ` [PATCH 2/2] gpio: Add support for SLG7XL45106 I2C GPO expander Shubhrajyoti Datta
2022-06-28 19:13   ` Andy Shevchenko
2022-06-28 19:21     ` Andy Shevchenko
2022-06-29  1:00       ` Sungbo Eo
2022-06-29  7:14         ` Michal Simek
2022-06-29 10:15           ` Andy Shevchenko
2022-06-29 10:37             ` Michal Simek [this message]
2022-06-29 13:19               ` Datta, Shubhrajyoti

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=02badfe5-395d-b63b-cf18-e2b3aad93625@amd.com \
    --to=michal.simek@amd.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=git@amd.com \
    --cc=git@xilinx.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mans0n@gorani.run \
    --cc=michal.simek@xilinx.com \
    --cc=shubhrajyoti.datta@xilinx.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