linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH v3 3/3] pinctrl: cherryview: Pass irqchip when adding gpiochip
Date: Thu, 14 Nov 2019 11:00:36 +0100	[thread overview]
Message-ID: <ee61eaa1-320c-964c-711c-407b7dec8311@redhat.com> (raw)
In-Reply-To: <20191113192722.GK32742@smile.fi.intel.com>

Hi,

On 13-11-2019 20:27, Andy Shevchenko wrote:
> On Wed, Nov 13, 2019 at 08:05:20PM +0100, Hans de Goede wrote:
>> We need to convert all old gpio irqchips to pass the irqchip
>> setup along when adding the gpio_chip. For more info see
>> drivers/gpio/TODO.
>>
>> For chained irqchips this is a pretty straight-forward conversion.
>>
>> Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> 
>>   	struct irq_chip irqchip;
>>   	void __iomem *regs;
>> +	unsigned int irq;
>>   	unsigned intr_lines[16];
> 
> This will conflict with our for-next.

Ah, I did cherry-pick intel-pinctrl for-next into my tree a couple of days
back, but I see there is a new "pinctrl: cherryview: Missed type change to unsigned int"
commit there which causes this conflict. I have cherry picked this new
commit into my tree and I will send out a v4 which should not conflict.

> 
>> +	if (need_valid_mask)
>> +		chip->irq.init_valid_mask = chv_init_irq_valid_mask;
>> +	chip->irq.init_hw = chv_gpio_irq_init_hw;
>> +	chip->irq.parent_handler = chv_gpio_irq_handler;
>> +	chip->irq.num_parents = 1;
>> +	chip->irq.parents = &pctrl->irq;
>> +	chip->irq.default_type = IRQ_TYPE_NONE;
>> +	chip->irq.handler = handle_bad_irq;
>>   
>>   	if (!need_valid_mask) {
>>   		irq_base = devm_irq_alloc_descs(pctrl->dev, -1, 0,
> 
> 
> Perhaps now it makes sense to
> 
> 	if (need_valid_mask) {
> 		chip->irq.init_valid_mask = chv_init_irq_valid_mask;
> 	} else {
> 		irq_base = devm_irq_alloc_descs(pctrl->dev, -1, 0,
> 		...
> 	} >
> ?

Ack good one, will also change this for v4.

Regards,

Hans

p.s.

About upstreaming this, I know this has a pre-requisite on the new add_ranges
callback stuff, but how about Linus Walleij creating an immutable branch
of his tree with the first series which adds the add_ranges callback in
there and then you merge that branch into pinctrl-intel/for-next and then
we just upstream all of this for 5.5 ? That seems easier then spreading
it out over 2 cycles. Just my 2 cents.


      reply	other threads:[~2019-11-14 10:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13 19:05 [PATCH v3 1/3] pinctrl: cherryview: Split out irq hw-init into a separate helper function Hans de Goede
2019-11-13 19:05 ` [PATCH v3 2/3] pinctrl: cherryview: Add GPIO <-> pin mapping ranges via callback Hans de Goede
2019-11-13 19:05 ` [PATCH v3 3/3] pinctrl: cherryview: Pass irqchip when adding gpiochip Hans de Goede
2019-11-13 19:27   ` Andy Shevchenko
2019-11-14 10:00     ` Hans de Goede [this message]

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=ee61eaa1-320c-964c-711c-407b7dec8311@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mika.westerberg@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;
as well as URLs for NNTP newsgroup(s).